TC3064en-Ed02 Installation Procedure For OmniVista8770 R5.1.16.01

Release Note OmniVista 8770
TC 3064 ed. 02 Release 5.1
Installation Procedure for version 5.1.16.01.a
This is the installation procedure for OmniVista 8770 version 5.1.16.01.a
The software is available on MyPortal
Revision History
Edition 01: October 9th 2023
Edition 02: October 14th 2023
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 2023 ALE
International, ALE USA Inc. All rights reserved in all countries.
1 GENERAL ................................................................................................................................................ 5
2 CONTENT OF THE SOFTWARE PACKAGE .................................................................................................. 6
2.1 References ....................................................................................................................................... 6
2.2 Patches ............................................................................................................................................ 6
Mandatory patches delivered ...................................................................................................... 6
Anomaly Reports fixed in the patches ......................................................................................... 7
Additional patches (mandatory) .................................................................................................. 7
2.3 License file ...................................................................................................................................... 7
2.4 Versions of embedded software ........................................................................................................ 9
3 PREREQUISITES ................................................................................................................................... 10
3.1 Server PC prerequisites ................................................................................................................... 10
Hardware and software ............................................................................................................ 10
Virtualization requirements ...................................................................................................... 11
Network hardware requirements… ............................................................................................ 11
Software and hardware compatibility........................................................................................ 11
Configuring the Server PC ......................................................................................................... 11
3.2 PCX compatibilities ........................................................................................................................ 13
IP and IP/X25 connections to OmniPCX Enterprise ..................................................................... 13
OpenTouch .............................................................................................................................. 14
OmniPCX Office and OXO Connect............................................................................................. 15
OmniPCX Enterprise and OpenTouch: software locks ................................................................. 15
3.3 Client PC prerequisites ................................................................................................................... 17
4 INSTALLATION AND UPGRADE .............................................................................................................. 18

4.1 Server installation .......................................................................................................................... 18
4.2 Server Upgrade ............................................................................................................................... 20
4.3 Client installation via MSI file .......................................................................................................... 21
Remote client installation via MSI file ....................................................................................... 21
Silent client installation via MSI file .......................................................................................... 22
4.4 Client upgrade via the server .......................................................................................................... 22
5 SERVER UNINSTALLATION .................................................................................................................... 22

6 MIGRATION FROM OMNIVISTA 4760 R5.2 ............................................................................................. 23
7 SPECIFIC MANAGEMENT ....................................................................................................................... 23

7.1 Users management and OmniPCX Enterprise profiles ........................................................................ 23
7.2 Server IP address or server name modification ................................................................................. 23
7.3 MSAD synchronization and CMISE security ........................................................................................ 23
7.4 Backup on network drive ................................................................................................................ 24
7.5 Internet Explorer configuration ....................................................................................................... 24
8 NEW FEATURES IN OMNIVISTA 8770 R5.1 ............................................................................................. 26
OmniVista 8770 - Release 5.1 - Installation Procedure for version 5.1.16.01.a TC 3064 ed. 02
© Copyright 2023 ALE International, ALE USA page 2/70
8.1 Components evolution .................................................................................................................... 26
Components update in R5.1 ...................................................................................................... 26
Components evolution: log4j .................................................................................................... 26
8.2 Compatibility ................................................................................................................................. 26
Compatibility with Windows 11 and Windows Server 2022 .......................................................... 26
Compatibility with OXE PURPLE R100.1 ..................................................................................... 26
8.2.2.1 New OPUS codecs with SIP Devices .....................................................................................................27
8.2.2.2 Increase of provisioning level for Abbreviated number to 32500 ..........................................................27
8.3 Support of new terminals ................................................................................................................ 27
Compatibility with ALE-300 ...................................................................................................... 27
Compatibility with ALE-3 SIP DeskPhone .................................................................................... 27
8.4 New features in OmniVista 8770 R5.1 .............................................................................................. 28
Subscription mode for OmniVista 8770 and OXE Purple on demand ............................................. 28
Security enhancements ............................................................................................................ 30
WBM Performance Dashboard Enhancement .............................................................................. 30
8.4.3.1 Dynamic threshold detection .............................................................................................................30
8.4.3.2 New Widget: threshold detection list view .........................................................................................31
8.4.3.3 Display more detailed data ...............................................................................................................31
8.4.3.4 Customize the main dashboard ..........................................................................................................32
8.4.3.5 Display the variations between two consecutive polling counters ........................................................33
8.4.3.6 Multiselect filterable objects in detailed dashboards .........................................................................34
Last login date / hour and 8770 version in WBM panel ............................................................... 35
DECT registration from Users management ................................................................................ 36
RTU metering evolution ............................................................................................................ 38
8.4.3.1 Display activate RTU metering with MCS license .................................................................................38
8.4.3.2 Number of OmniPCX enterprise Media Gateways ................................................................................38
9 NEW FEATURES IN OMNIVISTA 8770 R5.1 MD1 ..................................................................................... 39

9.1 In Support of ALE-3 SIP DeskPhone ................................................................................................... 39
9.2 Change of port 80 ( http ) to 8443 ( https ) ...................................................................................... 39
10 NEW FEATURES IN OMNIVISTA 8770 R5.1 MD2 ................................................................................... 40
10.1 Update of Apache and OpenSSL components ................................................................................... 40

10.2 Support of ALE 300 DeskPhones in SIP mode ................................................................................... 40
10.3 Management of the XL rack ........................................................................................................... 40
10.4 Voip polling enhancements ............................................................................................................ 40
11 NEW FEATURES IN OMNIVISTA 8770 R5.1 MD3 ................................................................................... 41
11.1 Components Update ...................................................................................................................... 41

11.2 VoIP SIP on OXE main and standby ................................................................................................ 41
12 MISCELLANEOUS INFORMATION & RESTRICTIONS .............................................................................. 42

12.1 RTUM ........................................................................................................................................... 42
12.2 Users Application .......................................................................................................................... 42
12.3 Device Management (DM): ............................................................................................................. 44
12.4 Device Management on OmniPCX Enterprise .................................................................................. 46
12.5 OpenTouch Configuration .............................................................................................................. 47
12.6 OpenTouch/ OmniPCX Enterprise Synchronization .......................................................................... 47
12.7 Performance Application ............................................................................................................... 48
12.8 Audit ............................................................................................................................................ 48
12.9 Alarms/topology ........................................................................................................................... 50
12.10 OmniPCX Enterprise Object model ............................................................................................... 50
12.11 OmniPCX Office and OXO Connect Configuration .......................................................................... 51
12.12 MSAD - Active Directory Synchronization and Light Client for User Provisioning ............................. 51
12.13 SNMP Proxy ................................................................................................................................. 52
12.14 CITRIX Presentation server .......................................................................................................... 52
12.15 OmniVista 8770 UTF8 Characters in Web Directory ....................................................................... 52
12.16 SECURITY: PKI ............................................................................................................................. 53
12.17 SECURITY: POODLE Vulnerability ................................................................................................. 54
12.18 SECURITY: SHA2 conformity ......................................................................................................... 54
12.19 8082 MyIC Phone on OmniPCX Enterprise and https requests ......................................................... 54
12.20 VoIP quality supervision .............................................................................................................. 54
12.21 USERS application ....................................................................................................................... 55
12.22 Upgrade...................................................................................................................................... 55
12.23 Web Based Management .............................................................................................................. 55
12.24 WBM for OXE Configuration ......................................................................................................... 56
Restrictions .......................................................................................................................... 56
How to clear the OXE MIBs from browsers .............................................................................. 56
12.25 WBM Performance dashboard ...................................................................................................... 59
12.26 Mail Server ................................................................................................................................. 59
12.27 ManageMyPhone .......................................................................................................................... 60
12.28 Device Management (DM) ............................................................................................................ 60
12.29 Purple on Demand subscription OmniVista8770 (OPEX) ................................................................. 61
13 ISSUE FIXED IN R5.1.16 ...................................................................................................................... 62

ANNEX A: Upgrade to OmniVista 8770 5.0.24.00 ....................................................................................... 64
1 End customers in R4.2 version ............................................................................................................ 64
2 End customers already in R5.0 facing MariaDb issue ............................................................................ 64
3 End customers already in R5.0 haven’t any MariaDb issue ................................................................... 64
4 End customers already in R5.0.23.00.b ............................................................................................... 68
5 How to know the exact level of version 5.0.23.00 installed: a or b ...................................................... 69
1 GENERAL
This document describes the installation procedure for OmniVista 8770 version 5.1.16.01.a
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 MyPortal. Some new information regarding OmniVista 8770 current
version could be available.
Our Technical Knowledge Center will help you to establish your technical diagnostics:
https://myportal.al-enterprise.com/alebp/s/tkc-redirect
Warning
Each time you are requested to erase or edit a file, it is 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 (MyPortal/Quick Access or your local Services representative).
2 CONTENT OF THE SOFTWARE PACKAGE
2.1 References
The documentation is available on MyPortal, in the section OmniVista 8770/Release 5.1:
Link for Business Partners:

English
https://myportal.al-enterprise.com/a4F5I000000YOGbUAO
Link for ALE internal:

English
https://al-enterprise.lightning.force.com/a4F5I000000YOGbUAO
Note
System documentations before R3.2.8 are archived on this website.
Please open an eSR to the Support Team to receive them
2.2 Patches
Mandatory patches delivered

In the \Patches\Mandatory folder you will find the following patches:
8770.5.1.16.01.a
-------------------------------------------------------------------
Patch name : Patch_511601A_OPENJRE_DLL_JAR.zip
Delivery date : 01Sep2023
-------------------------------------------------------------------
CR8770-14094 8770: JRE 11 vulnerabilities

CR8770-14100 Failed to connect to the LDAP server during sync for old oxe versions in fresh instal
-------------------------------------------------------------------
Patch name : Patch_511601B_HELP.zip
-------------------------------------------------------------------
CR8770-14120 OXE (N2) Help texts to be incorporated in 8770 R5.1
-------------------------------------------------------------------
Patch name : Patch_511601C_WAR.zip
-------------------------------------------------------------------
CR8770-14123 8770 R5.1 Unable to add Directory containers from WBM user
-------------------------------------------------------------------
Patch name : Patch_511601D_DLL_JAR_XML_LDIF_EXE.zip
-------------------------------------------------------------------
CR8770-14150 8770-5.1.16.01: New SIP ticket format is wrong in the loader file
CR8770-14095 OV8770 | Graphical view is not correct for ALE-120 (72 keys
CR8770-14087 Serial numbers of ALE-300 sets do not show up on the 8770 application
CR8770-13960 5.1.16a\8770 to adapt new OXE SIP Ticket format SIP#xxxxx.DAT.Z
CR8770-14153 In Redundant OXE Setup- Last Polled SIP file for 2nd CPU attributes is not filled /fetched
as expected in data collection tab
=========================================
Patch name : Patch_511601E_EXE.zip
Delivery date : 05Oct2023
=========================================
CR8770-14103 INTERACT SYSTEMES IDF Blocage de synchronisation 8770
==========================================
Patch name : Patch_511601F_EXE.zip
Delivery date : 05Oct2023
==========================================
CR8770-13642 NTT Austria GmbH After the upgrade to 5.1.14 the Customer has the Same issue of
CR8770-13385.Randomly the service notification is crashing
Anomaly Reports fixed in the patches
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.
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 OXO Connect and specify in its configuration that it is the
declaration node for the OmniVista 8770 server.
OV8770 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 R5.0 R5.1
release
License 1 2 3 4 5 6 7 7 8 9 10 11 12 13 14 15
version
Note During a R5.1 new server installation, the version 15 license is mandatory.
During server upgrade: version 14 is acceptable. However, upgrade to version 15 will be necessary to benefit
from new features.
During the OmniVista 8770 server running mode: versions 14 and 15 are accepted.
2.4 Versions of embedded software
Component Version Comment
Apache 2.4.56
Apache Axis 2 1.7.9
Apache Ant 1.10.11
Wildfly 22.0.10
EJBCA No more available
Installshield Premium 2015
Oracle Directory Server Enterprise 11.1.1.7.171017
PHP 7.4.30
OpenJRE 8 (Update 1.8.0_382) Embedded in the software from
R3.2
11.0.20(x64) See TC 2547: OmniVista 8770: No
impact of Oracle Java
announcement on OmniVista 8770
MariaDB 10.6.9.0
MySQL ODBC driver 3.0.9
Python Python no more embedded
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.t
gSOAP 2.8.69
ManageMyPhone 2.9.0
Microsoft Visual C++ 2015-2019 14.22.27821.0
Redistributable -x86
Edge browser version 92.0.902.84 (64 bit)
Log4j 2.14.0
This list is not exhaustive
3 PREREQUISITES
This section describes the prerequisites required to install OmniVista 8770 server and client applications.
3.1 Server PC prerequisites
Hardware and software
< 5000 users > 5000 users

Windows 10 Professional and Enterprise(64bits) Windows Server 2016 Datacenter or Standard
Windows 11 Pro and Enterprise (with desktop experience)
Windows 2016 Datacenter or Standard (with Windows 2019 Datacenter or Standard (with
desktop experience) desktop experience)
Windows 2022 Datacenter or Standard ( with
Operating System Windows 2019 Datacenter or Standard (with desktop experience)
desktop experience)
Windows 2022 Datacenter or Standard (with
desktop experience)
1 processor Dual-Core (frequency near 2 GHz, but 1 processor Quad-Core (frequency near 2,2
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 8 GB
7 GB with license Manage My Phone 9 GB 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 from Version 93 (WBM, Directory web client, Manage My Phone)
qualified versions Mozilla Firefox from Version 72 (WBM, Directory web client, Manage My Phone)
Edge 92 64 bits (WBM, Web Directory)
IE Version 11.0 (Directory web client, Manage My Phone)
Warning Windows Server 2012 R2 is no more supported by Microsoft, thus there is no more support from ALE on
OmniVista 8770 issues linked to Windows 2012 R2
Warning
Due to the Apache release and Visual C++2015 redistributable, for All OS except Windows 10, the KB2999226
is mandatory.
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, and 60 for the web client
Virtualization requirements
OmniVista 8770 has been validated in a VMware ESX® environment and Microsoft Hyper-V®.
Refer to the OmniVista 8770 R5.0 Capacity Planning tool.
The hyper-threading option should not be validated on the VM.
Network hardware requirements…
Recommendation to use a network card Ethernet 10/100bT
Note OmniVista 8770 doesn’t support two Network boards for the administration flow.
Thus, there is no possibility to dissociate the administration flow from the thick client on a network board
and OmniVista 8770 server flows with the OXE, OT, OCE nodes on a second network board.
Software and hardware compatibility

The installation on a dedicated Server PC according to the prerequisites 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 for compatibility between an external application
and OmniVista 8770 server.
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 error 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.2 PCX compatibilities
Warning
ICS is no more supported from OmniVista 8770 R3.2. OmniPCX Office is no more supported from OmniVista
8770 R5.1, it is replaced by OXO Connect.
OmniVista OmniVista OmniVista OmniVista

8770 R4.1 8770 R4.2 8770 R5.0 8770 R5.1
OpenTouch BE / MS / MC
OT R2.4/2.5 X X X
OT R2.6 X X X
OT R2.6.1 X X X
OmniPCX Enterprise
OXE R12.3.x X X X X
OXE R12.4 X X X
OXE Purple R100 X X
OXE Purple R100.1 X
OmniPCX Office
OXO Connect / OXO Connect Evolution

X X X X
R3.1/R3.2
OXO Connect / OXO Connect Evolution R4.0 X X X
OXO Connect / OXO Connect Evolution R5.0/

X X
R 5.1
OXO Connect / OXO Connect Evolution R5.2 X
OXO Connect / OXO Connect Evolution R6.0 X
IP and 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 are supported
Warning
PPP connection is not supported.
OXE Releases OV8770 Releases

R8.0 >= R1.3
OXE Releases OV8770 Releases
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
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
R100 >=R5.0
R100.1 >=R5.1
Warning
OmniVista 8770 ≤ R4.1 are no more supported. OmniPCX Enterprise ≤ R12.2 are no more supported.
OmniVista 8770 will be supported if no issue is detected in OXE, otherwise technical support will close the
Service Request.
OpenTouch
OT Releases Software version equal to or higher than … OmniVista 8770 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
OT Releases Software version equal to or higher than … OmniVista 8770 Releases
OTMS/OTMC / R4.1
R2.5
OTMS/OTMC / R4.2
R2.6
OTMS/OTMC / R4.2.15
R2.6.1
OTMS/OTMC / R5.0
R2.6.1
Warning
OmniVista 8770 ≤ R4.1 are no more supported
OTBE is no more supported. OTMC/MS version ≤ 2.6 is not supported. Omnivista 8770 will be supported if
no issue is detected in Opentouch, otherwise technical support will close service request.
OmniPCX Office and OXO Connect
OXO
OV8770 Releases
Connect Software version equal to or higher than …
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
5.0 05.0 / OCE R5.0 >=R5.0
6.0 06.0 / 016.001 >=R5.1
Warning OmniVista 8770 ≤ R4.1 is no more supported

OmniPCX Office is no more supported
OXO Connect ≤ R3.2 is no more supported. OmniVista 8770 will be supported if no issue is
detected in OXO Connect, otherwise technical support will close the Service Request.
Refer to cross compatibility document for more details
OmniPCX Enterprise and OpenTouch: software locks
The modules of the OmniVista 8770 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 Connect.
3.3 Client PC prerequisites
Hardware and Software (Minimum required)
Operating System Windows 10 Professional and Enterprise (64bits)

Windows 11 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 93 64 bits (WBM, Directory web client, Manage My
versions Phone)
Mozilla Firefox version 72 (WBM, Directory web client, Manage My Phone)
Edge version 92 64 bits (WBM, Directory web client)
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 750MB to run the JVM
application. Refer to crqms00191548
The client is also supported on the Windows Server OS supported by the OmniVista 8770 server application.
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 OXO Connect nodes. The OMC tool is not compatible with Citrix.
Warning
In Windows 11 build 22572 ( 22H2 ) wmic ( command line interface ) is now deprecated.
As prerequisite, WMIC utility must be installed as an optional feature from: Windows settings > Apps >
Optional Features
4 INSTALLATION AND UPGRADE
4.1 Server 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, 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.
- Help Online: To view the PDF file in the browser, it is required to have the PDF reader add-on.
- The firewall may generate messages asking for allowing communication for Java.exe and bin_ns-slapd.exe
programs. You must validate these requests.
- It is mandatory to manage a fix IP address (and not a DHCP one) and the default gateway before starting
the server installation.
- The server name cannot contain the following characters: «/\[]":;|<>+=,?* _ ». If it is the case, the server
installation would fail.
- 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 is also used for Apache.
Warning During the installation, OmniVista 8770 checks the KB3021910 and KB2919355 are well installed. Otherwise
a popup will indicate that the hotfix requirements are not installed.
Do not continue: press “Ok” and “No” in the subsequent popup. Then install the KB listed above.
- From Windows 2016, to avoid general slowness add < 8770 folder > in Windows Defender settings (refer to
CR8770-8161: Infrastructure: 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, do not 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 must 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.
• 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.
- Manage My Phone information
• Minimum supported version for Manage My Phone application is .Net 4.0

• 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.
• From OmniVista 8770, the Administrator can manage all the functions in the programmable keys for all
the users.
• After the upgrade from R4.0/R4.1 server to R4.2 version, the Manage My Phone application is sometimes
disabled. By closing the Zulu platform application in Windows task manager, the services will be triggered
to start mode and service will be up.
4.2 Server Upgrade
Warning According to MariaDb version in 5.0 and OmniVista 8770 version, the upgrade procedure has changed.
OmniVista 8770 initial MariaDB MariaDB release Manual MariaDB Update procedure
release release changed? downgrade
< 5.0 5.5.x No No Regular upgrade procedure
5.0.22.00.a/ 10.5.12 Yes Yes - Remove MariaDB version
5.0.23.00.a from control panel (data are
not removed)
- Update to 5.0.24
- Regular update to 5.1
5.0.23.00.b/5.0.24.00 10.5.5 No No Regular upgrade procedure
/ 5.0.25.00
About upgrade details from 5.0.22.00.a or 5.0.23.00.a to 5.0.24.00, please refer to the Annex A
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 release brings a modification for the VOIP quality supervision application. The
Performance application based on a VitalSuite module has been removed. It has been replaced by a simpler
and more integrated module. Reports and data from the previous application will no more be available
after the upgrade to R4.0. The data must be processed before the upgrade.
The upgrade to OmniVista 8770 R5.0 is available from version 4.0.08 (version 11 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, etc.
Instead of upgrading, it is always possible to reinstall the server: reinstallation allows restarting with new
data, while 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
R4.x R5.0
R4.x R5.1
Reminder: OmniVista 8770 versions ≤ R4.1 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 number.
For more details on the supported releases, please refer to the Alcatel-Lucent OpenTouchTM Suite for Mid
& Large markets - RELEASE POLICY INFORMATION - October 2022 offer and OmniVista 8770 Feature list and
provisioning level published on MyPortal.
4.3 Client installation via MSI file
Remote client installation via MSI file
The OmniVista 8770 thick client is now available as an .msi binary inside a package: "Omivista8770Client
5.0.msi". MSI is used to install the OmniVista 8770 remote thick client.
"Omivista8770Client 5.1.msi" is a standalone package. The MSI setup file is sufficient to install the OmniVista
8770 client. It has no dependency over any files in the package.
Silent client installation via MSI file
Silent client installation via MSI is done from the location "<Package_Location>/OmniVista 8770 Client 5.1.msi"
msiexec /i "<Package_Location>\OmniVista 8770 Client 5.1.msi" /qn /l*v C:\msilog.txt”
This command has to be executed from the command prompt.
Restriction:
➢ VC++ 2015-2019 redistributable must be installed before installing the OmniVista 8770 client MSI in silent
mode. Supported version of VC++ package is made available in OmniVista 8770 package under folder name
'VC2015-2019_redistributable'.
➢ Command prompt must be run by “Run as Administrator”.
4.4 Client upgrade via the server

When a client connects to a server which has been upgraded, the client update is proposed.
- Accept the update
- Once the installation file has been retrieved, the client relaunch is required
- Enter login/password. Since 5.1, this step 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.
From client, the download of patches still uses the port 80, and not yet the port 8443.
If port is blocked by firewall, the client starting is blocked for 2 minutes.
The modification of downloading port from client will be done in MD1 (CR8770-12998)
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 folder Tools\8770Cleanup.
6 MIGRATION FROM OMNIVISTA 4760 R5.2
Warning Since 5.1, technical migration from OmniVista 4760 R5.2 to 8770 are no more possible.
The management server must be reinstalled from a new system and OmniVista 8770 version supported
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 during 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

When a secured access for configuration is managed for an OmniPCX Enterprise, the user “MSAD8770Admin”
must be added to the authorized users list on OXE side. This is to allow users creation from the MSAD server.
Note
The MSAD plug-in must be regenerated and installed again on the Active Directory server after rehosting.
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" must be
enable and the server name or its IP address had to be added in the proposed list.
For user’s creation from the MSAD Web client, the OmniVista 8770 server name must be inserted in the Trusted
sites list.
8 NEW FEATURES IN OMNIVISTA 8770 R5.1
OmniVista 8770 R5.1 is a major release and includes the main following features:
o Centralized management of OXE R100.1, OXO Connect R5.2, OTMS/OTMC 2.6.x
o Subscription mode in Purple on Demand commercial offer
o Management of ALE-2 and ALE-300 in SIP mode (MD1)
o Performance dashboard enhancements
o Compatibility with Windows 11 and Windows Server 2022
o Security enhancements (change the port Http to https (MD1), close 2 ports)
o ENS certification (Spain): timestamp on web client
o OTEC: Activate RTU meter in MCS mode, new KPI: number of OXE Media Gateways
8.1 Components evolution
Components update in R5.1

• JRE 11 64 bits (for Performance application )
• Apache
• OpenSSL
• PHP
• ManageMyPhone
• Python uninstallation for upgrade from R<5.0
• EJBCA no more available
• Wildfly
Refer to chapter 2.4 for more details
Components evolution: log4j
Update log4j to 2.1
8.2 Compatibility
Compatibility with Windows 11 and Windows Server 2022
From this version, 8770 Server and client will be compatible with the following new Operating system:
• Windows 11 Professional and Enterprise Editions Apache
• Windows Server 2022 Standard and Datacenter Editions
Compatibility with OXE PURPLE R100.1
8.2.2.1 New OPUS codecs with SIP Devices
New OPUS codecs to be added to the list of possible codecs in the SIP parameters of the SIP devices.
Those new codecs can be present in the VoIP tickets from SIP devices.
Those codecs will be available from OXE n2 MD1.
8.2.2.2 Increase of provisioning level for Abbreviated number to 32500
The abbreviated number is usually used to display the name of incoming external caller on the phone set.
There are more & more customer using the IP centralization model. Thus the current limit of 15,000
abbreviated number per OXE is becoming too low and should be increased to 32 500.
8.3 Support of new terminals
Compatibility with ALE-300
Omnivista 8770 5.1 MD1 will support the new SIP phones
Pleiades Enterprise ALE-300.
They will be supported in DM on OXE or Omnivista8770,

managed from the User, Device and OXE configuration modules.
The deployment can be done per device, per group of devices
and with their Mac@ or auto discovery
The other pleaides ALE-400 and ALE-500 will be supported in SIP mode in next MD of OXE.
Warning
The ALE 300 in SIP mode cannot be deployed on DM 8770 Server due the wild card certificate from the
8770. If the use of this set is needed in SIP mode, it is recommended to use the DM OXE till an official patch
in Omnivista 8770.
See restriction chapter.
Compatibility with ALE-3 SIP DeskPhone
Omnivista will support the new ALE-3 on OXE in next MD.
• Supported from OXE R100.1 MD1 and OmniVista 8770 5.1
MD1
• Management with the Users application, Device
management (OXE or Omnivvista 8770), OXE Configuration
• Deployment per device, per group of devices or global
• Deployment with MAC@ or auto-discovery
8.4 New features in OmniVista 8770 R5.1
Subscription mode for OmniVista 8770 and OXE Purple on demand
As of release 100.1 (n2), OXE Purple can work in a subscription mode (also called Purple on Demand, OPEX).
OXE interacts with the LMS (License Management Server located in the Cloud) to get the authorizations.
The OXE is also connected to the Cloud via the CCO agent for FTR (First Time Registration) and RTR (Right
To Run).
OmniVista 8770 is an option in the Purple subscription offer. There is no direct link between OmniVista 8770
and the LMS. All the checks are requested by the OXEs taking part of the subscription:
- Authorization to manage OXEs by OmniVista 8770
- Authorization to create users
A Purple on Demand subscription is made from MyPortal: the global number of users and the OmniVista 8770
option are defined in the subscription.
If the OmniVista 8770 option is subscribed, MyPortal requests eLP to generate one or more OmniVista 8770
OPEX licenses (full features, limited to 50,000 users), depending on the number of users in the subscription.
The OmniVista 8770 license contains 2 new items:
• SubscriptionMode = 0 / 1: 0 means CAPEX, 1 means OPEX
• CCApplicationID = string (unique, identifies the OmniVista 8770, automatically generated by eLP). The
CCApplicationID is present in the license file even in CAPEX mode.
OmniVista 8770 in OPEX mode request LMS thru OXE to check that the OXE of this subscription can be managed
by OmniVista 8770.
License
Opex
License OXE 8770

System Opex
creation eLP
My Portal
OK or not
Request for a license right OK
LMS FTR registration

System RTR = duplication
License Manager credential control
Subscription & system Server CCO & subscription active
listSubscription system
Security enhancements
For security reasons, the port 80 (http) is more and more replaced by the port 8443 (https) for all applications.
The application concerned: Alarm, topology, help online, server file chooser and scheduler logs.
As a result, when the administrator launches the Topology/Alarm application, there is a pop-up with a security
alart. If administrators must accept the security alert pop up to open the application. When you close and
launch the OmniVista 8770, this alert will occur once.
To avoid definitively this pop-up, the administrators can import manually the CA certificate from 8770 into the
trusted store of browsers. This is the auto signed certificate.
Manage My Phone has its own http server and will switch to https on port 15443.
WBM Performance Dashboard Enhancement
The purpose of this feature is to offer new improvements and adaptation to help administrator monitor OXE
performance.
8.4.3.1 Dynamic threshold detection

In order to animate the Performance application, the threshold detection is performed on the raw data, at the
time of reception and storage. Any detection marks the relevant OXE node as “threshold is exceeded”.
8.4.3.2 New Widget: threshold detection list view
A new widget has been added to offer a better view of the threshold detection.
8.4.3.3 Display more detailed data

Currently the polling of counters data is done and displayed every 30 minutes in the widgets graphs: Trunk
groups, Devices, IP domains and OXE health, except for the quality widget displayed hourly.
From the 8770 OmniVista 5.1, it is possible to change the SNMP polling time. The minimum polling time is 5
minutes and is manageable in ToolsOmnivista.
This feature is available only for daily displays.
8.4.3.4 Customize the main dashboard

From the main dashboard, widget can be customized :
- Possibility to set object filters in the widgets of the main dashboard. The selected filters are
displayed in the graphs.
- Add/Delete several widgets with different filters on objects.
- Move widgets to rearrange them
- Counters can be selected to be displayed in the widget settings
- Possibility to resize the widget to full or to half width
8.4.3.5 Display the variations between two consecutive polling counters
Display the variations between two consecutive polling for the cumulated counters, instead of displaying their
always increasing raw values, in order to make the monitoring of those counters more relevant/useful.
8.4.3.6 Multiselect filterable objects in detailed dashboards
From the widget settings, it is possible to filter several objects in details up to 6 maximum :
▪ Filter a specific period in the detailed widgets
▪ Resize and rearrange the widgets, add several instances of the same widget
Example of displays:
Last login date / hour and 8770 version in WBM panel
From the User management, the last login date/hour is displayed as well as the OmniVista 8770 version in
Help/About.
DECT registration from Users management
A new “Register” button in Users management is now available, for DECT main or secondary device, after its
creation is now available.
This button replaces the registration that was done by OXE command (dectinston )
“Deregister” button is also available, to check before deleting the DECT device
RTU metering evolution
8.4.3.1 Display activate RTU metering with MCS license

• The RTU Meter process is automatically enable (and forbid disabling) on the OXE nodes for
OmniVista 8770 with MCS license (RSC=1)
• Activated when the OXE node is configured
• Triggers automatically OTEC invoicing
Restrictions:
➢ CR8770-13026 5.1.11c\No 31000 Internal Alarm raised When RTU metering calculation job failed
➢ CR8770-13030 5.1.11c\No 31000 Internal Alarm raised No 31000 Alarm raised - when OXE mao is off & the
synchronization between OmniVista 8770 and node failed
8.4.3.2 Number of OmniPCX enterprise Media Gateways
A new KPI value has been added: KAT078 NB MEDIA GATEWAY RTU, independent of the OXE release.
9 NEW FEATURES IN OMNIVISTA 8770 R5.1 MD1
9.1 In Support of ALE-3 SIP DeskPhone

ALE-3 is supported in SIP mode in this 8770 5.1 MD1 and from OXE R100.1 MD1
9.2 Change of port 80 ( http ) to 8443 ( https )

For security reasons, the port 80 (http) is no more reachable and has been changed to 8443 (https).
Now the following application are in https: Alarms, Topology, Help, server file chooser and Scheduler.
The access to the OmniVista 8770 WBM (http://OmniVista 8770 FQDN>/nmclient ) does not redirect to
https://OmniVista 8770 FQDN>:8443/nmclient if port 80 is blocked by the firewall. The administrator is required
to enter the URL https://OmniVista 8770 FQDN>:8443/nmclient directly on browser.
Information:
The server uses the 8443 port with https for the Alarms/Topology applications. As a result, when the
administrator launches the Alarm/Topology applications, a security alert will appear. If administrators wish to
use the Alarms/Topology applications, Omnivista 8770 client, this alert will occur once.
10.1 Update of Apache and OpenSSL components

Apache version is now 2.4.56 and OpenSSL is updated to 1.1.1.t.
10.2 Support of ALE 300 DeskPhones in SIP mode

From OXE R100.1 MD4, ALE300 can be managed as SIP mode by Omnivista 8770 in users, configuration and
devices applications ( deployment with MAC@ or auto-discovery )
ALE-300
Warning Restriction: ALE300 in SIP mode is not yet supported for DM on 8770.
Graphical view for SIP devices is planned in 5.2
10.3 Management of the XL rack

From OXE R100.1 MD3, the new XL rack and its boards can be configured Configuration from the thick and
web clients.
The new rack and boards are displayed in Topology.
10.4 Voip polling enhancements

To support an evolution in OXE N2 MD3, SIP VOIP Tickets are now archived every 30mn instead 1 hour by
SIP Motor.
In scheduler application, the VOIP hourly polling job is changed to collect tickets every 30mn.
11.1 Components Update

To avoid vulnerabilities, some components have been updated:
- Apache 2.4.56,
- MariaDB 10.6.9.0,
11.2 VoIP SIP on OXE main and standby

VoIP SIP tickets are now polled from OXE main and standby, and hourly loaded in 8770 database.
12 MISCELLANEOUS INFORMATION & RESTRICTIONS
Note
All the “CR8770-…” ref. mentioned below are internal anomaly reports references. Check with Technical
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.
12.1 RTUM
The Russian Government has changed the Time zone from utc+3.00 to utc+4.00. For this reason, a delay of
one hour in RTUM counter calculation can be experienced. 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, the
RTUM counter calculation will be OK.
Restrictions:
➢ CR8770-13026 5.1.11c\No 31000 Internal Alarm raised When RTU metering calculation job failed
➢ CR8770-13030 5.1.11c\No 31000 Internal Alarm raised No 31000 Alarm raised - when OXE mao is off & the
synchronization between OmniVista 8770 and node failed
12.2 Users Application

General Information:
➢ When DM on OXE feature is enabled, limited attributes are shown for associated sets from the Users
application
➢ Older OT meta profiles (created for OT16) are made inactive when OmniVista 8770 server is upgraded to
8770 R5.0
➢ During user creation with Meta profile, additional attributes are made editable from R4.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: [email protected]
➢ 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 menu. 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 the administrator sets a very high value
by mistake 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 via a
metaprofile. Several seconds can be wasted because of a too high Max.number parameter.
Workaround: 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.
➢ ALE SoftPhone:
• The ALE Softphone can only be associated to a secondary SIP Extension of an OXE user. ALES cannot
be associated to a main set.
• ALES: External login is not updated in Company Directory entry. Refer to CR8770-12097
➢ OTC PC SIP connection is no more working.
Restrictions:
➢ Memory limit is exceeded with OXE user search for more than 1000 users. Refer to CR8770-6607
➢ “X89 40 keys AOMV” system option has incidence on the ALE Essential/Enterprise phone sets. This
behavior observed with OXE N1.280.5 is not correct. This will be fixed in a future OXE N1 release.
Refer to CR8770-11642
➢ For ALE DeskPhones number of virtual keys and special keys are not finalized in OXE Purple R100.
➢ 'SIPVOIPTicketcollector' value:
With 'Dm on 8770', in the associated Device
If Voip Ticket is enabled, then following would be setting in config file generated by 8770
<setting override="true" value="true" id="SIPVoIPTicketsCollector"/>
If voip ticket is disabled, then following would be setting in config file generated by 8770
<setting override="true" id="SIPVoIPTicketsCollector" define="default"/>
➢ Even if 'sip translator fqdn' value is filled and available in OXE and in Native encryption settings, in
the OmniVista 8770 DM device config file this value is never used.
➢ EGW IP address of CS1 and EGW IP address of CS2 are filled for Server1 and Server2 SIP address in
configuration file.
➢ Special keys F1, F2, F3 and F4 are not available for IP DeskPhone Pleiades 86x8 as the special keys
are not available from OXE side ( Ref:CR8770-12210)
12.3 Device Management (DM):

➢ Configuration of remote settings feature is now enhanced for 8008, 8018 and 8028s devices along with
8001 devices. 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 anymore be put in
service if this set belong to a VLAN
Solution:
The solution is to manage the VLAN configuration in OmniVista 8770 (the security tab of the set). For
more 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
➢ CRPLESIP-664 ALE-300 cannot retrieve its config file on the 8770 DM / Wild card certificate ( CR8770-
13338 ) -> Fixed in ALE 300 firmware R201
➢ Status of the Terminals tests performed in OmniVista 8770 with “device profile”:
Without
Profile(Normal With
Device Node Deployment) Profile Binary used for the testing
8082 OXE OK OK R300_01_15_18.zip
8082 OT OK OK R300_01_15_18.zip
MyICphone_8002_8012_R110_
8002/8012 OXE OK OK 03_059_0.zip
MyICphone_8002_8012_R110_
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.
12.4 Device Management on OmniPCX Enterprise
Verify default OXE system option 'DM management in 8770' after OXE is upgraded to OXE R100 Purple from M5
or older releases. Following OXE upgrade, if default option is false, then if OmniVista 8770 is upgraded to
R5.0, during daily job synchronization, migration of DM to OXE will happen, and all non-supported '8770 DM'
devices will be removed along with profiles declared in OmniVista 8770 and binary packages
Migration of DM from OmniVista 8770 to OXE
Though not recommended, support for migration of DM from OmniVista 8770 to OXE is possible.
All '8770 DM' devices are deleted and All 'OXE DM' devices are replaced with a limited schema and configuration
files are removed.
Restriction:
➢ Following the DM migration to OXE, '8770 DM' device 8012 deskphone (which were created when 8770
was DM Master) IS NOT REMOVED. other '8770 DM' device like 8001 and 8002 are removed.
Following DM migration to OXE, 8012 device seems to be seen like a 'OXE DM device' and shown with
'OXE DM' device schema.
Device Profile name still shows the '8012 Telnet enable' which was created when 8770 was DM.
Note: In the 'parameters tab' all the '8770 DM' profiles are REMOVED following migration to OXE DM.
config file location in 8770 - 8012 device config file NOT REMOVED and 8082 device xml.
Warning
Revert to OmniVista 8770 DM management is not possible. An OmniVista 8770 backup is advised before
activating this feature.
To secure and to avoid the removal of all configuration files on OmniVista 8770 DM side due to disabling this
parameter by mistake, OmniVista 8770 R5.0 MD1 introduces a security with an additional “Device Management
in OmniVista 8770” parameter on OmniVista 8770 side.
SIP VoIP Ticket collection Enable:
Starting since OXE N1 and 8770 5.0, possible to enable SIP terminals to publish the SIP Tickets. With DM on
8770, This option could be enabled in 8770 using device profiles / devices menu directly.
General info: New hourly polling job is introduced since 5.0.23 package to poll hourly VOIP data from OXE N1
node. This Job is in disable state by default.
Restriction:
➢ SIP VoIP Ticket collector Enable was not possible through the OmniVista 8770 DM \ Parameters\
profiles.
12.5 OpenTouch Configuration
➢ ACU_OPENTOUCH user’s creation is forbidden in OpenTouch, but the create option is still available
from OT configuration (as OT 18 data models are still supporting create operation). So, the creation
fails with valid error message.
➢ The OpenTouch node number entered during the OpenTouch declaration should be a numeric value.
Otherwise the topology synchronization with the Performance application fails.
➢ Templates Tab is changed to Profiles in OpenTouch Configuration object tree.
➢ During user creation, the TUI password should not be trivial for security reason. It should not be cyclic,
a repetition, increasing or decreasing.
services -> Security -> Password Management -> Allow trivial TUI, checks 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 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 OT FQDN in the OmniVista 8770 server Windows hosts file
- Restart the Wildfly service
➢ A new tab ‘feature’ is available for OT nodes which have the version greater than OT R 2.1. Tree
will be segregated according to Tasks.
➢ New mass provisioning rules are implemented, 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 OT id
12.6 OpenTouch/ OmniPCX Enterprise Synchronization

➢ User’s name for template management should be filled in the connectivity tab to get the templates
during synchronization.
➢ After declaration of the OmniPCX Enterprise node, the OmniPCX Enterprise Complete Global
synchronization will not synchronize associated to an OpenTouch node. The OpenTouch node should
be synchronized first.
➢ TUI voice mail should be declared in both OmniPCX Enterprise and OpenTouch for successful complete
global synchronization.
Restriction:
➢ DM master status not present in scheduler during synchronization. Refer CR8770-12774
12.7 Performance Application

Restrictions:
➢ The polling fails on one OXE when 2 OXEs are configured in SNMP V3. Refer to CR8770-12074.
➢ The SNMP polling is not fully compatible with OXE configured in spatial redundancy: the polling is not
happening when the CS having the role main IP address declared in the first position in the "IP address"
attribute (in the OXE node parameters) is the standby CPU. Refer to CR8770-12080
12.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 to CR8770-6606: 8770 R3.2.08.04: Audit system details are not available in audit application for
OmniPCX Enterprise>=OXE 12.
Restriction:
From the OXE release R12 (M1.403), detailed information about “LOGIN” action are not available
Option “more detail” = no, must be selected
Reason: In the OXE release R12, a 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 information:
Before OXE release R12:
Since the OXE R12:
12.9 Alarms/topology
Restrictions:
- OpenTouch Alarms will not be received if two OpenTouch servers have the 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 username and the same associated parameters (security level,
user password, passphrase, …) for all the OpenTouch nodes
• 2nd option: use a different SNMP v3 username for each OpenTouch node
- Topology: Dashed Line style between two network elements will be supported with IE version 11 and
above.
- From 8770 R5.1, the server uses the 8443 port with https for the Alarms/Topology application.
As a result, « In the thick client, when opening the Alarms or Topology module for the first time, there
is a Security alert pop-up. This is the normal behavior with an autogenerated OmniVista 8770 server
certificate (case of the default installation) or an OmniVista 8770 server certificate signed by a private
CA not known to Windows. In this case, they must accept the security alert pop up.
This pop-up will disappear by importing the root certificate in the Windows trust store (Internet
options) of the client machine. If a custom certificate signed by a public certification authority known
to Windows has been installed, the message will not appear, because the root certificate of this
certification authority is already in the Windows trust store.
- The 8770 thick client is running over a Windows OS where internet options support TLS up to TLSv1.2
only,
TLSv1.3 cannot be enabled for https (port 8443) in ToolsOmniVista (the best possible TLS version is
TLSv1.2).
If ever TLSv1.3 is enabled in ToolsOmniVista,
there will be an error when starting the Topology app and the only way to solve that issue is to
revert to TLSv1.2 in ToolsOmniVista
(or update the client OS to an OS supporting TLSv1.3 or install some Windows updates).
Ex : the first versions of Windows 10 (idem Windows 2016, 2019) don’t support TLSv1.3.
12.10 OmniPCX Enterprise Object model

General Information
➢ OmniVista 8770 help files are integrated.
➢ OmniPCX Enterprise help files are integrated.
➢ OmniPCX Enterprise Native Encryption feature

The OmniPCX Enterprise Native Encryption feature can be activated only when Native Encryption
license is available on OmniPCX Enterprise side. The feature is not activated by default, it needs to
be modified. Enable automatic CTL Acquisition parameters, set as True, create the CA certificate and
define the IP details in lanpbxbuild comment. For more details, refer to the OmniPCX Enterprise
technical documentation.
12.11 OmniPCX Office and OXO Connect Configuration

General Information
➢ The license must be added manually for the OXO version based on the CPU (OmniPCX Office Board)
for major upgrades
➢ OXO Connect and OXO Connect Evolution have separate binaries that need to be considered during
the installation
➢ For OmniPCX Office binary downloads, the LOLA software is not required for OXO connect evaluation,
whereas no change for OXO connect installation
➢ OXO Connect and evaluation Input and Output performed only via OMC. OMC is installed on the local
server where the OmniVista 8770 server is running
➢ OmniPCX Office synchronization restriction: synchronization happens only 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 and OCE are not allowed from configuration. It is part of the
maintenance application
➢ OmniPCX Office backup directory needs to be mounted for configuring OmniPCX Office in
online/offline mode.
➢ OmniPCX Office and OCE alarms are integrated.
Restriction
➢ OXO Cloud Connect alarms are not received.

➢ OmniPCX Office R2.1 Alarms updated for Rainbow not received in OmniVista 8770 Refer: CR8770-7086
/RQOXOC-128
➢ During the first OmniPCX Office and OMC configuration/synchronization, the system must be restarted to
avoid the “OMC Stopping the Management services” failure message in status bar update area.
12.12 MSAD - Active Directory Synchronization and Light Client for User
Provisioning
General Information
➢ 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 to 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 to 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.
12.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
on the OmniVista 8770 server side. It is better to install them in the client side machines.
These tools by default take the port number 162, and due to this, OmniVista 8770 will not receive OpenTouch
Alarms due to port conflict.
12.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 than 8GB, the OmniVista 8770 GUI will not perform as expected.
12.15 OmniVista 8770 UTF8 Characters in Web Directory

The requirement addresses the need for a full UTF8 support in all applications for users names and first names.
The objective is to manage users names/first names in UTF8 characters in the whole OmniVista 8770
management platform and all the connected elements (OmniPCX Enterprise/OpenTouch). Same thing for
import/export with an external corporate directory, from the different OmniVista 8770 applications, Users,
Directory, web directory.
The requirement is driven by the capability of the UA/NOE devices 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
in all Directory-based applications.
12.16 SECURITY: PKI

From this version, PKI application has been removed.
12.17 SECURITY: POODLE Vulnerability
SSL v3 is now replaced by TLS for encryption for this POODLE vulnerability. Earlier components which were
using SSLv3 like LDAPS, WebClient, WebDirectory will now be using TLS for encryption.
A menu item is added in ToolsOmniVista to enable/disable SSLv3. If SSLv3 is disable, then TLS is enabled.
12.18 SECURITY: SHA2 conformity

SHA2 certificates are installed by default during OmniVista 8770 new installations.
For OmniVista 8770 upgrades from R2.6, only SHA1 certificates are available. If the administrator wants to
migrate to SHA2, he should use toolsOmniVista.exe.
12.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 must 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.”
12.20 VoIP quality supervision

The Performance application based on a VitalSuite module has been removed from the product as of 2.5
release. The reports and data from this application are no more available after an upgrade to R2.5 and next
releases, so they must be generated and exported before the upgrade.
The VoIP quality supervision is now managed through predefined reports definitions, included in the Reports
application.
The VoIP reports are available for OmniPCX Office, OXO Connect and OmniPCX Enterprise R≥ 8.0.
12.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.
12.22 Upgrade
Warning Case of an upgrade with a local client already started: it is mandatory to check that all the clients are
stopped before upgrading.
Recommendation: if possible, reboot the server before upgrading.
12.23 Web Based Management
➢ The OmniVista 8770 WBM Client is focused on the Users provisioning, including mass provisioning,
customized views for different administrators and domain Management, OmniPCX Enterprise Configuration
and performance dashboard.
➢ OmniVista 8770 WBM is accessible in Google Chrome, Microsoft Edge & 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
➢ Administrators can log to OmniVista 8770 WBM using the same administrator accounts used for
OmniVista 8770 server login
➢ Advance option is available in the main device tab of created user to Manage program keys of a user
from user application without opening the OXE configuration application.
➢ Support of new devices ALES-Desktop and ALES-Mobile are possible from user application and external
login attribute is mandatory field to create a user with ALES (Desktop/Mobile)
Accessing the OmniVista 8770 WBM:

➢ As of R5.1, the URL: http://OmniVista 8770 FQDN>/nmclient does not redirect to https://OmniVista
8770 FQDN>:8443/nmclient
➢ If port 80 is blocked by the firewall. The administrator is required to hit the URL https://OmniVista
8770 FQDN>:8443/nmclient directly on browser.
Restriction
➢ Multiple OXEs are not supported from customized views
➢ custom views and secondary devices restrictions:

CR8770-9447 : voice mail server wrongly seen as missing
➢ Automatic windows resizing for 8770 WBM is browser dependent and could have impact on the
windows organization if the browser application contains several windows. It is the case for OmniVista
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 un-zoom browser’s window.
➢ Forwarded settings are not displayed in WBM user: CR8770-11975
➢ c : no creation of OTMC users from WBM (“AC/No device” type not supported on WBM) =>
workaround: creation from thick client
Note The number of simultaneous Web client connections is limited to 60.
12.24 WBM 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
➢ 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”.
➢ Multiple delete is not possible from the grid or tree.
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 Web client 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
12.25 WBM Performance dashboard

Restrictions:
➢ 8770 Performance: polling fails on one OXE when 2 OXE are configured in snmp v3: CR8770-12074
➢ WBM Performance counters not displayed when 2 nodes are using SNMP V3 protocol with same SNMP
user account : CR8770-12908
As workaround, use different SNMP user account
12.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
12.27 ManageMyPhone
Restrictions
- After the upgrade of OmniVista 8770 R5.0 version, the ManageMyPhone application is sometimes shown
as “disabled”.
Workaround: By closing the “Zulu platform application” in Windows task manager, the services will be
triggered to start mode and service will be up.
12.28 Device Management (DM)
Migrating DM from OXE to OmniVista 8770:
Though migrating the DM back from OXE to OmniVista 8770 is not recommended, if the administrator
wishes to roll back, below steps can be helpful.
• Initial condition: Device management is on OXE side. And OmniVista 8770 device application
shows only 'OXE DM' entries with restricted schema.
• In OXE: : mgr\System\Other System Param\System parameters \'Device Management In 8770’
– Enable Boolean
• From OmniVista 8770 configuration application, perform complete synchronization of OXE
node. This step ensures rolling back device management to OmniVista 8770.
• From the exported backup file’s copy, remove the OTCPC entry line items, for the rest of the
devices, set the action to Delete.
• From Device management application, import this backup file. (This step will perform clean
up activity for the existing OmniVista 8770 device data for 80x8s devices, and ignore any
specific errors related to OTCPC in scheduler logs)
• From the exported backup file’s copy, set the action to Add for all entries and reimport from
device application. Verify all the Devices are imported successfully and could be seen in the
device application.
• Perform the OXE global synchronization to regenerate the configuration files in OmniVista
8770.
• Note: ALES Desktop, ALES Mobile and Other SIP Extensions with OXE supported device types
(80x8s, ALE-2) devices which are directly created in OXE node will be still shown in devices
application with limited schema. If the administrator tries deleting such devices from the
OXE Device management application, Set’s subtype will be changed to Default in SIP
parameters in OXE (device type will be lost and it is not recommended.)
Note ALES Desktop and ALES Mobile devices export is not possible from OmniVista 8770 device management, as
these devices are managed by OXE DM.
Restriction:
CR8770-12425: DM on OXE, config files are still present in 8770
12.29 Purple on Demand subscription OmniVista8770 (OPEX)
➢ OXE Purple offer-LMS - OPEX OXE - LMS error & restrictions (recovery period etc, alarms) are still in
review.
➢ CR8770-12838: 8770 5110\ OPEX OXE - Cannot Configure OPex OXE - Connection to administration
server failed. : No Response" as a observed restriction
13 ISSUE FIXED IN R5.1.16
Here the list of issues fixed in 5.1.16
Issue Summary
CR8770-13726 8770 Job fails to synchronize with the PCS after upgrading to 5.1.15.00
CR8770-13948 Last polled SIP file 2nd CPU attribute missed in 5.1.16 .00a package
CR8770-13960 5.1.16a\8770 to adapt new OXE SIP Ticket format SIP#xxxxx.DAT.Z
CR8770-13368 8770 ISDN number is not built with ISDN prefix when ISDN Prefix list per Entity is used
CR8770-13461 8770 Audit : scheduled Reportheader not in english
CR8770-13704 No accounting reports from 8770 after upgrade to R5.1.14.00
CR8770-13728 8770 R5.1 Client .msi installation failed
OV8770 R.5.1.14 ComServer crash when SSH to OXE from OV8770 Client Networks Tab
CR8770-13836
- Connect
CR8770-13926 Users: export user data to server still using http instead of https
CR8770-13927 Users: export for Rainbow still using http instead of https
CR8770-13955 Unable to import codebook in 8770 5.1.15.00.
CR8770-13965 8770 Job fails to synchronize CROXE-29801 "Needs fix" from 8770 for syncldap crash
CR8770-13973 8770 51Purple : ALE X00 Initialization in SIP mode fails from 8770
CR8770-14029 8770 - starting the remote client takes a long time after the update
CR8770-14095 OV8770 | Graphical view is not correct for ALE-120 (72 keys)
CR8770-14099 Java vulnerabilities in the 8770 5.1 embedded Version. VW gives us 90 days to fix it
CR8770-14100 Failed to connect to the LDAP server during sync for old oxe versions in fresh install
CR8770-14123 8770 R5.1 Unable to add Directory containers from WBM user
CR8770-14150 8770-5.1.16.01: New SIP ticket format is wrong in the loader file
CR8770-14153 In Redundant OXE Setup- Last Polled SIP file for 2nd CPU attributes is not filled
/fetched as expected in data collection tab
CR8770-12979 OmniVista 8770 information disclosure on /ext/ folder
CR8770-13194 Alarms are not audible when received
CR8770-13280 8770: Azul Zulu Java Multiple Vulnerabilities: JRE upgrade
CR8770-13286 Issue with user's ISDN number construction under user aliases 5.0.2500 and 5.1.13.00.
CR8770-13325 8770 WBM Application issue
CR8770-13426 Vulnerability in the JNDI component
CR8770-13450 8770 upgraded to 5.1.14.00 changes the Domain name in XML file of 8001 set from the
Primary SIP server IP address to hostname machine name
CR8770-13629 No user creation in 8770 if OXE directory name contains a comma
CR8770-13671 credentials of dba user disclosed in nms8770-client.jar
CR8770-13677 Following the upgrade of 8770 and OXE, on WBM, users with set type: GAP+ cannot be
accessed (profile) on WBM.
CR8770-13680 8770 Company Directory when logging in as authenticated, the screen is all jumbled for
Business
CR8770-13686 Graphical view of ALE30H and ALE300 not properly configured
CR8770-13710 8770 migration failure from 5.0.25 to 5.1.15 when installation is done in multiple drives
CR8770-13725 security vulnerability, access to passwords in plain text
CR8770-13837 8770 WBM does not display the details of the users associated with DECT sets
CR8770-13949 8770 R5.1 Unable to import the Carrier
CR8770-13971 60 seconds delay while logging in Ov8770 client
CR8770-14037 Case 00697646 - installation of 8770
CR8770-14087 Serial numbers of ALE-300 sets do not show up on the 8770 application.
CR8770-14094 8770: JRE 11 vulnerabilities
CR8770-14120 OXE (N2) Help texts to be incorporated in 8770 R5.1
ANNEX A: Upgrade to OmniVista 8770 5.0.24.00
According to the technical alert resolution TC2952en-Ed03 on MariaDb issue in 5.0.22 and 5.0.23 a, this Annex
helps upgrading the OmniVista 8770 to the 5.0.24.00
1 End customers in R4.2 version
If end customers are in R4.2(Ex: 4.2.16.00) version and they are upgrading to R5.0 (5.0.24.00) release for
the first time, follow regular upgrade procedures as per the installation manual from 4.2.16.00 to 5.0.24.00
2 End customers already in R5.0 facing MariaDb issue
If end customers are already upgraded to R5.0 ( 5.0.22.00.a) release from 4.2.16.0 and faced
mysql/mariadb issue or encountered upgrade failure, then revert to 4.2.16.0 version, and upgrade
OmniVista 8770 to 5.0.24.00
3 End customers already in R5.0 haven’t any MariaDb issue
If customers are in R5.0 (5.0.22.00.a or 5.23.00.a ) and haven’t faced any MySQL/MariaDB issue, then follow
below procedure to upgrade to 5.0.24.00 :
Note Before to start the OmniVista 8770 upgrades, Administrator must manually Uninstall the MariaDB
Why do we need to remove MariaDB with Manual procedures?

Since we are downgrading the MariaDB version from 10.5.12/10.5.9 to 10.5.5 while you upgrade to
5.0.24.00
(Actually the earlier version of 8770 [less than 5.0.23.00.b] has the higher MariaDB version so we need
to remove the higher MariaDB version before you upgrade to 5.0.24.00 version since 5.0.24.00 has
MariaDB 10.5.5)
a) Stop MySQL Service from services.msc
b) From control panel, remove MariaDB 10.5.12 (or 10.5.9) version.
c) Select Remove option
d) Select Remove data option as shown below:
This remove data option only will remove the MariaDB components under C:\Program Files (x86)\MariaDB
10.5
This remove data option is NOT related to 8770 data;
This removal process will not remove the 8770 data under \8770\data\data folder, this is only MariaDb
component removal.
e) If Mysql 8770 service files are in use pop up prompts, then select Ok and complete the uninstallation of
MariaDB.
f) Perform OmniVista 8770 upgrade to 5.0.24.00 by executing setup.exe from installation package. After
upgrade MariaDB version should be 10.5.5
4 End customers already in R5.0.23.00.b
If end customers are in R5.0 (5.0.23.00.b), follow regular upgrade procedures as per the installation manual
from 5.0.23.00.b to 5.0.24.00
5 How to know the exact level of version 5.0.23.00 installed: a or b
Currently when the OmniVista 5.0.23.00 is installed, the level of production (a or b) is not mentioned in any
files or help on line.
To know the exact level, open control panel windows, this information can be find thanks to MariaDB
version :
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 -

TC3064en-Ed02 Installation Procedure For OmniVista8770 R5.1.16.01

Uploaded by

Document Informationclick to expand document information

Copyright:

Available Formats

TC3064en-Ed02 Installation Procedure For OmniVista8770 R5.1.16.01

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

TC3064en-Ed02 Installation Procedure For OmniVista8770 R5.1.16.01

Uploaded by

Copyright:

Available Formats

Release Note OmniVista 8770

TC 3064 ed. 02 Release 5.1

Installation Procedure for version 5.1.16.01.a

This is the installation procedure for OmniVista 8770 version 5.1.16.01.a

The software is available on MyPortal

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

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

7 SPECIFIC MANAGEMENT ....................................................................................................................... 23

8 NEW FEATURES IN OMNIVISTA 8770 R5.1 ............................................................................................. 26

9 NEW FEATURES IN OMNIVISTA 8770 R5.1 MD1 ..................................................................................... 39

10 NEW FEATURES IN OMNIVISTA 8770 R5.1 MD2 ................................................................................... 40

10.1 Update of Apache and OpenSSL components ................................................................................... 40

11 NEW FEATURES IN OMNIVISTA 8770 R5.1 MD3 ................................................................................... 41

11.1 Components Update ...................................................................................................................... 41

12 MISCELLANEOUS INFORMATION & RESTRICTIONS .............................................................................. 42

13 ISSUE FIXED IN R5.1.16 ...................................................................................................................... 62

It refers to the Installation manual and Administrator manual.

Link for Business Partners:

Link for ALE internal:

Mandatory patches delivered

CR8770-14094 8770: JRE 11 vulnerabilities

Anomaly Reports fixed in the patches

Additional patches (mandatory)

2.3 License file

This list is not exhaustive

3.1 Server PC prerequisites

Hardware and software

< 5000 users > 5000 users

Network hardware requirements…

Recommendation to use a network card Ethernet 10/100bT

Software and hardware compatibility

Configuring the Server PC

OmniVista OmniVista OmniVista OmniVista

OXE Purple R100 X X

OXE Purple R100.1 X

OXO Connect / OXO Connect Evolution

OXO Connect / OXO Connect Evolution R4.0 X X X

OXO Connect / OXO Connect Evolution R5.0/

OXO Connect / OXO Connect Evolution R5.2 X

OXO Connect / OXO Connect Evolution R6.0 X

IP and IP/X25 connections to OmniPCX Enterprise

OXE Releases OV8770 Releases

OT Releases Software version equal to or higher than … OmniVista 8770 Releases

OmniPCX Office and OXO Connect

2.0 02.0/016.003 >=R3.1

Warning OmniVista 8770 ≤ R4.1 is no more supported

OmniPCX Enterprise and OpenTouch: software locks

OmniVista 8770 modules Software locks in OmniPCX Enterprise

OmniVista 8770 modules OpenTouch locks Description

OAMP_PERFKPI and SNMP data sending

Hardware and Software (Minimum required)

Operating System Windows 10 Professional and Enterprise (64bits)

4.1 Server installation

- Before server installation:

- Windows 2019 / 2016

- Manage My Phone information

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

Source Release Target Release