TC2837en-Ed01 Installation Procedure For OmniVista8770 R4.2.14.00

Release Note OmniVista 8770
TC 2837 ed. 01 Release 4.2
Installation Procedure for version 4.2.14.00 –

Release 4.2 Maintenance Delivery #2
This is the installation procedure for OmniVista 8770 version 4.2.14.00
The software is available on Alcatel-Lucent Business Portal (https://businessportal2.alcatel-lucent.com).
Revision History
Edition 01: March 2021
Legal notice:
www.al-enterprise.com The Alcatel-Lucent name and logo are trademarks of Nokia used under license by ALE. To view other
trademarks used by affiliated companies of ALE Holding, visit: www.al-enterprise.com/en/legal/trademarks-copyright. All other
trademarks are the property of their respective owners. The information presented is subject to change without notice. Neither
ALE Holding nor any of its affiliates assumes any responsibility for inaccuracies contained herein. © Copyright 2021 ALE
International, ALE USA Inc. All rights reserved in all countries.
Table of contents
1 GENERAL ................................................................................................................................................ 5
2 CONTENT OF THE SOFTWARE PACKAGE .................................................................................................. 6
2.1 References ....................................................................................................................................... 6
2.2 Patches ............................................................................................................................................ 6
2.2.1 Mandatory patches delivered ...................................................................................................... 6
2.2.2 Anomaly Reports fixed in the patches ......................................................................................... 6
2.2.3 Additional patches (mandatory) .................................................................................................. 8
2.3 License file ...................................................................................................................................... 8
2.4 Versions of embedded software ........................................................................................................ 9
3 PREREQUISITES ................................................................................................................................... 10
3.1 Server PC prerequisites ................................................................................................................... 10
3.1.1 Hardware and software............................................................................................................. 10
3.1.2 Virtualization requirements ...................................................................................................... 11
3.1.3 Software and hardware compatibility ........................................................................................ 12
3.1.4 Configuring the Server PC ......................................................................................................... 12
3.1.5 Servers delivered by Alcatel-Lucent .......................................................................................... 12
3.2 PCX compatibilities ........................................................................................................................ 13
3.2.1 IP & IP/X25 connections to OmniPCX Enterprise ......................................................................... 13
3.2.2 OpenTouch ............................................................................................................................... 14
3.2.3 OmniPCX Office and OXO Connect ............................................................................................. 15
3.2.4 OmniPCX Enterprise and OpenTouch : software locks ................................................................. 16
3.3 Prerequisites for administration Client PCs ...................................................................................... 17
4 INSTALLATION AND UPGRADE .............................................................................................................. 18

4.1 Installation ..................................................................................................................................... 18
4.2 Server Upgrade ............................................................................................................................... 20
4.3 Client upgrade................................................................................................................................ 21
5 SERVER UNINSTALLATION .................................................................................................................... 22

6 MIGRATION FROM OmniVista 4760 R5.2 ................................................................................................ 23
7 SPECIFIC MANAGEMENT ....................................................................................................................... 24

7.1 Users management and OmniPCX Enterprise profiles ........................................................................ 24
7.2 Server IP address or server name modification ................................................................................. 24
7.3 MSAD synchronization and CMISE security ........................................................................................ 24
7.4 Backup on network drive ................................................................................................................ 25
7.5 Internet Explorer configuration ....................................................................................................... 25
8 NEW FEATURES IN OMNIVISTA 8770 R4.2 ............................................................................................. 27

8.1 Compatibility with Windows Server 2019 .......................................................................................... 27
OmniVista 8770 - Release 4.2

Installation Procedure for version 4.2.14.00 –Release 4.2 Maintenance Delivery #2 TC 2837 ed. 01
© Copyright 2021 ALE International, ALE USA page 2/58
8.2 Users application in the Web Based Management (WBM) enhancements ............................................ 27
8.2.1 New pagination in the navigator ................................................................................................ 27
8.2.2 New attributes in creation and edition ........................................................................................ 28
8.2.3 Programmable keys graphical view and management .................................................................. 29
8.2.4 Users mass provisioning ............................................................................................................ 30
8.3 OmniVista 8770 Web Configuration Application ................................................................................. 34
8.3.1 OmniVista 8770 Web Configuration interface .............................................................................. 34
8.3.2 OmniVista 8770 Web Configuration : Quick search and notification .............................................. 35
8.3.3 Comparison between OXE WBM and OmniVista 8770 Configuration via the web client .................. 35
8.4 OTC smartphone as single device..................................................................................................... 36
8.4.1 OTC smartphone as single device : creation ............................................................................... 36
8.4.2 OTC smartphone as single device : mass conversion of old configuration to new one .................... 37
9 NEW FEATURES IN OMNIVISTA 8770 R4.2 MD1 ..................................................................................... 38
10 NEW FEATURES IN OMNIVISTA 8770 R4.2 MD2 ................................................................................... 39
10.1 Components update ...................................................................................................................... 39

10.2 Certificates deployment by ToolsOmnivista ..................................................................................... 39
10.3 Bug Fixed on TLS 1.2 configuration ................................................................................................ 40
11 MISCELLANEOUS INFORMATION & RESTRICTIONS .............................................................................. 41
11.1 RTUM ........................................................................................................................................... 41
11.2 Users Application .......................................................................................................................... 41
11.3 Device Management (DM): ............................................................................................................. 42
11.4 OpenTouch Configuration .............................................................................................................. 44
11.5 OpenTouch/ OmniPCX Enterprise Synchronization .......................................................................... 44
11.6 Performance Application ............................................................................................................... 45
11.7 Re-Hosting .................................................................................................................................... 45
11.8 Audit ............................................................................................................................................ 45
11.9 Alarms .......................................................................................................................................... 47
11.10 OmniPCX Enterprise Object model: .............................................................................................. 47
11.11 OmniPCX Office and OXO Connect Configuration .......................................................................... 47
11.12 MSAD - Active Directory Synchronization & Light Client for User Provisioning ................................ 48
11.13 SNMP Proxy ................................................................................................................................. 49
11.14 CITRIX Presentation server .......................................................................................................... 49
11.15 OmniVista 8770 UTF8 Characters in Web Directory ....................................................................... 49
11.16 SECURITY: PKI ............................................................................................................................. 49
11.17 SECURITY : POODLE Vulnerability ................................................................................................ 50
11.18 SECURITY : SHA2 conformity ........................................................................................................ 50
11.19 8082 MyIc Phone on OmniPCX Enterprise and Https requests ......................................................... 50
11.20 VOIP quality supervision .............................................................................................................. 50
11.21 USERS application ....................................................................................................................... 51
11.22 Upgrade...................................................................................................................................... 51
11.23 Web Based Management .............................................................................................................. 51
11.24 OmniVista 8770 Web Based Management for OXE Configuration .................................................... 52

11.24.1 OmniVista 8770 Web Based Management for OXE Configuration : Restrictions .......................... 52
11.24.2 OmniVista 8770 Web Based Management for OXE Configuration: How to clear the OXE MIBs from
browsers........................................................................................................................................... 53
11.25 Multiple IP Plane ......................................................................................................................... 55
11.26 Mail Server ................................................................................................................................. 56
11.27 Manage My Phone ........................................................................................................................ 56
12 KNOWN PROBLEMS IN R4.2.14.00 ....................................................................................................... 57

1 GENERAL
This document describes the installation procedure for OmniVista 8770 version 4.2.14.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 (). 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: professional.services@al-enterprise.com or your local Services
representative).

2 CONTENT OF THE SOFTWARE PACKAGE
2.1 References
OmniVista 8770 software DVD for R4.2.12: 3BH11669ANAA
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
- 8770_4.2_am_adminmanual_8AL90703USAM
- 8770_4.2_im_installationmanual_8AL90704USAM
- 8770_4.2_am_securityguide_8AL90705USAJ
- 8770_4.2_am_snmpproxy_8AL90708USAH
- 8770_3.2.8_am_accountvoipticketscollect_8al90709usad
- 8770_4.1_am_apiusermanagement_8al90710usae
- 8770_4.1_am_rtu_metering_8AL90712USAH
2.2 Patches
2.2.1 Mandatory patches delivered

In the \Patches\Mandatory folder you will find the following patches:
8770.4.2.14.00
2.2.2 Anomaly Reports fixed in the patches
[1]
===========================================
Patch name : Patch_421400A_JAR_WAR_LDIF
Delivery date : 19Jan2021
===========================================
CR8770-11259 [Report]: Field Alignment issue for SetOf attribute in DSP parameter class.
CR8770-11248 AMILLAN LIMITED/ MSAD synchronization failed with an Exception
CR8770-11058 NTT Germany AG & Co. KG / WBM : How Works the Add Button in In Domain Configuration
and Administrator Configuration
CR8770-11266 keys are not removed from OxeDm sync Filter
[2]

===========================================
Patch name : Patch_421400B_DLL_WAR.zip
Delivery date : 27Jan2021
===========================================
CR8770-10998 RFP Solutions, Inc // East Windsor - 8770 Alarm Filters are sending alarms to the email id
even email id has removed for an Alarm filter.
CR8770-11307 SelfCare: Upgrade of 8770 from 4.2.13.01 to 4.2.14 must install Selfcare version 2.0.0
[3]
===========================================
Patch name : Patch_421400C_JAR_WAR.zip
Delivery date : 08Feb2021
===========================================
CR8770-11255 U-Com A/S/ 8770 - Problem with Web Service: Internal error. It is not possible to associate
devices using User or Device applications
[4]
===========================================
Patch name : Patch_421400D_JAR_EXE.zip
Delivery date : 19Feb2021
===========================================
CR8770-11177 ORANGE SA/ CALCULATE TOTAL TRAFFIC OBSERVATION COUNTERS - Base stations fails
CR8770-11171 NXO France SAS/ 8770 : Alarm server is going done when deleting 700X incidents
CR8770-10874 HELDELE GmbH/ OT User could not created via MetaProfile in case of numeric Login
credentials
[5]
===========================================
Patch name : Patch_421400E_EXE_LDIF.zip
Delivery date : 15March2021
===========================================
CR8770-11292 8770 : Restoration with rehosting failed when the server uses customer certificate
CR8770-11293 8770 : Backup doesn't contain custom certificate ( apache, ldaps )
CR8770-10812 8770 : error message "same alias" during the certificate importation
CR8770-10439 Web access fails after trying to install signed certificate => P12 file not correct
CR8770-10805 Impossible to insert clients' generated certificat
CR8770-11046 CA certificate deployement with toolsOmnivista (HFx3 provided)
CR8770-11126 same issue of CR8770-11125
CR8770-11347 8770-4.2.13- can't deploy certificate using the last hotfix provided in CR8770-11126
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.

2.2.3 Additional patches (mandatory)
2.3 License file

To install OmniVista 8770 and to access the various clients, you must have a specific license file for your
OmniPCX. This license describes the available modules.
In ACTIS, choose one OmniPCX Enterprise or Office or OCE and specify in its configuration that it is the
declaration node for the OmniVista 8770 server.
OV8770 release R1.0 R1.1 R1.2 R1.3 R2.0 R2.5 R2.6 R2.6.7 R3.0 R3.1 R3.2 R4.0 R4.1 R4.2
License version 1 2 3 4 5 6 7 7 8 9 10 11 12 13
Note During a R4.2 fresh server installation, the version 13 license is mandatory
During server upgrade: version 12 is acceptable. However, upgrade to version 13 will be necessary to
benefit from new features
During the OmniVista 8770 server running mode: versions 12 and 13 are accepted

2.4 Versions of embedded software
Component Version Comment
Apache 2.4.46
Apache Axis 2 1.6.2
Apache Ant 1.10.1
Wildfly 10.0.0
EJBCA 6.5.0.5 PKI Re-enabled
Installshield Premium 2015
Oracle Directory Server Enterprise 11.1.1.7.171017
PHP 7.3.11
OpenJRE(Azul) OpenJRE 8(Update Embedded in the software from
1.8.0_241) R3.2
See TC 2547 : OmniVista 8770 :

No impact of Oracle Java
announcement on OmniVista
8770
MariaDB 5.5.68.0
MySQL ODBC driver 3.0.9
Python 2.7.17
7 zip (7za – Command Line) 18.05
mariadb-java-client (JDBC driver) 2.4.2
Wodsftp.dll 3.8.5
NetSNMP 5.7.3
MindTerm 4.1.5
Plink 0.73
OpenSSL 1.1.1.7
gSOAP 2.8.69
Manage My Phone 2.0.0
This is not exhaustive

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

Windows 7 Professional SP1 Windows 2012 Server R2 Std Edition
Windows 8 Professional (64bits) Windows Server 2012 R2 DataCenter edition
Windows 8.1 Professional (64bits) Windows Server 2016 Datacenter, Standard
Windows 2012 Server R2 Std Edition (with desktop experience)
Windows 10 Professional and Enterprise(64bits) Windows 2019 Datacenter, Standard (with
Operating System Windows Server 2012 R2 DataCenter edition desktop experience)
Windows 2016 Datacenter, Standard (with
desktop experience)
Windows 2019 Datacenter, Standard (with
desktop experience)
1 processor Dual-Core (frequency near 2 GHz, 1 processor Quad-Core (frequency near 2,2
but dependent on the processor architecture) GHz, but dependent on the processor
Processor architecture)
Processor architecture equivalent or superior
to Haswell is required
RAM (minimum) 6 GB 8GB
7GB With License Manage My Phone 9GB With License Manage My Phone
Minimal
120 GB (disk: RAID5)
characteristics of 120 GB
15K rpm
Hard Disk
Graphics board 128 MB
Partition 1 NTFS partition for installation of the LDAP server
Browsers latest Google Chrome - Version 80.0.3987.100 (Official Build) (64-bit) (WBM, Directory web client,
qualified versions Manage My Phone)
Mozilla Firefox - Version 73.0 (64Bit) (WBM, Directory web client, Manage My Phone)
IE - Version 11.0 (Directory web client, Manage My Phone)
Drives A DVD drive is required
Warning Windows 7 and Server 2008 are no more supported by Microsoft, thus there is no more support from ALE
on OmniVista 8770 issues linked to Windows 7 and 2008

Warning
Due to the Apache release and Visual C++2015 redistributable, the following hotfixes and service packs
are mandatory.
Operating System Service Pack or Hotfix Installation

Windows 7 – Windows 2008 R2 SP1
Windows 8.1 – Windows 2012 R2 KB2919442 replaced by The installation order must be done as
KB3021910 – KB2919355 follows :
KB3021910
KB2919355
KB2999226
All OS except Windows 10 KB2999226
Note  From 50000 subscribers, you need the agreement of ALE International (process PCS – Premium
Customer Support).
 From 100 nodes or PCS, you need the agreement of ALE International (process PCS – Premium
Customer Support).
 For Accounting, the maximum number of tickets is 30 million.
 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.
 If you encounter slowness on the OmniVista 8770 server, it can be due to Windows Defender
antivirus scan of Windows 2016
Workaround : Configure the OmniVista 8770 folder as an exception
Note The number of simultaneous thick client connections is limited to 30
3.1.2 Virtualization requirements
OmniVista 8770 has been validated in a VMware ESX® environment and Microsoft Hyper-V®.
Refer to the OmniVista 8770 R4.x Capacity Planning tool published on the Business Portal for minimum
requirements.
The hyper-threading option should not be validated on the VM.

3.1.3 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.4 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\
The name of the computer must NOT include the following characters:
«/ \ [ ] “ : ; | < > + = , ? * _ ».
3.1.5 Servers delivered by Alcatel-Lucent
As of the October 19, 2020 Offer, the server rack Platform 3-4 reference 3BA27817EN and 3BA27818EN are
no more delivered with Windows 2012 R2 and Windows 2016 in English, preinstalled. Only the Server rack
Platform 3-4 reference 3BA27769AA is available in stock permitting, without Windows.
OmniVista 8770 application is not preinstalled and has to be installed according to the present release note
and installation guide.
For more details on the server 3-4, the detailed Bill Of Material (BOM) can be found in the cross
compatibility document reference: ENT_MLE_033442, published on the Business portal.

3.2 PCX compatibilities
Warning
ICS is no more supported from OmniVista 8770 R3.2
3.2.1 IP & IP/X25 connections to OmniPCX Enterprise
From OmniPCX Enterprise R6.0 till R12.x and all associated OmniVista 8770 releases the IP connection or
IP/25 connection is ok
Warning
PPP connection is not supported.
OXE Releases OV8770 Releases

R8.0 >= R1.3
R8.0.1 >= R1.0
R9.0 >= R1.0
R9.1 >= R1.0
R10.0 >= R1.0
R10.1 >= R1.1
R10.1.1 >= R1.2

OXE Releases OV8770 Releases
R11.0 >= R1.3
R11.0.1 >= R2.0
R11.1 >= R2.5 & R2.6
R11.2 >= R2.6.7
R11.2.1 >= R3.0
R11.2.2 >= R3.1
R12 .0 >= R3.2
R12.1 >= R3.2.08
R12.2 >= R4.0
R12.3 >=R4.1
R12.4 >=R4.2
Warning : OmniVista 8770 <= R4.0 are no more supported

OmniPCX Enterprise <= R12.1 are no more supported
3.2.2 OpenTouch
OT Releases Software version equal to or higher than … OV8770 Releases

R1.0.1 1.0.100.040 >=R1.0
R1.0.1 1.0.100.060 >=R.1.1
R1.1 1.1.000.080 >=R1.1
R1.2 1.2.000.051 >=R1.2
R1.3 1.3.000.061 >=R1.3
R2.0 2.0.000.90/2.0.100.32/2.0.200.4x >=R2.0 and R2.5
R2.1 2.1.000.092 >=R2.6
R2.1.1 2.1.100.042 R2.6.7
R2.2 & R2.2.1 2.2.017.009 R3.0
R2.2.1 2.2.110.0022 / 2.2.120.003 / 2.2.130.003 / R3.1
2.2.140.005
R2.3 2.3.013.002 R3.2
R2.3.1 2.3.109.004 / 2.3.110.004 R3.2.08
Min R2.3.1 2.3.109.004 / 2.3.110.004 R4.0
R2.4 tbd R4.0
OTMS/OTMC / R4.1
R2.5
OTMS/OTMC / R4.2
R2.6

OpenTouch <=R2.3 are no more supported

3.2.3 OmniPCX Office and OXO Connect
OmniPCX
Office
OV8770 Releases
RCE Software version equal to or higher than …
Releases
5.1 510/070.001 or 510/071.001 (wrong call duration fix) >=R1.2

9.0 Not supported – upgrade to 9.2 >=R1.2
9.2 920/089.001 >=R2.0
10.2 Not supported – upgrade 10.3 R2.6.7
10.3 103/009.002 – recommended: last maintenance version >=R3.0
103/024.001
OXO
Connect
Releases
2.0 02.0/016.003 >=R3.1
2.1 02.1/021.001 >=R3.2
2.2 02.2/012.001 >=R3.2.08
2.2 02.2/012.001 >=R3.2.08.09
3.0 03.0/012.001 >=R4.0
3.1 03.1/007.001 >=R4.1
3.2 03.2 / >=R4.1.12
4.0 04.0 / - OCE R4.0 >=R4.2

OmniPCX Office is no more supported
OXO Connect < 2.2 is no more supported
See cross compatibility

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 No specific lock for OmniPCX Enterprise.
Enterprise
OmniVista 8770 modules OpenTouch locks Description

Configuration OAMP_CONFIG Configuration GUI
Alarms OAMP_ALARMS Alarms sending
Performance OAMP_VOIPPERF VOIP tickets sending (not used anymore since
removal of Vital)
OAMP_PERFKPI and SNMP data sending

mlsnmp
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.
RAM 4 GB or higher
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)
Browsers latest qualified Google Chrome - Version 80.0.3987.100 (Official Build) (64-bit) (WBM,
versions Directory web client, Manage My Phone)
Mozilla Firefox - Version 73.0 (64Bit) (WBM, Directory web client, Manage My
Phone)
IE - Version 11.0 (Directory web client, Manage My Phone)
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.
The use of Clients installed on a Citrix server is not possible when we manage OmniPCX Office nodes. The
OMC tool is not compatible with Citrix.
Warning
Windows 7 is no more supported by Microsoft, thus there is no more support from ALE on OmniVista 8770
issues linked to Windows 7

4 INSTALLATION AND UPGRADE
4.1 Installation
- 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 or Windows 8, 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.
- OmniVista 8770 server Installation should start with the User Account Control (UAC) setting level “Do not
notify “in Windows 7 professional machine.
- Help Online: To view the PDF file in the browser it’s required to have the PDF reader add-on. If not it
shows file download prompt as below.
- From OmniVista 8770 R3.0.13.00.c , new password policy has been introduced and the policy is
applicable for all the password changes which happen during the first login/ password resets. This
password policy is not implemented during installation under 8770 InstallShield.
- 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 you use 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 (443) because they are required by
SIP device management. The port 443 has as well to be available for Apache.

Warning During the installation, OmniVista 8770 checks the KB3021910 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 before.
- From Windows 2016, to avoid general slowness add < 8770 folder > in Windows Defender settings (refer
CR8770-8161 : Infrastrusture : general slowness due to Windows Defender with windows 2016)
- Windows 2019 / 2016

 In Windows 2019 and Windows 2016; windows start menu - OmniVista 8770- 'OmniVista 8770 client'
and '8770 Diagnostic' - Right click contextual menu doesn't display - Run as administrator' option.
Only 'open File location' would be shown.
 However, for other apps like 'ServiceManager' 'Dict customization' Right click contextual menu - Run
as administrator' option would be available.
 The user has to execute the 'OmniVista 8770 client' and '8770 Diagnostic' with 'Run as administrator'
from the specific file locations. There Right -click - 'Run as administrator' option would be available.
 Apparently in Windows 2019 / 2016 'batch file' and vbs file in the start menu - there is no 'run as
administrator' option. For exe 's option 'run as administrator' is available.
 In windows 2012, there seems to be no such behavior. 'OmniVista 8770 client' and '8770 Diagnostic' -
Right click contextual menu - Run as administrator' option is available.

- Manage My Phone informations:
o Minimum supported version for Manage My Phone application is .Net 4.0

o For Windows 7 machine .Net 4.0 must be installed manually to make Manage My Phone
application operational.
o End user with Manage My Phone application cannot manage MultiLine and supervision set, both
the functions are removed from the drop down list of programable keys.
o From OmniVista 8770 the Admin can able to manage all the functions in the programmable keys
for all the users.
o After the upgrade from R4.0/R4.1 server to R4.2 version, the Manage My Phone application
rarely shown as disabled stage- By killing the Zulu platform application in windows task manager
the services will be triggered to start mode and service will up.
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.5 releases 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 R4.0. The data have to be processed before the upgrade.
The upgrade to OmniVista 8770 R4.2 is available from version 3.2.08 (version = 10 in the license). It is
mandatory to update the server in the latest maintenance release before upgrading.
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.
For OmniVista 8770 servers with a version < 2.0 (version < 7 in the license), the recommendation is to do a
new installation. Direct upgrade is not available, it is necessary to upgrade following the migration paths
below :

Possible Migration Path
Source Release Target Release

R2.0 R2.6.7
R2.x R3.0
R2.6.7 R3.2
R3.0 R3.2
R2.6.x R4.0
R3.x R4.0
R3.x R4.1
R4.0 R4.1
R3.2.08 R4.2
R4.x R4.2
Reminder: OmniVista 8770 versions <= R3.2 are no more supported.
You can create an eSR to get an intermediate license with the current OmniVista 8770 license and the
confirmation of the order of the Target OmniVista 8770 license 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
- Then accept the next proposals.
Nota : From OmniVista 8770 R3.2.08, web client via java applet is no more available
Cf : OmniVista 8770 WBM

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 must
be deleted before starting a new installation.
In case of server un-installation failure, it could be necessary to remove some registry keys. This can be
done using the script 8770Cleanup.vbs from the DVD folder Tools\8770Cleanup.

6 MIGRATION FROM OmniVista 4760 R5.2
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.
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)” must be equal to “Loaded records”)
For the complete migration procedure, refer to the Installation Manual.
Warning __________________________________________________________________________________________
As of the April 2019 offer, the OmniVista 4760 R5.2 license and DVD are no longer configured in ACTIS
and are removed from the catalog.
__________________________________________________________________________________________
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.
Then import the entries which were exported during step 1

7 SPECIFIC MANAGEMENT
7.1 Users management and OmniPCX Enterprise 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.
7.2 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.
 Restore the saved data using the OmniVista 8770 Maintenance application. Select the “Restore with
rehosting” operation.
A Restore with rehosting operation has also to be launched when the server IP address has been changed.
7.3 MSAD synchronization and CMISE security

In the case where a secured access for configuration is managed for an OmniPCX Enterprise 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.
Note
The MSAD plug-in must be regenerated and installed again on the Active Directory server after rehosting.
Warning
The password of the account MSAD8770Admin must not be changed in the Security application.
Note
The account declared in Active Directory server must be a member of "Admins group".

7.4 Backup on network drive
Network drives can’t be seen from Maintenance application.
A network backup location must be identified by its own UNC ().
The Security guide describes the preliminary operations management for the backups on network drives.
7.5 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.
For users creation from the MSAD Web client, the OmniVista 8770 server name has to be inserted in the
Trusted sites list.

Warning
Languages can be downloaded on BPWS

8 NEW FEATURES IN OMNIVISTA 8770 R4.2
OmniVista 8770 R4.2 is a major release and includes the following features :
• Centralized management of OmniPCX Enterprise up to R12.4, OpenTouch Multimedia Services and Message
Center up to R2.6, and OXO Connect/OCE up to R4.0
• Users mass provisioning via the web client
• Graphical interface for DeskPhones keys management from the web client
• New features in the web client for OmniPCX Enterprise users: Add in a hunting group, update language,
secret code, lock, do not disturb, manage forwarding
• Full configuration of multiple OmniPCX Enterprise systems via the web client
• Compatibility with Windows Server 2019
8.1 Compatibility with Windows Server 2019

OmniVista 8770 server and client can be installed on Windows Server 2019 Standard and Datacenter.
AD plugin installation on an Active Directory instance can be hosted by a Windows Server 2019.
AD Client from an Active Directory instance can be hosted by a Windows Server 2019.
SNMP proxy is compatible with Windows Server 2019.
8.2 Users application in the Web Based Management (WBM) enhancements
8.2.1 New pagination in the navigator

In order to navigate easily in the grid results from page to page, the pagination is configured in the Grid
configuration menu.
The number of rows displayed in the grid is limited by a setting, configurable from the Settings menu. It
applies to the display of the entries of a level selected from the tree and the display of search results.
Up to R4.1, when the number of entries exceeds the grid limitation, the “More” action (> button) searches
for a new bulk of entries but adds them to the grid below the previous set of results.
From R4.2, when the number of entries exceeds the grid limitation, the “Next” operation (> button)
searches for a next bulk of results (grid limitation still applicable) and displays them in a new grid (only the
new set of results). A “previous” operation (< button) allows to come back to the previous set of results,
and only them.
A “first page” operation (<< button) displays the first set of results in a new page, while the “last page”
operation (>> button) displays the last set of results.

The “sort/reorder” operation and a global re-calculation of all the pages are available. As a result, a new
first page is displayed whatever the page displayed at the time of the sort request.
Restriction: multi-selection of users (to delete or to export) over several pages is not supported
8.2.2 New attributes in creation and edition

New attributes are available in Users application, in creation and update mode so that there is no need to
switch to the OXE Configuration application for these attributes.
Those attributes are located on Details tab of a user :
 Synchronized attributes showing current values or status in OXE before any modification :
- Hunting group
- Language
- Secret code
 Non synchronized attributes never showing current values or status in OXE before any modification :
- Lock
- Do not disturb
- Forward type and forward directory number
The limits are :
 Dynamic state of the user is not visible before applying non synchronized values
 Selection of hunting groups and language are only possible when objects managed from OXE
configuration first (thick client)

8.2.3 Programmable keys graphical view and management
This feature provides the ability to manage the keys for the IP Touch sets, in update mode only (meaning
once the user is created on the OXE).
The list of the supported deskphones is :

 IP Touch 8028s / IP Touch 8058s / IP Touch 8068s / IP Touch 8078s
 8019s
 IP Touch 8008 / IP Touch 8018 / IP Touch 8028 / IP Touch 8038 / IP Touch 8068 / IP Touch 8082 / IP
Touch 8088
 8029 / 8039
 IPTouch 4008 / IPTouch 4018 / IPTouch 4028 / IPTouch 4038 / IPTouch 4068
 4019 / 4029 / 4039
 4003 / 4004 / 4010 / 4011 / 4012 / 4021 / 4023 / 4034 / 4035 / 4036 / 4040
 4302 / 4302 / 4321
Just by enabling the parameter as below, the programmable keys management is available for the main and
secondary sets.

• Forbid the management of custom views for local administrators with Users and Users and Directory
configuration access rights. Custom views management is authorized for local administrators with
Delegation rights.
8.2.4 Users mass provisioning
This feature is the import / export of users from the Users application in the WBM.
The content of the file reflects the GUI as defined by the logged in administrator, meaning the custom view
assigned to the administrator is used to build the template file, export the user data and control the import
validity.

In the same manner, the management domain membership of the administrator restricts the scope of the
export and import operations.
8.2.4.1 Mass provisioning - Export
The administrator can export the users selected from the grid, from a branch or sublevel
(immediately/locally).
In case of a branch, this operation can be planned via the scheduler.

8.2.4.2 Mass provisioning – Import
The same way as export, it is possible to import users file (immediately or via the scheduler).
As in the thick client, import mechanism includes the action to create, update or delete users and devices.
Create is converted as Update if user already exists. Update is converted as Create if user doesn’t exist.
Limitation compared to the OmniVista 8770 thick client:

 Can’t remove devices from users
 Can’t remove OT applications from Connection users
 Mass provisioning file generated from thick client cannot be used in WBM and vice-et-versa

8.2.4.3 Scheduled Import and Export actions
From WBM, it is possible to schedule users importation and exportation.
Scheduled users import:
From WBM and as on the scheduled application in thick client, it is possible to follow the execution getting
the status with the appropriate log file accessible via the browser.

8.3 OmniVista 8770 Web Configuration Application
8.3.1 OmniVista 8770 Web Configuration interface
As previously in release 4.1, the authorized administrators can access to the Users application via the
OmniVista 8770 web client.
From release 4.2, the global administrators with Configuration access right can also access to the OXE
configuration via the web client.
Users WBM
Users WBM
Web
Configuration
Application
OXE configuration
Connection to the Web Configuration application is possible via a standard administrator credential
(management domain feature disabled) or a global administrator credential (management domain feature
enabled) with Configuration rights.
Local administrators cannot launch OmniVista 8770 web configuration application, even if they have
configuration rights
Remark : OmniVista 8770 license « OXE management » and « Configuration » are needed.
A click on the “Configuration” icon gives the access to the Web Configuration application :
 Display networks, sub-networks, OXE nodes

 Tree navigation by expanding/closing levels or with breadcrumb
 Quick/advanced search of network elements with display of the result in grid
 Notification of errors thanks to toaster and notification list
• Connection to several OXE nodes

8.3.2 OmniVista 8770 Web Configuration : Quick search and notification
OXE WBM provides 2 new features :

- Quick search of the exact string matching the searched instance (as per the naming attribute)
Remark :The advanced search is not available for the moment
- Notification of errors and successful DELETE only

Remark : The successful CREATE, UPDATE and SEARCH operations are not notified
8.3.3 Comparison between OXE WBM and OmniVista 8770 Configuration via the web client
From the R4.2, the connection to the OXE configuration can be made via the OmniVista 8770 web client.
The application embedded in the OmniVista 8770 server is different from the OXE WBM embedded in the
OXE, even if the look and feel is similar :
- HTTPS between WBM client and OmniVista 8770 server (REST API)
- CMISE / CMIP protocol to exchange data between OmniVista 8770 server and OmniPCX Enterprise,
same as from thick client
- Download of the MIB at first connection and stored locally on Browser
- The same connectivity types as thick client are supported
- All node redundancy types are supported
- OXE management domain feature is supported
- Access profiles are supported and configured via the thick client

8.4 OTC smartphone as single device
This feature concerns the deployment of OTC Smartphones as main and unique devices for OTCt users.
Currently when an OTCt user owns only an OTC Smartphone device, the usual configuration is to declare a
tandem configuration, where main set is a SIP Extension and secondary set is a Remote Extension associated
to the OTC Smartphone. The SIP extension is put in Out Of Service and is used by OT to route the calls
properly.
As a simplification for provisioning and a reduction of license costs, the goal is to declare only a Remote
Extension in OmniPCX Enterprise, to associate the OTC Smartphone to this OXE subscriber and to get rid of
the extra SIP Extension.
Due to some OmniPCX Enterprise constraints, a Remote Extension can’t be the main device of any multi-
device configuration. As soon as an OTC Smartphone is associated to a main Remote Extension, it is the
main and unique device of the user. Thus, the OTC smartphone cannot be multidevice.
From OmniVista 8770 perspective, when the manual configuration in several steps is already possible, the
request is to allow the creation of the OTCt user with his unique device in one step, from Users application –
thick and WBM clients.
Note : The OpenAPI is not updated to support the creation of the user and its unique device in one step
when using a free number range : such a provisioning is still possible in several steps. Anyway, the creation
in one step is possible when the user of Remote Extension type is created with an explicit directory number,
duplicated for the Remote Extension associated to the OTC Smartphone.
Note : The evolution of this configuration has impact on RTU KPI.

 Up to OT 2.5 or with a SIP Extension/Remote Extension : the out of service SIP Extension is counted
with KAT010 – STD USER SIP DEVICE RTU and the OTC Smartphone is counted with KAT023 –
UNIVERSAL CLIENT OPTION RTU. The Remote Extension is not counted as secondary device of a
tandem configuration
 OT 2.6 or with unique Remote Extension : the Remote Extension is counted with KAT048 –STD USER
CELLULAR DEVICE (main and unique Remote extension) and the OTC Smartphone is counted with
KAT023 – UNIVERSAL CLIENT OPTION RTU : this means that such a user is still counted twice
8.4.1 OTC smartphone as single device : creation
After user+device creation, the remote extension number is the main user’s directory number.
There is a new predefined view for creating a Connection user with OTC smartphone as single device named
“OXE User with OTCsmartphone main”.

8.4.2 OTC smartphone as single device : mass conversion of old configuration to new one
Suppose that a lot of users with mobile as single device have been configured according to old configuration
in previous releases.
OmniVista 8770 R4.2 documentation provides a procedure to convert them to the new configuration.
This procedure is based on mass pro import/export functions available in Devices and OXE Configuration
applications of OmniVista 8770 thick client :
From Devices application, export OTC Smartphone entries to be converted in simple mode 
otcsmartphone.csv
Save a copy of the file before update
Disassociate the devices : update the devices file (otcsmartphone.csv) by adding the operation
“Disassociate” as 1st column of each data line and import the updated otcsmartphone.csv file from Devices
application.
The devices are disassociated, the associated entries are automatically deleted on OXE (Remote extension,
SIP device, Abbreviated number, ARS route, …) and the remaining SIP extensions are removed from tandem.
From OXE Configuration, export the SIP extensions to be converted in prg format  sipext.prg
Save a copy of the file before update
Delete the SIP Extensions : update the extensions file (sipext.prg) by adding the – operation as 1st column of
each data line and import the updated file
Create the Remote extensions : update the extensions file (sipext.prg) by adding the + operation as 1 st
column of each data line, replace SIP_Extension by Remote_Extension in the Station_Type column, clear the
Secret_Code column (ie remove ****) and import the updated file.
The Remote extensions are created with same directory number as the previous SIP Extensions
From Devices application, associate again the OTC Smartphone to the user : update the devices file
(otcsmarphone.csv) by adding the “Associate” operation as 1st column of each data line and update the
“Remote extension directory number" (last column) with the new Remote Extension directory number and
import the updated otcsmartphone.csv file from Devices application.
The device is associated as unique device to the user who keeps his company phone number, login, email,
call log and contacts.

9 NEW FEATURES IN OMNIVISTA 8770 R4.2 MD1
No new features in R4.2 MD1 – Only Bug Fixing

10 NEW FEATURES IN OMNIVISTA 8770 R4.2 MD2
10.1 Components update

 APACHE 2.4.46
To solve Vulnerability issues identified in APACHE 2.4.41 (OmniVista 8770 R4.2.12)
 MariaDB 5.5.68
MariaDB 5.5.68 is a maintenance release which contains following updates and bug fixes:
 HeidiSQL updated to 11.0 (MDEV-22032)
 Unregister of slave threads disconnected before COM_BINLOG_DUMP (Bug#29915479)
 Server can fail while replicating conditional comments (Bug#28388217)
 Fixes for the following security vulnerabilities:
 CVE-2020-2752
 CVE-2020-2812
Please refer to MariaDB release note for more information https://mariadb.com/kb/en/mariadb-5568-release-
notes/
 Manage My Phone 2.0

Manage My Phone 2.0 contains fix for Supervision keys and programmable keys which are no more
manageable
Manage My Phone 2.0 includes Tomcat 8.5.57 to solve vulnerability issues
10.2 Certificates deployment by ToolsOmnivista
The Certificate installation and deployment had major issues. Several of them were design issues in the
implementation. Some of the issues found were difference of understanding on how the certificates were
deployed at the customer place. Using the previous fixes and the patches delivered in 4.2 MD1 and previous
hot fixes, several certificates were deployed.
A procedure to deploy certificates using ToolsOmnivista (Apache & LDAPS) is needed to clean up before any
more new certificates is installed/deployed. The certificates installed using the old patches delivered in 4.2
MD1 and previous releases has some basic design issues which prevent removal of certificates from oracle
server DB and hence it is needed to follow this procedure to clean up and bring the system back to self-
signed certificates before any more Certificate is installed deployed using the new patches.
For complete explanation, please refer to the Technical Communication:

TC2599en_authenticated_certificat_deployment (edition 2)

10.3 Bug Fixed on TLS 1.2 configuration
 CR8770-11107: After migration 4.2.13.01, the Apache loses its TLS configuration
e.g.: in 4.1.14.00, the TLS is configurated in TLS 1.2 on LDAPs and Apache. After migration in 4.2.13.01,
LDAPs keeps its configuration in TLS 1.2 but Apache goes back to the default configuration (TLS 1.0 and
upper)
 CR8770-10890: in 4.2.13.01, after configuration in TLS 1.2 via toolsOmnivista, Apache doesn’t start
anymore
 CR8770-10892: in 4.2.13.01, configuration in TLS1.2 doesn’t work on Wildfly
 CR8770-10899: 8770 PKI application (EJBCA) is unusable

11 MISCELLANEOUS INFORMATION & RESTRICTIONS
Note
All the “CR8770-…” 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 miscellaneous information about applications, components that could be
useful plus some restrictions.
11.1 RTUM
The Russian Govt has changed the Timezone from utc+3.00 to utc+4.00 because of which there would be a
delay of an hour in RTUM counter calculation. To solve the issue Microsoft has recommended the patch
Windows8.1-KB3162835-x64 to be installed to bring back the time zone in utc+3.00 after which the RTUM
counter calculation will be ok.
11.2 Users Application

General Information:
 During user creation with Meta profile more number of attributes are made editable from R 4.1.
 To create OmniPCX Enterprise/ OpenTouch Connection users based on profiles, OmniPCX Enterprise/
OpenTouch synchronization needs to be performed first, to get the OE/OT profiles in Users Application.
 Option ‘Export for Rainbow’ is introduced in contextual menu at root and department level and new
preference rule in preferences menu is introduced to support mass provisioning of Rainbow users.
Refer help document for Loginmail syntax in rainbow preference rules.
Ex: Firstname_lastname@Domain.com
 A mandatory attribute “OXE Profile Name” has been added for OpenTouch Connection User creation in
the Users Application. This attribute is populated by selecting an entry from a drop down. In order for
the drop down list to be populated, the profile(s) need to be created in the OXE associated with Site
being used for OpenTouch Connection user creation and then synchronized.
 Admin creates a metaprofile for connection users with a free number range. This free number range is
previously created in OXE configuration :
Max.number parameter is very sensitive : it limits the number of first free directory numbers
returned by OmniPCX Enterprise when a consultation is requested. If admin sets a very high value by
ignorance or by thinking that this is the range size (possible misunderstanding), the consultation
time increases a lot.
Example: the time to get the first 3000 free number range is about 3-4 seconds.
The problem is that such consultation is done during the creation of a connection user creation from
a metaprofile. Several seconds can be easily wasted because of a too high Max.number parameter.

Workaround:
o The recommendation is to set 10 or even less. In such case, the consultation of free directory
numbers is immediate and the user creation is therefore optimized.
Restriction:
 Memory limit exceeds with OXE user search of more than 1K users. Refer : CR8770-6607
11.3 Device Management (DM):

 Configuration of remote settings feature is now enhanced for 8008, 8018 and 8028s devices along
with 8001 device. And test scenarios are executed with simulated reverse proxy.

 8001 set in Vlan environment
(KCS article 000046893)
Issue :
After upgrade from a release < 3.2.08.09 to a recent release, the 8001 set cannot put in service
anymore if this set belong to a VLAN
Solution:
The solution is to manage the VLAN config in OmniVista 8770 (the security tab of the set). Further
details, See technical alert TC2640
 No more support for MIC Android, MIC Blackberry, MIC Windows and MIC Nokia mobile devices.
 Secure download of OTC PC configuration file from 8770/data/DM/deploy to OT node takes 15

minutes Maximum, in case administrator requires immediate transfer of configuration file, enable
immediate transfer option from Administration Application->Application Configuration->Application
Settings->Device Management->OTCPC_DEVICE-CONFIG->Enable Immediate transfer
 For overall Terminals tests performed in OmniVista 8770 with “device profile” has given the status
below:
Without
Profile(Normal With
Device Node Deployment) Profile Binary used for the testing
VHE(8082) OXE OK OK R300_01_15_18.zip
VHE(8082) OT OK OK R300_01_15_18.zip
MyICphone_8002_8012_R110_
VLE (8002/8012) OXE OK OK 03_059_0.zip
MyICphone_8002_8012_R110_
VLE (8002/8012) OT OK OK 03_059_0.zip
8001 OXE OK OK 8001-R200.4.2.0.8.zip
8008 OXE OK OK 8008-SIP-R400_1.20.41.zip
8018 8018-SIP-R300_1.15.20
8028s 80x8S_SIP_R300_1.15.20
8068/
8038 OT OK OK 8068_R220_3_31_30.zip
8088_R304.03.014.1.2457-
8088 OT OK OK signed.zip
OXE :
8088-R304.03.014.1.2457-
8088 OXE OK OK signed.zip
OTC-android-smartphone-
OTC smart phone OT 2.911.05.0.apk

Restriction:
 Configuration file is not updated with subscriber key information when OXE user is created with SIP
extension along with subtype as IPtouchxx.
11.4 OpenTouch Configuration

 OpenTouch node number entered during the OpenTouch declaration should be numeric value.
Otherwise the topology synchronization with the Performance application will fail.
 Templates Tab is changed to Profiles in OpenTouch Configuration object tree.
 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 OmniPCX Enterprise
with OTVM users.
 The connect operation of OpenTouch from OmniVista 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 OmniVista 8770 server is
installed
- Restart of Wildfly 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 ease 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.
11.5 OpenTouch/ OmniPCX Enterprise Synchronization

 User name for template management should be filled in the connectivity tab to get the templates
during synchronization.
 After declaration of OmniPCX Enterprise node, OmniPCX Enterprise Complete Global synchronization
will not synchronize associated OpenTouch node. OpenTouch node should be synchronized first.
 TUI voice mail should be declared in both OmniPCX Enterprise and OpenTouch for successful
complete global synchronization.
 OpenTouch synchronization may get fail with Error invoking web service after upgraded to
3.2.8.X.(possibility of occurrence is very low) Even if restart of wildfly service is not solving the
issue.
Workaround: Change LDAP Directory manager password. From OmniVista 8770 tools
OmniVista.exe select password change (option 1)-> LDAP directory manager password
(option 2)->Enter new password and restart the system.
11.6 Performance Application

OmniPCX Enterprise and OmniPCX Office VoIP performance is now taken care of by NMC loader and other
legacy applications. OpenTouch VoIP tickets are not handled.
11.7 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-with-
administrator-privileges.htm
11.8 Audit
 After enabling the Global flag for audit process the OmniVista 8770 client needs to be restarted to get
the information of OmniVista 8770 login/logout
 Audit detailed system records will not be displayed in OmniVista 8770 with OmniPCX Enterprise
releases>=M1
Refer CR8770-6606: 8770 R3.2.08.04: Audit system details are not available in audit application for
OmniPCX Enterprise>=OXE 12.
 Restriction :
Since the OXE release R12 (M1.403), detailled informations about “LOGIN” action are not available
Option “more detail” = no has to be selected
Reason : In the OXE release R12, new package has been deployed (due to a vulnerability issue) on OXE.
This new package does not update the “auth.log” file with the PPID.
So the detailed information presents in the “shell.log” file cannot be displayed anymore

detailed informations :
Before OXE release R12 :
Since the OXE R12 :

11.9 Alarms
Restrictions :
- OpenTouch Alarms will not be received if two OpenTouch'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.
11.10 OmniPCX Enterprise Object model:

 OmniVista 8770 Help files are integrated with this build.
 OmniPCX Enterprise M5 help files are integrated with this build.
 OmniPCX Enterprise Native Encryption Feature

The OmniPCX Enterprise Native Encryption Feature can be activated only when Native Encryption
license is available from OmniPCX Enterprise side(Max license users -1500) Also the feature will not
be activated by default need to be changed the Native encryption and Enable automatic CTL
Acquisition parameters set as True and do create the CA certificate and define the IP details in
lanpbxbuild comment.
11.11 OmniPCX Office and OXO Connect Configuration

 License to be added manually for the OXO version based on the CPU (OmniPCX Office Board) for
major upgrades
 OXO connect and OXO connect evolution has separate binaries need to be considered during the
install
 For OmniPCX Office binary downloads the LOLA software is not required for OXO connect
evaluation, whereas OXO connect installation no change
 OXO connects & Evaluation Input and Output performs only via OMC. It should install in the local
server where the OmniVista 8770 server is running
 OmniPCX Office synchronization restriction (only synchronization happens with single OmniVista
8770 user using permanent IP connectivity alarm reception mode. Multiple Permanent IP

connectivity with multiple OmniVista 8770 user for single OmniPCX Office synchronization is not
allowed for OmniPCX Office
 Backup and Restore for OmniPCX Office not allowed from configuration. Now it is part of
maintenance application.
 OmniPCX Office backup directory needs to be mounted for configuring OmniPCX Office in
online/offline mode.
 OmniPCX Office 3.1 alarms are integrated.
Restriction:
 OXO Cloud Connect alarms are not received. Refer crqms00207552

 OmniPCX Office R2.1 Alarms updated for Rainbow not received in OmniVista 8770 Refer: CR8770-7086
 During the 1st time of OmniPCX Office & OMC configuration/synchronization, need to restart the system
to avoid the “OMC Stopping the Management services” failure message in status bar update area.
11.12 MSAD - Active Directory Synchronization & Light Client for User
Provisioning
 MSAD Sync: During the MSAD Access Info Configuration, the entire user Dn (Example :
Cn=ladmin,CN=Users,DC=Company X,DC=com)needs to be entered instead of the username
alone.
 MSAD: Metaprofile list is coming out of the application screen if you double click on it; Refer:CR8770-
7640
 AD Web Client: Page refresh not happening after OmniPCX Enterprise/OpenTouch 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: OmniVista 8770 Administrator is not allowed change the default password assigned to the
MSAD8770Admin account. Changing the password will make AD Client inoperable.
Workaround : If MSAD Admin password is changed then restart the Wildfly service in OmniVista 8770
server.

11.13 SNMP Proxy
 After OmniVista 8770 Install/upgrade, enable Windows SNMP service and then perform OmniVista 8770
SNMP Proxy configuration from ToolsOmniVista.
 If Windows SNMP service is already installed then OmniVista 8770 SNMP Proxy configuration must be
done after installation/upgrade from ToolsOmniVista.
 External tools like TrapReceiver and iReasoning MIB Browser should not be installed to receive the traps
from the OmniVista 8770 server side rather we could install them in the client side machines.
o These tools by default take the port number 162 and due to this OmniVista 8770 will not receive
OpenTouch Alarms. This may be due to the port conflict between these two.
11.14 CITRIX Presentation server

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

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
OmniVista 8770 management platform and all the connected elements (OmniPCX Enterprise/OpenTouch) as
well as an external corporate directory,from all the OmniVista 8770 applications, Users as well as
Directory, ... WebDirectory included, in both ways, meaning from OmniVista 8770 to other elements as well
as from network elements to OmniVista 8770.
The requirement is driven by the capability of the UA/NOE device to display non ASCII characters and the
OmniPCX Enterprise 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 OmniVista 8770 and OpenTouch, priority is given to UTF8 names, meaning UTF8 names are used
preferably, at least in all Directory-based applications.
11.16 SECURITY: PKI

For remote clients Certificate can be access from OmniVista 8770 Server.
Ex: https://<FQDN>:8443/certificates/
Download superadmin certificate from OmniVista 8770 server C:\8770\Ejbca\p12 and import to local
browser

11.17 SECURITY : POODLE Vulnerability
SSL v3 is now replaced by TLS for encryption for this POODLE vulnerability. So earlier
components which were using SSLv3 like LDAPS, WebClient, WebDirectory will now be using TLS for
encryption.
Menu item added in ToolsOmniVista to enable/disable SSLv3. If SSLv3 is disabled then TLS is enabled.
11.18 SECURITY : SHA2 conformity

SHA2 certificate would be installed by default during fresh installation of OmniVista 8770
For OmniVista 8770 upgrades from R2.6 SHA1 certificate would only be available. If administrator wants to
migrate to SHA2 he should use toolsOmniVista.exe
11.19 8082 MyIc Phone on OmniPCX Enterprise and Https requests

Http requests from 8082 MyIc Phone to OmniVista 8770 server are no more supported from OmniVista 8770
R2.6.7.8.
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
Refer to KCS article “000040438 : 8770- Directory client consultation via WEB : Invalid certificate.”
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 VoIP reports are only available for OmniPCX Office and OmniPCX Enterprise (version superior or equal to
8.0)

11.21 USERS application
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.
11.22 Upgrade
Warning Case of an upgrade with a local client already started ! it is mandatory to check that all the clients are
stopped !!!
Recommendation : if possible, reboot the server before doing the upgrade
11.23 Web Based Management
 The OmniVista 8770 WBM Client is focused on the Users, Departments, Mass Provisioning, Scheduled
Reports, Configuration of Administrators, Customizing the views for different Administrators & Domain
Management and OmniPCX Enterprise Configuration
 Customizations of GUI and integration of other applications are planned in Future releases of OmniVista
8770
 OmniVista 8770 WBM is accessible in Google Chrome & Mozilla Firefox browsers
(Cf 3.3 Prerequisites for administration Client PCs)
 OmniVista 8770 Home page can be accessed using the below URL format
https://<8770_Server IP or FQDN>:8443/
 OmniVista 8770 WBM can be accessed directly using the below URL format
https://<8770_Server IP or FQDN>:8443/nmclient
 Administrator can login in to 8770 WBM using the same administrator accounts used for OmniVista
8770 server login
Restriction
 When the tree is expanded in the tree panel and from root level Advance search is not happening
with city, company and country-CR8770-10623

 Pagination will be not there for a local admin when Filter (quick search or advanced search) is
performed. CR88770-10550
 CR8770-7579 CRUD operation of OXE user and connection user fails in thick client with
"CORBA.SystemException"
 Multiple OXEs are not supported from customized views
 custom views and secondary devices restrictions :

CR8770-9464 : only one station type is possible when adding a secondary device to a user
CR8770-9447 : voice mail server wrongly seen as missing
CR8770-9448 : ANALOG station type must be removed from some predefined views and must not be
the default value for other ones
 Automatic windows resizing for 8770 WBM is browser dependent and could have impact on the
windows organisation if the browser application contains several windows. It is the case for 8770
WBM, with grid windows, tree windows.
Workaround : Manually resize the browser windows.
Browser windows can be easily resized using: CRTL + scroll mouse.
This action enables to zoom or unzoom browser windows.
 Customization views modifications will be taken into account in next Release
Note The number of simultaneous Web client connections is limited to 60.
11.24 OmniVista 8770 Web Based Management for OXE Configuration
11.24.1 OmniVista 8770 Web Based Management for OXE Configuration : Restrictions
 The GRID display limitation and Pagination are not implemented as in User WBM application
 Unable to perform quick search operation for object classes where naming attribute is Enumerated
value. Refer CR8770-10576
 Wrong toaster messages are observed in several scenarios. Refer CR8770-10567
Config WBM : Search with ‘/’, ‘ * ’ in config. Refer CR8770-10653
 Signaling link backup level is missing under shelf/board. Refer CR8770-10105
 In WBM interface, the uid is displaying as “Login”.

11.24.2 OmniVista 8770 Web Based Management for OXE Configuration: How to clear the
OXE MIBs from browsers
OmniVista 8770 configuration application is introduced in the WBM to support the configuration capabilities.
Before using the OXE configuration Webclient application, do the following steps to clear the old OXE schema
files from the OmniVista 8770 server and from browser.
Do the below steps only once.
Server side
Delete the files under the folder <8770 Install Dir>\data\config\WBM\OXE
Client side
1) Launch OmniVista 8770 WBM using the URL https://<8770 server IP or FQDN>:8443/nmclient/ in
chrome or firefox

2) In chrome
a. Launch developer tools by clicking F12 or Navigate and select More tools-> Developer
tools
b. Under Application Tab, select Clear storage and select Clear site data button. Make sure
the IndexedDB checkbox selected.

3) In Firefox
Go to menu Options-> Privacy & Security and select the button Clear Data… under Cookies and
Site Data section
11.25 Multiple IP Plane
 OXE is assigned with 3 IPs (Management IP,Service IP and Storage IP) in three different plane.
 Omnivista 8770 and Management IP of OXE should be in same Plane
 Associated OT and Management IP of OXE should be in same plane
Restriction:
 None

11.26 Mail Server
From R4.2, Protocol encryption field STARTLS is Mandatory for SMTP server configuration with authentication.
If SMTP authentication is required, select the Authentication mechanism check box, and complete the
following fields:
• In the Connection username field, enter the SMTP account name used for authentication
• In the Connection password field, enter the SMTP account password
• In the Protocol encryption field, select “startls” from the list
11.27 Manage My Phone
From this version R4.2 MD2, Creation and management of multi-line or supervision keys in the
programmable keys from Manage My Phone is not authorized.

12 KNOWN PROBLEMS IN R4.2.14.00
Here is the list of the problems (critical and major) that are not yet fixed. These are the problems detected
in the current version.
Issue key Summary

CR8770-10537 [Related] : N1 SIP: AOM is not initialized in sets configured with 8770 DM
CR8770-10586 [Related] : N1 SIP : During SEPLOS DSS logon ,event is not received from 8770
CR8770-10636 [8770 NMClient]: prog keys not displayed because of bad connection id
CR8770-10714 Alpha 8770 Trouble with installer - can't write in WINDOWS folder
CR8770-10864 [Related] : M5 NRT Unable to modify ds-start-tls field as True in 8770 v4.2.12
CR8770-10890 8770 421301 A\SSL Protocol Illegal Protocol TLSv1.0\Apache doesn't start
CR8770-10892 4.2.13.01A\ToolsOmnivista\Security -Wildfly Enable during TLS Enable
CR8770-10962 [Related] : OXE M5 : Unable to access 8770 server after upgraded to v4.2.13.1.a
OXE real time synchro: performance issue of event processing in case of huge inflow
CR8770-11213 of events
CR8770-11258 8770-MSAD server creation with secure port 636 fails
CR8770-11283 8770 Copyright ALE 2021
CR8770-11295 wildfly can not be started anymore
Prebeta 8770 : restore without rehosting / Failure: action "deploy.bat" could not be
CR8770-11317 started: [1] Fonction incorrecte.
CR8770-11323 OXE synchronization fails while loading Voice Number Pl.Modif.Dates
4.2.14 Patch c - CA signed certs- Restore Defaults option - DOESN'T remove earlier
CR8770-11329 existing certificates in oracle ldap
4.2.14 Patch c - CA signed certs- Updated cert key strength - updated cert validity -
CR8770-11330 IMPORT NOT POSSIBLE
4.2.14 Patch c - CA signed certs- 8770 Backup CANNOT BE RESTORED on same 8770
CR8770-11331 server with self-signed cert state - Apache and Directory service DON'T START
4.2.14 Patch c - CA signed certs- P12 file generated doesn't contain AD or
CR8770-11332 EJBCA Root CA cert info and in Apache CA cert - no usage
CR8770-11394 8770 : the access to the LDAP via DSCC is not possible anymore
Security failure : if we don't precise the Â port the 8770 URL https://fqdn point on a
CR8770-11437 wrong certificate (*)

Submitting a Service Request
Please connect to our eService Request application.
Before submitting a Service Request, please be sure:

 The application has been certified via the AAPP if a third party application is involved.
 You have read the release notes that list new features, system requirements, restrictions, and more,
and are available in the Technical Documentation Library.
 You have read through the related troubleshooting guides and technical bulletins available in the
Technical Documentation Library.
 You have read through the self-service information on commonly asked support questions and known
issues and workarounds available in the Technical Knowledge Center.
- END OF DOCUMENT -


TC2837en-Ed01 Installation Procedure For OmniVista8770 R4.2.14.00

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

TC2837en-Ed01 Installation Procedure For OmniVista8770 R4.2.14.00

Uploaded by

Copyright:

Available Formats

Release Note OmniVista 8770

TC 2837 ed. 01 Release 4.2

Installation Procedure for version 4.2.14.00 –

This is the installation procedure for OmniVista 8770 version 4.2.14.00

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

4 INSTALLATION AND UPGRADE .............................................................................................................. 18

5 SERVER UNINSTALLATION .................................................................................................................... 22

7 SPECIFIC MANAGEMENT ....................................................................................................................... 24

8 NEW FEATURES IN OMNIVISTA 8770 R4.2 ............................................................................................. 27

OmniVista 8770 - Release 4.2

9 NEW FEATURES IN OMNIVISTA 8770 R4.2 MD1 ..................................................................................... 38

10 NEW FEATURES IN OMNIVISTA 8770 R4.2 MD2 ................................................................................... 39

10.1 Components update ...................................................................................................................... 39

OmniVista 8770 - Release 4.2

12 KNOWN PROBLEMS IN R4.2.14.00 ....................................................................................................... 57

OmniVista 8770 - Release 4.2

It refers to the Installation manual and Administrator manual.

OmniVista 8770 - Release 4.2

OmniVista 8770 software DVD for R4.2.12: 3BH11669ANAA

2.2.1 Mandatory patches delivered

2.2.2 Anomaly Reports fixed in the patches

OmniVista 8770 - Release 4.2

OmniVista 8770 - Release 4.2

2.3 License file

OmniVista 8770 - Release 4.2

See TC 2547 : OmniVista 8770 :

This is not exhaustive

OmniVista 8770 - Release 4.2

3.1 Server PC prerequisites

3.1.1 Hardware and software

< 5000 users > 5000 users

OmniVista 8770 - Release 4.2

Operating System Service Pack or Hotfix Installation

Note The number of simultaneous thick client connections is limited to 30

3.1.2 Virtualization requirements

OmniVista 8770 - Release 4.2

3.1.4 Configuring the Server PC

3.1.5 Servers delivered by Alcatel-Lucent

OmniVista 8770 - Release 4.2

3.2.1 IP & IP/X25 connections to OmniPCX Enterprise

OXE Releases OV8770 Releases

OmniVista 8770 - Release 4.2

Warning : OmniVista 8770 <= R4.0 are no more supported

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

Warning : OmniVista 8770 <= R4.0 are no more supported

OmniVista 8770 - Release 4.2

5.1 510/070.001 or 510/071.001 (wrong call duration fix) >=R1.2

Warning : OmniVista 8770 <= R4.0 are no more supported

OmniVista 8770 - Release 4.2

OmniVista 8770 modules Software locks in OmniPCX Enterprise

OmniVista 8770 modules OpenTouch locks Description

OAMP_PERFKPI and SNMP data sending

OmniVista 8770 - Release 4.2

Hardware and Software (Minimum required)

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

OmniVista 8770 - Release 4.2

- Before server installation:

OmniVista 8770 - Release 4.2

- Windows 2019 / 2016

OmniVista 8770 - Release 4.2

o Minimum supported version for Manage My Phone application is .Net 4.0

4.2 Server Upgrade

OmniVista 8770 - Release 4.2