Installation Procedure for version Maintenance delivery Release 3.1(MD2)

(1)

Legal notice:

The information presented is subject to change without notice.

ALE International assumes no responsibility for inaccuracies contained herein.

Release Note

OmniVista 8770

TC2379 ed. 01 Release 3.1

Installation Procedure for version 3.1.10.00 –

Maintenance delivery Release 3.1(MD2)

This is the installation procedure for Omnivista 8770 version 3.1.10.00 until “Patch_311000B_EXE.zip”

It is available on Alcatel-Lucent Business Portal (https://businessportal2.alcatel-lucent.com).

Revision History

(2)

1 GENERAL

Note

The final letter usually indicated in the version naming is not significant & can create confusion with the delivered patches.

This document describes the installation procedure for OmniVista 8770 version 3.1.10.00 It refers to the Installation manual and Administrator manual.

These documents are essential since this procedure does not provide full installation details.

It is also highly recommended to consult Alcatel-Lucent Business Portal (https://businessportal2.alcatel-lucent.com). Some new information regarding OmniVista 8770 current version could be available. Our Technical Knowledge Center will help you to establish your technical diagnostics:

https://businessportal.alcatel-lucent.com/alugesdp/faces/gesdp/integration/KCSKnowledge.jspx

Warning

Each time you are requested to erase or edit a file, it is absolutely necessary to make a copy of the original.

These operations must be performed by an expert (ACSE) trained on the product. You can also contact the "Professional Services" team (mailto: [email protected] or your local Services representative).

Note

(6)

2 CONTENT OF THE SOFTWARE PACKAGE

2.1 References

The documentation is available on the Alcatel-Lucent Business Portal, in the section Technical Support\ Technical Documentation Library :

https://businessportal2.alcatel-lucent.com/technical_documentation_library

 Security Guide : 8AL90705USAF Ed.1.0

 SNMP Proxy : 8AL90708USAD Ed.1.0

 Installation Manual : 8AL90704USAH Ed.1.0

 Administrator Manual : 8AL90703USAH Ed.1.0

 Accounting and VoIP ticket collector : 8AL90709USAC Ed.1.0

 Users management API : 8AL90710USAC Ed.1.0

 OpenTouch™ Suite RTU Metering Feature : 8AL90712USAD Ed.1.0

2.2 Patches

2.2.1 Mandatory patches delivered with the DVD-ROM version

In the \Patches\Mandatory folder you will find the following patches:

- 8770.3.1.10.00 till

Patch_311000B_EXE.zip

Reminder:

On server side, all patches located in the Patches\Mandatory folder are automatically installed at the end of the installation.

Note

The manual patches files opening is failing when using the embedded Windows tool. It’s happening correctly when using an external tool like 7-Zip.

(7)

2.2.3 Anomaly Reports fixed in the patches

The list below is included in the “readme” file “PATCHES\Mandatory” in the R3.1.09.00 delivery :

[1]

========================================= Release Name : Patch_311000A_LDIF.zip Delivery date : 08 Sep 2017

=========================================

CR8770-6758 SUNRISE COMMUNICATIONS AG./AAPP [Related] : OpenAPI: User creation failure leaves ghost entry with incorrect userId

[2]

========================================= Release Name : Patch_311000B_EXE.zip

Delivery date : 08 Sep 2017

=========================================

CR8770-6796 NXO FRANCE [Report] : User created in pbx is not inserted in technical directory CR8770-6797 DIMENSION DATA GERMANY AG & CO. KG [Report] : 8770 3.0.13.00/SSH connections not closed in OXE following the synchronization/1-194062451

CR8770-6798 REVOLUTION TECHNOLOGIES REVTEC, S.A. [Report] : 8770 - Issue in loading the accounting tickets.

CR8770-6799 LEV03_SPAIN_PORTUGAL_53 [Report] : 8770 MSAD\Photo of one user is not synchronized between MSAD and 8770 LDAP\1-211103851

CR8770-6800 LEV01_END CSBU_ [Report] : Trunk group colonn is missing in accounting application CR8770-6801 TELBA AG [Report] : Issue with 8770 Report Designer/1-210425708/

License file

 To install OmniVista 8770 and to access the various clients, you must have a specific license file for your PCX network and which describes the available modules.

 In ACTIS, choose one PCX in the network and specify in its configuration that it is the declaration node for OmniVista 8770 server.

release OV8770 R1.0 R1.1 R1.2 R1.3 R2.0 R2.5 R2.6 R2.6.7 R3.0 R3.1

License version 1 2 3 4 5 6 7 7 8 9

Note _{This 3.1.09.00 version does accept a fresh server installation using a version 8 license (OT2.2.1 & OV 8770} 3.1 being maintenance/minor versions).

(8)

2.3 Versions of embedded software

Component

Version

Comment

Apache Tomcat

7.0.70 Apache

2.4.26 Apache Axis 2

1.5.1 Apache Ant

1.8.0 Jboss

6.1.0 EJBCA

Disabled.

Disabled due to JRE/JBOSS

incompatibility.

Installshield Premier

2015

Oracle Directory Server Enterprise

11.1.1.7.3 PHP

5.6.22 JRE(Oracle)

1.8.0.121 MariaDB

5.5.49 MySQL ODBC driver

2.0.10 Python

2.7.4 7 zip (7za – Command Line)

9.20

(9)

3 PREREQUISITES

This section describes the prerequisites required to install OmniVista 8770 server and client applications.

3.1 Server PC prerequisites

3.1.1 Hardware and software

< 5000 users > 5000 users

Operating System

Windows7 SP1 Professional (64 bits) Windows 2008 Server R2 Std Ed. SP1 Windows 8 Professional (64bits) Windows 8.1 Professional (64bits) Windows 2012 Server Std Edition Windows 2012 Server R2 Std Edition

Windows 10 Professional and Enterprise(64bits) Windows Server 2012 R2 DataCenter edition

Windows 2008 Server R2Std SP1 Windows 2012 Server Std Edition Windows 2012 Server R2 Std Edition Windows Server 2012 R2 DataCenter edition

Processor

1 processor Dual-Core (frequency near 2 GHz, but dependent on the processor architecture)

1 processor Quad-Core (frequency near 2,5 GHz, but dependent on the processor architecture)

RAM (minimum) 6 GB 8GB

Minimal

characteristics of

Hard Disk 120 GB 120 GB (disk: RAID5)

Graphics board 128 MB

Network card Ethernet 10/100Base-T

Partition 1 NTFS partition for installation of the LDAP server Internet browser Internet Explorer (version 9/10/11)

Mozilla FireFox (up to version 49)

Microsoft Edge and Google Chrome up to 54.x for the web directory Browsers should support Java applets

Drives A DVD drive is required

Warning

Due to the new apache version 2.4.20 and VC++2015 redistributable, the following hotfixes and service packs are mandatory.

Operating System Service Pack or Hotfix Installation

Windows 7 – Windows 2008R2 SP1

(10)

Note _{ From 50000 subscribers, you need the agreement of Alcatel-Lucent (process PCS – Premium Customer}

Support).

 From 100 nodes or PCS, you need the agreement of Alcatel-Lucent (process PCS – Premium

Customer Support).

 OmniVista 8770 has been validated in a VMware ESX

®

environment and Microsoft Hyper-V

®

.

The hyper-threading option should not be validated on the VM. Configure one CPU with 4 cores and not 2 CPUs with 2 cores.

 For Accounting, the maximum number of tickets is 30millions.

 It’s not recommended to use the local Client installed on the server. However, if for any reason

this Client is regularly used it’s advised to increase the memory size.

 Windows 2008 Server R2 being no more supported by Microsoft, it’s no more recommended to use

this Operating System.

3.1.2 Software and hardware compatibility

The installation on a dedicated Server PC in accordance with the prerequisite allows a correct operation of the software. If the number of users is lower than 250 and if the Server PC must support other applications, you should analyze the compatibility, estimate the performance requirements of other applications and strictly follow the installation/un-installation procedure. Moreover, the operation of these other external applications is not supported.

The Security Guide provides a description of parameters to take into account to study compatibility between an external application and OmniVista 8770 server.

3.1.3 Configuring the Server PC

The space disk requirements and the rules of disks partitioning are described in the Installation manual. Here are the essential points:

 Hard disk.

A NTFS partition must be set for installing the DSEE Oracle LDAP Server. When installing the server, it is better to keep the defaults directories and to change only the physical drives.

 The Path environment variable giving the access path to Windows and to its dll, which will receive the access path to OmniVista 8770 binary must be valid.

 The Path is managed through the System icon of Windows Control Panel.  If the Path is too long, a blocking can occur during installation.

 The Path must not have obsolete path, ;; doubles or \\ doubles.

 If there is an error message regarding the Path on installation, change its value and keep only the access path to the operating system.

C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32 \WindowsPowerShell\v1.0\

(11)

3.2 PCX compatibilities

3.2.1 IP & IP/X25 connections to OmniPCX Enterprise

From OXE R6.0 till R11.x and all associated OminVista 8770 releases the IP connection or IP/25 connection is ok

Warning

PPP connection is not supported.

OV8770 Releases OXE Releases IP Connection or IP/X25

>= R1.3 R6.0 to R8.0 Yes >= R1.0 R8.0.1 Yes >= R1.0 R9.0 Yes >= R1.0 R9.1 Yes >= R1.0 R10.0 Yes >= R1.1 R10.1 Yes >= R1.2 R10.1.1 Yes >= R1.3 R11.0 Yes >= R2.0 R11.0.1 Yes >= R2.5 & R2.6 R11.1 Yes >= R2.6.7 R11.2 Yes >= R3.0 R11.2.1 Yes >= R3.1 R11.2.2 Yes

3.2.2 OpenTouch

OV8770 Releases OT Releases Software version equal to or higher than …

(12)

3.2.3 OmniPCX Office

OV8770 Releases OmniPCX Office RCE Releases

Software version equal to or higher than …

>=R1.2 5.1 510/070.001 or 510/071.001 (wrong call duration fix) >=R1.2 6.1 510/053.001 or 610/054.001 (wrong call duration fix) >=R1.2 7.1 710/100.001 or 710/101.001 (wrong call duration fix) >=R1.2 8.2 820/090.001 or 820/091.001 (wrong call duration fix) >=R1.2 9.0 Not supported – upgrade to 9.2

>=R1.3 9.1 Not supported – upgrade to 9.2

>=R2.0 9.2 920/089.001

R2.6.7 10.2 Not supported – upgrade 10.3

R3.0 10.3 103/009.002 – recommended: last maintenance version 103/024.001

OXO Connect Releases

R3.1 2.0 02.0/016.003

3.2.4 OmniPCX Enterprise and OpenTouch : software locks

The modules of the OmniVista application are validated by the server license file. On the other hand the access to data of the various PCXs requires having appropriate software locks in each PCX:

OmniVista 8770 modules Software locks in OmniPCX Enterprise Configuration 50 – Configuration

Accounting 42 - Accounting users

98 – Accounting for local calls (for local accounting use) 99 – Accounting for ABC calls(for network accounting use) Directory (STAP calls) 49 – Directory

Traffic observation 42 - Accounting users 39 – Performance

VoIP 42 - Accounting users

Alarms 47 – Alarms

Secured SSH connection to OmniPCX Enterprise

(13)

OmniVista 8770 modules OpenTouch locks Description Configuration OAMP_CONFIG Configuration GUI

Alarms OAMP_ALARMS Alarms sending

Performance OAMP_VOIPPERF

OAMP_PERFKPI and mlsnmp

VOIP tickets sending (not used anymore since removal of Vital)

SNMP data sending

There is no lock for OXO.

3.3 Prerequisites for administration Client PCs

Hardware and Software (Minimum required)

Operating System Windows®7 SP1 Professional (32 or 64 bits) Windows® 8 Professional (32 or 64bits) Windows® 8.1 Professional (32 or 64bits)

Windows® 10 Professional and Enterprise (64bits)

Processor Intel® Core 2 GHz

This processor type is given as example. The frequency clock is a minimum requirement.s

RAM 4 GB

Hard drive 40 GB

Graphics board 4 MB video memory with a resolution of 1024 x 768, 16 million colors Monitor 17 inches (19 inches recommended)

Internet browser Internet Explorer

®

(version 9/10/11) Mozilla FireFox

®

(version 49.0.1)

Microsoft Edge

®

(not compatible with the Web administration client) Google Chrome

®

54 (not compatible with the Web administration client) Browsers should support Java applets

Free disk space OmniVista 8770 client cannot be launched if the free space in the memory size is below 750MB. Minimum required memory space is to be 750MB to run the JVM application. Refer: crqms00191548

The use of Clients installed on a Citrix Presentation server XenApp 7.6 is validated. The number of clients is limited to 4.

A minimum of 8 Gb dedicated RAM is required.

(14)

3.4 Prerequisites for Client PCs for directory consultation via WEB

Hardware and Software (Minimum required)

Operating System All Windows versions

Internet browser (tested) Internet Explorer

®

(version 11.0) Mozilla FireFox

®

(version 49.0.1) Google Chrome

®

54.0.2840.59 Microsoft Edge

®

Browsers should support Java applets

Warning

(15)

4 INSTALLATION AND UPGRADE

Consult the Installation Manual (Business Portal) for the detailed operations for installation and upgrades.

Warning

Make sure that no client in local has opened a session otherwise there is a risk of database corruption !

4.1 Installation

Warning

During the installation, OmniVista 8770 checks the KB2919442 and KB2919355 are well installed. Otherwise a popup will indicate the hotfix requirements are not installed.

Do not continue : press “Ok” and “No” in the subsequent popup. Then install those kb listed in 3.1.1 chapter hardware and software.

 Before server installation:

* Consult and apply prerequisites detailed in Installation Manual documentation, Chapter “Installation - Server Requirements – Collecting Data for the Server”

* Verify that your computer has administrator privilege (local administrator account)



Starting from Windows 7, when using an account different from “Administrator”, to start the server installation or an Upgrade, right click on the ServerSetup.exe file and select the option Run as administrator. Otherwise the installation would fail.

 8770 server Installation should start with the User Account Control (UAC) setting level “Do not notify “in Windows 7 professional machine.

(16)

 From 8770 R3.0.13.00.c New password policy has been introduced and the policy is applicable for all the password changes which happens during the first login/ password resets. This password policy is not implemented during installation under 8770 InstallShield. Refer CR8770-3453

 The firewall may generate messages asking for allowing communication for Java.exe and bin_ns-slapd.exe programs. You have to validate these requests.

 It’s mandatory to manage a fix IP address (and not a DHCP one) and also the default gateway before starting the server installation.

 The server name cannot contain the following characters: «/\[]":;|<>+=,?* _ ». In the opposite case, the server installation would fail.

 If a previous Java version is already installed on a machine, it will be updated to the latest Java version during OV8770 server or client installation.

As a consequence, to have OmniVista 8770 and OmniVista 4760 clients in the same machine then the clients have to be installed in the following order:

 OmniVista 8770 client  OmniVista 4760 client



It is not allowed to modify the default HTTP (80) and HTTPS ports (8443) for compatibilities reasons with the Performance application. The port 443 has as well to be available for Apache.

 During server installation, directory path should not contain any spaces. Incase other than default path is used for installation make sure new directory path doesn’t contain any spaces. Refer: crqms00149127

4.2 Server Upgrade

Warning

Make sure that no client in local has opened a session otherwise there is a risk of database corruption !

Warning

The server upgrade from 2.0 or 2.5 releases to R3.1.09.00 brings a modification for the VOIP quality supervision application. The Performance application based on a Vital Suite module has been removed. It has been replaced by a more simple and integrated module. Reports and data from the previous application will no more be available after the upgrade to R3.1. The data have to be processed before the upgrade.

The upgrade to OmniVista 8770 R3.1 is available from version 2.6.x (version = 7 in the license).

The upgrade provides upgrade of the OmniVista 8770 database in new version, including scheduled tasks, administrators accounts, …

Instead of upgrading, it is always possible to reinstall the server : reinstallation allows restarting with fresh data, and importing archived accounting tickets and custom report definitions.

(17)

 For release 1.3.10.00.a (version = 4), an intermediate upgrade in version 2.6.7 is needed, before upgrading to version 3.1,

 For release 2.0.09and 2.5.x(versions = 5 and 6), an intermediate upgrade in version 2.6.7 (version = 7) is needed before upgrading to version 3.1.

Reminder: OmniVista 8770 versions before 2.6 (1.3, 2.0, 2.5, …) are no more supported.

You can create an eSR to get an intermediate license 2.6.7 or 3.0 if you really decide for an upgrade from versions < 2.6, with the current OmniVista 8770 license and the confirmation of the order of the 3.1 or active SPS contract #.

For more details on the supported releases, please refer to the “Alcatel-Lucent OpenTouch® Suite for Mid & Large markets RELEASE POLICY INFORMATION ENT_MLE_016065” and “OmniVista 8770 feature list

8AL91400USAA” published on the Business Partner Portal.

4.3 Client upgrade

When a client connects to a server which has been upgraded, a proposal for the client update is suggested. - Accept the update

- Once the installation file has been retrieved, the client relaunch is required

- To relaunch the client, right click on the client launching icon and select the « run as administrator » option

(18)

5 SERVER UNINSTALLATION

To automatically uninstall all the server components launch the command:

Start\Programs\OmniVista8770\Tools\Uninstall OmniVista 8770 Server

The installation folder is not always deleted during the automatic server un-installation. In this case it has to be deleted before starting a new installation.

(19)

6 MIGRATION FROM OmniVista 4760

6.1 Description

The goal of the OmniVista 4760 to OmniVista 8770 migration is to export the following data from an OmniVista 4760 R5.2 server to import them in a new OmniVista 8770 server.

If an upgrade to OmniVista 4760 R5.2 from previous releases is required, a temporary license can be asked by an eSR.

The following data is retrieved:

 PCX tree and related management  Company Directory

 Accounting carriers data  Personalized reports definitions  Accounting organization by levels

To retrieve the accounting tickets from an OmniVista 4760 server you need to archive them, and then restore them in the OmniVista 8770 server. (For the Restore operation the option “Label for records (tickets)” has to be equal to “Loaded records”)

For the complete migration procedure, refer to the Installation Manual.

Warning

The Migration tool does not allow retrieving the directory replication management from OmniVista 4760. It has to be managed completely in OmniVista 8770 servers.

In addition, during migration, the replicated sub-suffixes from OmniVista 4760 are created as normal entries in the OmniVista 8770 company directory. That’s why when the sub-suffix is created to reproduce the replication with the same name the system throws “The entry already exists”.

The workaround for the issue is After migration :

1. Export the entries under the sub-suffix entry in the company directory (For eg., if it is a department sub-suffix, then export the department and its children).

2. Then delete the replicated entries (For eg., department sub-suffix and its children in this case) from the company directory.

3.

Now create the sub-suffix with the same name using the replication procedure. This will create the corresponding entry in the company directory.

(20)

7 SPECIFIC MANAGEMENT

7.1 SNMP Proxy feature

If SNMP service is not started in the machine during OmniVista 8770 server installation, SNMP proxy registry entries are not created and hence SNMP proxy will not be installed.

Then Windows SNMP service need to be started and script called inmcsnmpproxy.vbs (in the path:

\8770\bin\) has to be run to create SNMP proxy entries in the registry : \8770\bin\inmcsnmpproxy.exe -v2

7.2 Users management and OXE profiles

You need to validate the following parameter on OmniPCX Enterprise :

System\Other System Param\System parameters\Use profile with auto. Recognition=yes. Otherwise no data will be inherited from the profile at a user creation.

The document TC1520-ed.02 describes the User’s management.

7.3 Server IP address or server name modification

In order to change an OmniVista 8770 server name, you need to perform the following operations:  Backup the server data

 Confirm the Directory Manager account password (launch the tool 8770\bin\ToolsOmnivista.exe)  Uninstall the server

 Change the server name

 Install the server taking the same installation paths than on the previous server as well as the same company directory root name. The password entered at the installation time (Directory Manager and other accounts) has also to be the same as the previous one.

(21)

Note

The MSAD plug-in must be regenerated and installed again on the Active Directory server after rehosting.

7.4 MSAD synchronization and CMISE security

In the case where a secured access for configuration is managed for an OXE PCX, the user” MSAD8770Admin” has to be added to the authorized users list at PCX side. This is mandatory to allow users creation from the Web client that can be launched from the MSAD server.

Warning

The password of the account MSAD8770Admin must not be changed in the Security application

7.5 Backup on network drive

Network drives can’t be seen from Maintenance application.

A network backup location must be identified by its own UNC (\\server_name\shared_drive).

The Security guide describes the preliminary operations management for the backups on network drives.

7.6 Disable Java update

(22)

Note

If the Java update parameters are not displayed in the Java control panel, you have to do the following: Click Start. In the Start Search box, type command.

The result list will appear. Right-click Command Prompt in the Programs list. Click Run as administrator

To open the Java Control Panel, in the Command Prompt window execute this program:

"

C:\Program Files (x86)\Java\jre1.8.0_102\bin\javacpl.exe"

In the Java Control Panel, click on the Update tab. Uncheck the automatic updates.

Click Apply and then OK to save settings

If the Update tab is still not displayed the solution is to change from 0 to 1 the value of the following registry key:

(23)

(24)

7.7 Internet Explorer configuration

- When Internet Explorer 11 is the default web browser, the option "Use Microsoft compatibility lists" has to be enable and the server name or it’s IP address had to be added in the proposed list.

(25)

8 NEW FEATURES IN 3.1.10.00

This maintenance delivery contains only bug fixing. See chapter

9 NEW FEATURES IN 3.1.09.00

9.1 Autodiscovery on 8001

From OmniVista 8770 3.1.09.00 and 8001 R200 4.1.0.5, the provisioning of the device is with an identification key and password instead of the MAC address.

The provisioning with the MAC address is still available, and is the only way to provision the device for other versions of OmniVista 8770 and 8001.

(26)

10 NEW FEATURES IN 3.1.08.00

10.1 Accounting calculation evolution for the French market

For the French market, from the 1st October 2015, there are new tariffs for "colored numbers" (called in French “numéro vert, indigo, ...”). These tariffs are called "SVA" for “Services à Valeur Ajoutée” in French. They apply for specific numbers beginning by specific digits, like 08 XXXXXX. They are more expensive than normal numbers, whatever the Service Providers.

OmniVista 8770 accounting allows to add a fee on a communication depending on the dialed number, but what is new for the SVA is that there is an additional cost depending on the duration, in addition to the Service Provider cost.

So, there are two different duration costs calculations on the same call, that OmniVista 8770 will be able to calculate today. There are about 17 different tariffs /duration for the SVA, and hundreds of specific

numbers 08 XXXXXX. These tariffs are the same for France, whatever the service provider.

10.2 Mass provisioning import/export improvements

mass provisioning improvements to do in OpenTouch configuration application to have the import/export features at the same level as Import/Export features from OXE Configuration

- mimimum set of attributes

- no reference to internal OpenTouch id

 Export a template from OpenTouch configuration application : to easily create offline an import file for mass provisioning

The enhancement here consists in generating a header without unnecessary information and in the most appropriate way for import file. However for clarity reasons the header can’t give all the information present in the datamodel (type, min, max, attributes dependencies, …). Keep in mind it is a text file that can’t replace the knowledge of the model and the meaning of all the attributes.  Export Data from OpenTouch configuration application :

to export data from OpenTouch configuration with the same header as with export template option so that it’s easy to duplicate data from the exported lines in a new import file created offline. The export data option, already available in OmniVista 8770< R3.1, is enhanced to get exported data under the same header as with “Export template” option.

The administrator selects a datamodel or directly some instances and asks for an “Export data” operation. The result is a file (.txt, .csv or .prg) with exported data.

 Create/Modify/Delete instances by importing a file with a few attributes only from OpenTouch configuration application :

to be able to easily build offline a mass pro file with few attributes only so that I can import it to quickly create, modify or delete some instances in OpenTouch configuration.

In OmniVista 8770< R3.1, importing a file in OpenTouch configuration in order to create or modify instances always requires the full list of attributes, i.e. the complete header which can be retrieved by “export template” option. This constraint makes always to be totally dependent from the

(27)

Import can be requested from a local file with immediate operation or from a server file and scheduled

A log file is created for every scheduled import (same name with date indication). For immediate import, the status is given in the message area. Both cases are names log hereafter.

Note that due to the header changed the import files used in previous OmniVista 8770releases have to be updated.

 Complete and import a file from OpenTouch configuration in order to apply several modifications to OpenTouch node :

to import a file with all possible action types mixed with several models from OpenTouch

configuration so that I can apply a lot of modifications (creation, update, deletion) to an OpenTouch node from a single import file.

The administrator completes an import file offline by mixing :

 All action types: create (with ‘+’ symbol) , modify (with ‘#’), delete (with ‘-‘)  Several models

The same model can appear several times in the file but each time with a different header. For instance, the same model appears once with a header for creation, another one for modification and a last one for deletion.

During import, the actions are processed along with the order of the file, meaning that if the same datamodel appears several times in the file, eventually with different headers, the import starts with the first occurrence of this datamodel (and processes the actions from the below lines), then with the second, etc.

The datamodels are analyzed and executed in the file order : there is no lines reordering. This means that the possible dependencies must be solved with the file creation.

 Export a template from Users application :

to export a user template in a file so that I can easily use it to populate it in off line mode for mass provisioning purposes.

The file includes in the header all the possible attributes, whatever the type of the user (OmniVista 8770 or OXE or OT) plus an action in 1st_{column. Among all the attributes :}

 action : Create, Modify, Delete  userType : None, OXE, OT

 directoryLevel : the hierarchical directory level where the user is attached  lastName : user’s name

 firstname : user’s firstname

 uid : login, built as “<firstname> <lastname>” by default

Note that the user dn is no more present in the file as redundant with other attributes (uid, directoryLevel). Please note that this simplification makes the 3.1 file incompatible with the previous releases files. Note also that this format can induce some more for analysis and execution time (directory level to identify, uid and dn construction).

 Modify a user by importing a file with the minimum of attributes from Users application : to prepare offline a file, as simple as possible, and import it to modify user(s) from Users application so that I don’t waste time to export the user(s) to be modified first.

(28)

In OmniVista 8770< R3.1, if the administrator imports a file in order to modify users (action is set to “Modify”) and this file contains only the uid attribute (to identify the user(s) to be modified) and just one attribute, i.e. the attribute to modify (example : lastname), OmniVista 8770considers as NULL all the missing attributes as it is for user creation. Generally, the file import fails because NULL is not accepted as a new value for a lot of parameters.

The enhancement consists in managing properly the import of this kind of file :  action = Modify

 uid is set (in order to identify the user to modify, thanks to uid uniqueness)  only the attributes to change (meaning : not necessary to put the full header)  NULL values are not considered during the update operation

 Empty value is considered as a clear value (removing the current value) Not all the attributes are editable : directoryLevel, OXE or OpenTouch instance, …

This US makes the Users application be at the same level of service for modification by import as OXE configuration and OpenTouch configuration.

However note that as the user dn is no longer part of the import file, the execution time for such a file is increased with a preliminary search to get the dn of the user to update.

 Export a user for template from Users application :

to export a user from Users application so that I can use the exported user as a user template and easily duplicate it to create other users.

In OmniVista 8770< R3.1, “user export” option exists and allows to export a user from Users

application. This option is useful to modify the parameters of the exported user(s) in the export file and to modify it (them) by importing the file.

But, this option doesn’t suit to another use case which is the user duplication. That’s why a second “export user” like option is proposed in the same contextual menu, in addition to “user export” option which is kept without any modification. This new option, called “user export for template”, is a little bit different. The result file is included 2 lines

 A header line limited to the columns relevant for the exported user, depending on his type (none, OXE or OT) and editable based on the presence or not of a meta profile

 A values line where :

 action is set to “add”

Personal and mandatory values (name, firstname, uid, password, salutation (OTCV/CT), email(OTCV/CT)) are set to “XXXX”

 Personal attributes that can be overwritten from metaprofile are left blank (directory number, login (OTCV/CT) TUI and GUI passwords (OTCT/CV)), device number (OTCT)

 Other editable attributes are copied from the exported user : metaprofile, devicetype (OXE), key role (OXE), cost center

 Non editable attributes are not part of the file (header and value)

 When the exported user doesn’t own a metaprofile, the metaprofile column is removed and replaced the metaprofile attributes (node instances, user profiles) and the values copied from the exported user

(29)

Remember that the goal of this US is to minimize the number of values to set in the export file in order to create new users from an exported user (used as a template).

Also note that this new “user export for template” option is different from “export template” which generates the header only.

10.3 Support of OpenTouch 2.2.1 (OT 12) / OXE 11.2.x / OXO 11

 OXE 11.2

All patches compatible in 11.2 including 11.2, 11.2.1 & 11.2.2

 OT 12

 OXO Connect R2 (ex. R11)

This requirement is to support the OXO R11 in the OmniVista 8770R3.1, in addition to the previous releases. It is an extension of the general support of the OXO by the OmniVista 8770.

From the point of view of the administrator, the support of the new release is transparent, except the installation of the new OMC, used to the Configuration and Maintenance activities

(backup/restore and software download).

10.4 Multi-valued Primary link in the Directory to be consistent with 4760

In 4760 the primary link attribute between a Person entry in Company Directory and an OXE Subscriber entry in Technical Directory was a multi-valued attribute allowing a person to be associated with several OXE devices with full name/firstname update.

In OmniVista 8770due to OpenTouch support, and its user-centric notion (1 user – n devices), the primary link is getting mono-valued. The primary link is also used within the Users application to manage a person, the OXE/OT user and his associated devices in a unified way.

This means that during the 4760 to OmniVista 8770migration, only 1 primary link value is kept, the other being discarded. Even if secondary manual links are set up after migration, the name/first name updates are not propagated from person to OXE devices.

The requirement addresses this point with the addition of a new attribute – additionalResources – set up during migration with the extra primary link values, available for manual set up from Directory application, that ensures the update of name/firstname in the same way as the primary link.

10.5 Modification of all mapping attributes in Active Directory

synchronization

to allow a more flexible mapping between the AD attributes and the OmniVista 8770attributes, regarding the mapping direction as well as the default mapping

The solution takes advantage of the solution put in place for the “crqms00187239 – [8770] AD synchro enhancement” which synchronize the AD organization levels with the adjunction of the objectGUID attribute as a unique reference in AD.

The following recommendations have to be considered to avoid data inconsistency

- In case of migration to OmniVista 8770R3.1, a 1st_{synchronization is done in 8770 R3.1 before any}

modification / deletion in the synchronization rules.

- After any modification of the attribute mapping, a complete synchronization and the generation of the AD Plugin has to be performed

 Define the attribute mapping for AD synchronization so that the AD attributes and 8770 are kept consistent.

(30)

perform an AD synchronization so that the entries and their attributes are kept consistent according to the mapping rule.

Once the correlation is done between the AD entry and the 8770 entry is done, the update of the entries is done in step 9.

Special operation for uid update when rename operation is used. Already created entries are not impacted when one of the attributes firstname, name or uid is removed from the attribute mapping, whereas these created entries are impacted during a complete synchronization when the mapping is modified.

 AD Client :

to create a user in the OXE/OT from the AD Client with attributes automatically copied from the AD entry to the 8770.

From the selected AD user entry, from the menu "Alcatel-Lucent Enterprise Unified Users Management" the AD Client is launched in the default browser. The attributes defined in the mapping rule in the AD  8770 direction are searched from the AD entry and used to populate the 8770 entry.

If no attribute mapping is defined for firstname attribute (givenname), it is considered as empty and non-editable in the AD Client.

If no attribute mapping is defined for name attribute (cn), it is valued with lastname (sn) + firstname (when it is exists).

10.6 Secure communication with 8770 server for MSAD plug-in

This is to prevent the AD Client url to be copied/passed/updated so that it is no more possible to use the URL outside the MSAD application and perform creation/deletion/update operation in the 8770 server.

10.7 Management of Active Directory users with the same name/surname for

8770 directory synchronization

Use case : a first AD user with name John Doe is already created in OmniVista 8770 Directory, associated or not by a Primary link with an OpenTouch user.

A second AD user is created thru the AD plug-in with the same Name and surname, but with different attribute from AD point of view, for example email address.

Today, this second user is not created in OmniVista 8770.

This second user should be created in OmniVista 8770 Directory as a new Entry. If a Primary link already exists with an OXE user, then no link should be added with this OXE user, the existing link should not be broken.

10.8 Active Directory synchronization enhancement: synchronize the AD

organization levels

Up to 8770 3.0, the AD hierarchical organization is copied into the 8770 Company Directory during the AD synchronization with tree mode, only in creation mode. This means that any subsequent change in the AD hierarchy (delete, rename or move) nor the move of the inner users to another AD hierarchical level is not reflected in the 8770 hierarchy during the AD synchronization.

(31)

The AD levels synchronization is the 1st_{step of the AD synchronization in case of a Tree mode}

synchronization, followed by the users synchronization and the 8770  AD update.

Based on an ldif export file with the AD organizational levels, the AD synchronization expectation is to maintain the same hierarchy in AD and in 8770 Company Directory, for the parts of the AD and 8770 trees defined in the synchronization rule, with the assumption the AD hierarchy is the master to be replicated.

Any change in the AD hierarchy will not be seen in the 8770 Company Directory as long as a 1st_AD

synchronization is not run from 8770 R3.1, that brings in 8770 the linking attribute objectGUID. It is recommended for the Administrator to perform an AD synchronization from 8770 3.1, before he performs a change in AD hierarchy he would like to be automatically forwarded to 8770.

The evolution applies mainly for a synchronization in hierarchical mode.  Update the Department name :

To have the update of a department name in AD be automatically reported in 8770.

Note : After department name update, AD Synchronization needs to be performed before using AD Client.

 Create an AD department :

an AD Department newly created be automatically created in 8770 at next synchronization  Move an AD department to another place :

to move an AD Department to another place,

 either in the same root point covered by the synchronization, so that move is forwarded in the 8770

 either outside the root point covered by the synchronization, so that the department is deleted or marked as deleted with its inner users

 Delete an AD department :

the department deleted in AD is automatically deleted in the 8770  Move a user to another AD department :

the AD user move to a department is forwarded to the 8770 directory

10.9 ONLY_RTU_CA_02 New RTU KPIS 2

US_RTU_Meter OPENESS APIS (CSTA/TxAPI/Recording)

- get the following counter on APIS : - CSTA Monitor - TAPI Monitor - TsAPI - CSTA Pilot monitoring These KPI are available from OXE m1 (12.0), from OXE > System > Other System Param. > RTU

Parameters instances

US_RTU_Meter RSI /RSI Business counters

- to see in the 8770 RTU reports, the average, maximum and minimum value of Agent logged as RSI Agent. So that we’ll able to see what it has been really used during the commercial period. -

US_RTU_Meter RSI Business counter

(32)

10.10 Other KPIs

US_RTU_meter DESKSHARING

- The KPI is a concatenation for all device types, based on the number of OXE User instances with "Set

function" parameter as Desk Sharing user.

KAT067 DESKSHARING USER

Early delivered as a TR+1 patch against 3.0

Count real users and DSS devices, based on the OXE Subscriber "Set function" parameter : count only

Default and Desk Sharing Set.

US_RTU_meter_SIP KPIs

- to get a KPI calculate the real SIP devices whatever the level of service (SIP device or SIP extension), excluding the SIP devices for OTCv users and the OXE SIP nomadic device

A counter KAT068 OXE STD USER EXTERNAL SIP DEVICE calculates the OXE SIP devices, not used for an OTCv user, ie. excluding the devices where the "Gateway type" attribute is valued as ICE type. A counter KAT069 OXE NOMADIC SIP DEVICE calculates the size of the pool of OXE SIP devices declared for the Nomadic feature. This counter is evaluated from OpenTouch as the number of OXE SIP subscriber instances (OT > System services > Topology > OXE CS > OXE SIP subscriber)

US_RTU_meter_HOTEL ROOM

- to get a KPI calculate the Room numbers so that it is possible to a differentiated price / per room for room with multi-devices

Already some KPIS are provided up to 8770 3.0

KAT051 NUMBER OF DEVICES IN HOTEL MODE (GUEST OR ROOM) KAT052 NBR OF DEVICES IN HOTEL MODE (ADMINISTRATIVE) KAT053 NBR OF DEVICE GUEST OR ROOM IN CHECKIN

The new counters have to differentiate the rooms and the guests, for the devices counter and the checkin counter. However the availability of separate checkin counters depends on the OXE release In addition a total counter for “Suite” type is added.

New Counters are :

KAT070 NUMBER OF CONFIGURED SUITES

KAT071 NUMBER OF DEVICES IN HOTEL MODE (GUEST) KAT072 NUMBER OF DEVICES GUESTS IN CHECKIN

KAT051 is replaced by KAT151 NUMBER OF DEVICES IN HOTEL MODE (ROOM) KAT053 is replaced by KAT153 NUMBER OF ROOMS IN CHECKIN

These KPI are delivered as TR+1 patch against 3.0

US_RTU_meter MULTI_COMPANY

- to get a KPI calculate the number of companies within and OXE with "multi-company" mode activated and configured

The "Multi-company" feature is activated by the flag OXE > System > Other System Param. > Spec. Customer Features Parameters > Centrex Version No.

Then an OXE Entity (OXE > Entities) can be declared as a company as soon as it assigned a Company

Call Number value, except the entity 0.

(33)

10.11 Upgrades

10.11.1 3.1 component updates

Migration to MariaDB 5.5.48 at least Migration to easel.js 0.8.2

Migration to jQuery 2.2.3

Migration to SFTPdll 3.8.2 (wodSFTPdll) Migration to Apache 2.4.20 at least

Migration to JRE 1.8u121 at least or better with Oracle Critical patch Updates

10.11.2 From OV 8770 2.6/ 3.0

The initial version can come from a R2.6.x or a R3.0 :

2.6.05.01 (TR), 2.6.07.01 (MD1), 2.6.07.05 (MD2), 2.6.07.06 (MD3), 2.6.07.07 (MD4), 2.6.07.08 (MD5) and 3.0.13.00 (TR)

The supported versions of the license file are 8 (upgrade) and 9 (upgrade and fresh installation)

10.12 New license = 9 (from 3.1.08.00)

(34)

11 MISC INFORMATION & RESTRICTIONS

Note

All the “crqms…..” ref. mentioned below are internal anomaly reports references. Check with Tech. Support on which version/patch it is fixed or if correction is important for you.

In this chapter you will find misc information about applications, components that could be useful plus some restrictions.

11.1 RTUM

The Date and time of OmniVista 8770 server and OpenTouch sever should be synced for KPIs update in RTUM reports afterOpenTouchPartial sync (Global/Separate).

11.2 Unified User Management (UUM):



To create OXE/OXE MME user based on profiles, OXE/OXE MME synchronization needs to be performed first to get the OXE profiles /OXE MME templates in UUM.

While creating OXE profile in OXE configuration, attribute profile name is mandatory to be filled and profile name should be in UPPER case Otherwise “OXE error: Profile directory number not found” will get displayed during OXE user creation using profile in UUM : Refer: crms00299205

When a user (with usertype as OXE / OT) is created using the metaprofile thru the UUM application and the particular user‟s firstname or lastname is modified in OXE/OT, A new entry will be created instead of modifying the existing entry. The metaprofile name will be lost from both the user entries. Refer

crms00361222

Cost Center override on the OXE user, does not work when there is a non-default cost center id in the OXE profile. Refer:crms00358229

Restriction:

8770/Users : CRUD operations with 1K OtCt users in UUM grid takes too much time. Refer : CR8770- 5772

11.3 Device Management (DM):

OT/8770 rehosting: MYICPCSIP cannot connect - the OTCT MYICPCSIP DM files keep the old domain name value explaining that: The SIP URI value will be filled by the administrator during association of MYICPCSIP device to OTCt user. So administrator has to update SIP URI manually based on the new OT host name after rehost. Refer: crqms00194838

Only 70 devices will be displayed during search of Particular device type. Refer the following CR for more details crqms00179010: 8770 - device application - filter - big set of instances( 4K ) -> space problem indicated.

No more support for MIC Android, MIC Blackberry, MIC Windows and MIC Nokia mobile devices. Ref: crqms00192940 :Devices: MIC Android, MIC Blackberry, MIC windows ,MIC Nokia devices to be removed from devices application

(35)

 

For overall Terminals tests performed in 8770 with “device profile” has given the status below:

Device Node

Without Profile(Normal

Deployment) With Profile Binary version

VHE(8082) OXE OK OK R300_01_15_16.zip

VHE(8082) OT OK OK R300_01_15_16.zip

VLE (8002/8012) OXE OK OK MyICphone_8002_8012_R110_ 03_056_0.zip VLE (8002/8012) OT OK OK MyICphone_8002_8012_R110_ _{03_056_0.zip}

8001 OXE OK OK 8001-R200.4.1.0.5.zip

8068/

8038 OT OK OK 8068_R220_3_31_01

8088 OT OK OK 8088_R300.03.001.0.2020.zip

8088 OXE OK OK 8088_R300.03.001.0.2020.zip

OTC smart phone OT OTC-android-smartphone-_{2.11.05.0.apk}

It is strongly recommended to upgrade to the last firmware binary (released in the Business Portal).

Restriction:

CR8770-3073: Devices:"Could not load the table due to Aborted: memory limit exceeded" error thrown during search of OTC smartphone devices

11.4 SIP devices supported

SIP DEVICES AND MOBILES MANAGED

Declaration Configuration Deployment Open

API Inventory

Declaration Configuration Deployment

Open

API Inventory

OpenTouch Connection users

ST 2022/2030 1 _X _X _X 4008/4018 3 _X _X _X 8001 from OXE 11.1 _X _X _X 8002 1 X X X X 8012 _X _X _X _X 8082 in hotel mode _X _X _X _X

(36)

8088 video associated as a SIP device _X _X _X _X Windows Desktop: MyIC PC or OT Connection

PC 2 _X _X _X

MIC mobile: Android, Blackberry, Nokia,

Windows2 _X _X _X

OTC Smartphone: iPhone, Android _X _X _X_{for Android} _X

Anymobile _X

OpenTouch Conversation users

4008/4018 3 X X X 8001 from OT 2.1.1 _X _X _X 8002 1 X X X X X 8012 _X _X _X _X _X 8038 from OT 2.1.1 _X _X _X _X _X 8068 _X _X _X _X _X 8082 _X _X _X _X _X 8088 _X _X _X _X _X

Windows Desktop (MyIC PC or OT

Conversation PC) X X X X

OTC Smartphone (iPhone, Android) _X _X _X_{for Android} X from OT

2.1.1 X

OTC Tablet (iPAD, Android) _X _X _X_{for Android} _X

MIC mobile (Android, Blackberry) 2

X X X

Video endpoint _X _X

Anymobile _X

1_{Thomson ST 2020/2022 is no more supported. 8002 Deskphones are removed from the catalogue} since November 2014 Offer

2_{MIC client deployment is no more possible from} OpenTouch 2.2

3_{4008/18 Deskphones are no more supported}

11.5 OpenTouch Configuration

OT node number entered during the OpenTouch declaration should be numeric value. Otherwise the topology synchronization with the Performance application will fail.

(37)

User creation, the TUI password should not be trivial for security reason. It should not be of cyclic, repetition, increasing or decreasing fashion.

services -> Security -> Password Management -> Allow trivial TUI check this attribute to allow trivial values to be used for TUI password. Uncheck this attribute doesn’t permit using trivial value

for TUI password.

For OTVM- Automatic creation of persons in directory is applicable for only for OXE with OTVM users. The connect operation of OpenTouch from 8770 will not work with the root user and password. The maintenance credentials should be used for login.

While configuring OpenTouch server if ERROR_REMOTE_EXCEPTION error occurs then check following : - Add the FQDN of OpenTouch in the hosts file of windows where the 8770 server is installed - Restart of JBOSS service

A new tab „feature‟ is available for OpenTouch nodes which have the version greater than OpenTouch R 2.1. Tree

will be segregated according to Tasks.

New mass provisioning rules are implemented in R 3.1 to make ease of export/import operations. Improvements include:

- Import/export with minimum set of attributes - New enhanced template

- “Action” attribute in first column, “displayname attribute” in second column - No reference to internal OpenTouch id.

For detailed change refer to chapter 8.2 Restriction:

java.exe(Administrator-jboss) service utilizes maximum memory (1Gb) during Open Touch configuration basic operations with entries more than 1k. Refer crqms00205094

Scheduled export failure scenarios happens sometimes. Refer crqms00205095

11.6 OpenTouch Synchronization

User name for template management should be filled in the connectivity tab to get the templates during synchronization.

After declaration of OXE node, OXE Complete Global synchronization will not synchronize associated OpenTouch node. OpenTouch node should be synchronized first.

TUI voice mail should be declared in both OXE and OpenTouch for successful complete global synchronization.

11.7 Performance Application

(38)

11.8 Re-hosting

Execute the re-hosting script in the “Elevated command prompt” in Windows 7, otherwise script execution will be failed. Refer the below link for info:

http://www.blogsdna.com/2168/windows-7-how-to-open-elevated-command-prompt-withadministrator- privileges.htm

11.9 Audit

After enabling the Global flag for audit process the 8770 client needs to be restarted to get the information of 8770 login/logout

11.10 OpenTouch Alarms

OpenTouch Alarms will not be received if two OT's have same username but different parameters (like encryption password, passphrase, etc..).To receive the OpenTouch alarms from all the declared OpenTouch nodes, there are two possible configurations:

- 1st option: use the same SNMP v3 user name and same associated parameters (security level, user password, passphrase, …) for all the OpenTouch nodes

- 2nd option : use a different SNMP v3 user name for each OpenTouch node

Topology : Dashed Line style between two network elements will be supported with IE version 11 and above. Purge Alarms failed in Weekly & Daily Job. Refer: CR8770-3735

11.11 PKI

Database and EJBCA passwords are hard-coded during the PKI installation.

Default browser certificate needs to be installed to open PKI administration page. The default PKI browser certificate (superadmin.p12) is available in the following location %install

drive%/8770\Ejbca\p12

It is not possible to use password with more than 8 characters in PKI, since 'Unlimited Strength Jurisdiction Policy Files are not installed.

Restriction:

PKI application is greyed out in 8770. Please refer CR crqms00183697 - 8770 Component

11.12 .OmniPCX Office and OXO Connect Configuration

OXO software update through 8770 Network Maintenance application has some issue for ONE 2.0 version. Refer CROXOOC-60

OXO Cloud Connect alarms are not received. Refer CROXOC-136

11.13 MSAD - Active Directory Synchronization & Light Client for User

Provisioning

(39)

( Cn=ladmin,CN=Users,DC=FranceTelecom,DC=com)needs to be entered instead of the username alone.

 Providing a translation for all the MSAD attributes is not possible because all the MSAD attributes are dynamically pulled out from the MSAD; Refer:crms00361627

 MSAD: Device Association Information is NOK for OXE-OT user creation with two device profile associated with it; Refer: CR8770-2443

 MSAD: Sync Log is not matching with 8770 server installation language; Refer: CR8770-1410  MSAD: Export of MSAD data is restricted to branch level; Refer: CR8770-2322

 MSAD: Deleted user information getting display in another browser; Refer: CR8770-73

 MSAD: Performance Issue creations and modification of user in AD taking long time then general; Refer: CR8770-2975

Workaround:

 AD Web Client: Page refresh not happening after OXE/OT metaprofile selected from the IE8&9 browser

Workaround:The Active Scripting needs to be enabled in the IE browser Internet Options Enable the Active Scripting as follows:

Open Internet Explorer, click the "Tool" button in the menu bar, select the "Internet Options” “Security” tab

To enable JavaScript for all sites:

Select the "Internet" area, select "Custom Level" and "Security Settings - Internet Zone" box gets launched.

Enable "Active Scripting" under the “Scripting” section and then click the OK button to apply the settings. Restart your browser when finished to apply the settings and enable

JavaScript.

 MSAD Client: 8770 Administrator is not allowed change the default password assigned to the MSAD8770Admin account. Changing the password will make AD Client inoperable.

o Workaround: If MSADAdmin password is changed then restart the Jboss service in 8770 server.

 MSAD: MSAD: User Creation/Modification not possible from AD side with latest IE 11.0 browser; Refer: CR8770-3874

o Workaround: If we are using Internet Explorer, the host name has to be added in the trusted sites in the below following path: Tools->Internet Option->Security->Trusted sites

Restriction:

 None

11.14 SNMP Proxy

8770 SNMP proxy will be installed as a part of 8770 installation if windows SNMP Service are present in that machine.

(40)

SNMP proxy will be installed by creating necessary registry entries.

If SNMP service is not installed in the machine, then during 8770 installation SNMP proxy registry entries are not created and hence SNMP proxy will not be installed.

So, to use SNMP proxy feature then Windows SNMP service need to be installed and script called inmcsnmpproxy.vbs (in the path: \8770\bin\) has to be run to create SNMP proxy entries in the registry External tools like TrapReceiver and iReasoning MIB Browser should not be installed to receive the traps from the 8770 server side rather we could install them in the client side machines.

These tools by default take the port number 162 and due to this 8770 will not receive OpenTouch Alarms. This may be due to the port conflict between these two.

11.15 Citrix Presentation server

To run multiple 8770 clients in Citrix presentation server the minimum requirement is 8GB RAM; if the available RAM is less 8770 GUI will not perform as expected.

11.16 8770 UTF8 Characters in Web Directory

DM Overview and Scope:

The requirement addresses the need for a full UTF8 support in all applications for User names and firstnames. The objective is to manipulate user names/firstnames in UTF8 characters in the whole 8770 management platform and all the connected elements (OXE/OT) as well as an external corporate directory, from all the 8770 applications, Users as well as Directory, ... WebDirectory included, in both ways, meaning from 8770 to other elements as well as from network elements to 8770.

The requirement is driven by the capability of the UA/NOE device to display non ASCII characters and the OXE management restrictions where the OXE User attributes vary from Directory name and firstname to UTF8 name and firstname depending on the character set used for the name/firstname In 8770 and OT, priority is given to UTF8 names, meaning UTF8 names are used preferably, at least in all Directory-based applications.

11.17 SHA2 conformity

SHA2 certificate would be installed by default during fresh installation of 8770

For 8770 upgrades from R2.6 SHA1 certificate would only be available. If administrator wants to migrate to SHA2 he should use toolsOmnivista.exe

11.18 Limitation for displayed entries following a search by device type on

OpenTouch

In the Devices application, the maximum of displayed entries following a search by device type can be limited to 70.

This evolution has been made mandatory to prevent from a memory overload following some OpenTouch data model modifications.

(41)

11.19 8082 MyIc Phone on OmniPCX Enterprise and Https requests

Http requests from 8082 MyIc Phone to OmniVista 8770 server are not supported.

Https requests are now mandatory. The OmniVista 8770 server is checking the device certificate at each file downloading request.

Warning

A particular care has to be taken before doing an upgrade to R3.1. Make sure the devices are doing https requests and not http

11.20 VOIP quality supervision

The Performance application based on a Vital module being removed from the product as of 2.5 release. The reports and data from this application will no more be available after an upgrade to R2.5 and next releases.

So they have to be used before the upgrade.

The VOIP quality supervision is now managed thanks to predefined reports definitions included in the Reports application.

The reports are only available for OmniPCX Office and OmniPCX Enterprise (version superior or equal to 8.0)

11.21 Topology

The Topology application has been re-designed in R2.0.

The customized views from releases older than R2.0 will be lost after an upgrade from these releases to R2.O and next versions.

User with Read only rights is able to modify Topology. Refer to : crqms00188231

11.22 USERS

Users creations fail when the Entity 1 does not exist on the OmniPCX Enterprise.

The reason is that the user creation by profile is failing in this case. The system tries first to create the user, using the default parameters (including missing entity 1) before applying the profile’s parameters.

(42)

Warning

An OXE user with ICS rights will be counted for 2 users at the license level. This is not managed by ACTIS.

11.24 Upgrade

Warning

Case of an upgrade with a local client already started ! it is mandatory to check that all the clients are stopped !!!

(43)

Installation Procedure for version Maintenance delivery Release 3.1(MD2)

Release Note

OmniVista 8770

Installation Procedure for version 3.1.10.00 –

Maintenance delivery Release 3.1(MD2)

Table of contents

1 GENERAL

2 CONTENT OF THE SOFTWARE PACKAGE

2.1 References

2.2 Patches

2.2.1 Mandatory patches delivered with the DVD-ROM version

Patch_311000B_EXE.zip

2.2.3 Anomaly Reports fixed in the patches

2.3 Versions of embedded software

Component

Version

Comment

Apache Tomcat

7.0.70

Apache

2.4.26

Apache Axis 2

1.5.1

Apache Ant

1.8.0

Jboss

6.1.0

EJBCA

Disabled.

Disabled due to JRE/JBOSS

incompatibility.

Installshield Premier

2015

Oracle Directory Server Enterprise

11.1.1.7.3

PHP

5.6.22

JRE(Oracle)

1.8.0.121

MariaDB

5.5.49

MySQL ODBC driver

2.0.10

Python

2.7.4

7 zip (7za – Command Line)

9.20

3 PREREQUISITES

3.1 Server PC prerequisites

3.1.1 Hardware and software

®

®

3.1.2 Software and hardware compatibility

3.1.3 Configuring the Server PC

3.2 PCX compatibilities

3.2.1 IP & IP/X25 connections to OmniPCX Enterprise

3.2.2 OpenTouch

3.2.3 OmniPCX Office

3.2.4 OmniPCX Enterprise and OpenTouch : software locks

3.3 Prerequisites for administration Client PCs

®

®

®

®

3.4 Prerequisites for Client PCs for directory consultation via WEB

®

®

®

®

4 INSTALLATION AND UPGRADE

4.1 Installation





4.2 Server Upgrade

4.3 Client upgrade

5 SERVER UNINSTALLATION

6 MIGRATION FROM OmniVista 4760

6.1 Description

3.

7 SPECIFIC MANAGEMENT