Readme G

Release Note OmniVista 8770
TC2458 ed. 01 Release 3.2
Installation Procedure for version 3.2.08.10 –

Maintenance Delivery Release 3.2
This is the installation procedure for Omnivista 8770 version 3.2.08.10 – Third Maintenance delivery for the Release R3.2.
The software is available on Alcatel-Lucent Business Portal (https://businessportal2.alcatel-lucent.com).
Revision History
Edition 01: May 18, 2018 creation of the document
Legal notice:
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. © 2018 ALE International. All rights reserved.
www.al-enterprise.com
Table of contents
1 GENERAL ................................................................................................................................................ 5
2 CONTENT OF THE SOFTWARE PACKAGE .................................................................................................. 6
2.1 References ....................................................................................................................................... 6
2.2 Patches ............................................................................................................................................ 6
2.2.1 Mandatory patches delivered ....................................................................................................... 6
2.2.2 Other optional patches ................................................................................................................ 6
2.2.3 Anomaly Reports fixed in the patches .......................................................................................... 7
2.3 License file ....................................................................................................................................... 7
2.4 Versions of embedded software ......................................................................................................... 8
3 PREREQUISITES ..................................................................................................................................... 9
3.1 Server PC prerequisites ..................................................................................................................... 9
3.1.1 Hardware and software ............................................................................................................... 9
3.1.2 Software and hardware compatibility ......................................................................................... 10
3.1.3 Configuring the Server PC ......................................................................................................... 10
3.2 PCX compatibilities .......................................................................................................................... 11
3.2.1 IP & IP/X25 connections to OmniPCX Enterprise ......................................................................... 11
3.2.2 OpenTouch .............................................................................................................................. 12
3.2.3 OmniPCX Office ........................................................................................................................ 13
3.2.4 OmniPCX Enterprise and OpenTouch : software locks ................................................................. 14
3.3 Prerequisites for administration Client PCs ........................................................................................ 15
Network Management via WEB: ............................................................................................................. 15
4 INSTALLATION AND UPGRADE .............................................................................................................. 16

4.1 Installation ..................................................................................................................................... 16
4.2 Server Upgrade ............................................................................................................................... 17
4.3 Client upgrade ................................................................................................................................ 18
5 SERVER UNINSTALLATION .................................................................................................................... 19
6 MIGRATION FROM OmniVista 4760 ........................................................................................................ 20
7 SPECIFIC MANAGEMENT ....................................................................................................................... 21
7.1 SNMP Proxy feature ........................................................................................................................ 21
7.2 Users management and OmniPCX Enterprise profiles ........................................................................ 21
7.3 Server IP address or server name modification ................................................................................. 22
7.4 MSAD synchronization and CMISE security ....................................................................................... 22
7.5 Backup on network drive ................................................................................................................. 22
7.6 Internet Explorer configuration ........................................................................................................ 23
OmniVista 8770 - Release 3.2

Installation Procedure for version 3.2.08.10 – Maintenance Delivery Release 3.2 TC2458 ed. 01
Copyright © ALE International 2015 page 2/52
8 NEW FEATURES IN 3.2.08 ..................................................................................................................... 24
8.1 Support of Video P2P SIP seplos on OTC PC ..................................................................................... 24
8.2 8008 DeskPhone support in NOE mode (without SIP hospitality and IPv6) .......................................... 24
8.3 8018/28s DeskPhone SIP Seplos support in business mode ............................................................... 25
8.4 Web Client - Web for user provisioning............................................................................................. 26
8.5 Grid limitation in Users Application ................................................................................................... 29
8.6 Multi Device Management improvement in Users Application ............................................................. 30
8.7 OTCt Smartphone configuration improvement................................................................................... 30
8.7.1 Creation of users + OTCt Smartphone through metaprofiles from the Users application ................ 30
8.7.2 Management of the users/devices from the Users application ...................................................... 31
8.7.3 Management of the users/devices from the AD Client ................................................................. 32
8.7.4 Management of the users/devices from the OpenAPI .................................................................. 32
8.7.5 Management of the users/devices from mass provisioning files .................................................... 32
8.7.6 Management of the users/devices from 8770 WBM ..................................................................... 33
8.8 8001 DeskPhone remote management ............................................................................................. 33
8.9 RTU_MULTI-DEVICES_KPIS ............................................................................................................. 37
8.10 Support Windows Server 2016 ....................................................................................................... 37
8.11 OmniPCX Enterprise 12.1 support ................................................................................................... 38
8.12 PKI availability .............................................................................................................................. 38
9 NEW FEATURES IN 3.2.08.09 ................................................................................................................ 39
9.1 Omni Vista 8770 Web Management evolution ................................................................................... 39
10 NEW FEATURES IN 3.2.08.10 ............................................................................................................... 41
11 MISC INFORMATION & RESTRICTIONS ................................................................................................ 41
11.1 RTUM ........................................................................................................................................... 41

11.2 Users Application .......................................................................................................................... 41
11.3 Device Management (DM): ............................................................................................................ 43
11.4 OpenTouch Configuration .............................................................................................................. 44
11.5 OpenTouch Synchronization ........................................................................................................... 45
11.6 Performance Application ................................................................................................................ 45
11.7 Audit ............................................................................................................................................ 45
11.8 Alarms .......................................................................................................................................... 45
11.9 OmniPCX Office and OXO Connect Configuration ............................................................................. 46
11.10 MSAD - Active Directory Synchronization & Light Client for User Provisioning .................................. 46
11.11 SNMP Proxy ................................................................................................................................ 47
11.12 CITRIX Presentation server .......................................................................................................... 47
11.13 8770 UTF8 Characters in Web Directory ....................................................................................... 47
11.14 SECURITY : PKI .......................................................................................................................... 47
11.15 SECURITY : POODLE Vulnerability ................................................................................................ 48

11.16 SECURITY : SHA2 conformity ....................................................................................................... 48
11.17 LIMITATION for displayed entries following a search by device type on OpenTouch ........................ 48
11.18 8082 MyIc Phone on OmniPCX Enterprise and Https requests ........................................................ 49
11.19 VOIP quality supervision .............................................................................................................. 49
11.20 USERS application ....................................................................................................................... 49
11.21 Upgrade ..................................................................................................................................... 49
12 KNOWN PROBLEMS IN 3.2.08.10 ......................................................................................................... 50

1 GENERAL
Note
The final letter usually indicated in the version naming is not significant and can create confusion with
the delivered patches.
This document describes the installation procedure for OmniVista 8770 version 3.2.08.10.
It refers to the Installation manual and Administrator manual.
These documents are essential since this procedure does not provide full installation details.
It is also highly recommended to consult Alcatel-Lucent Business Portal (https://businessportal2.alcatel-
lucent.com). Some new information regarding OmniVista 8770 current version could be available.
Our Technical Knowledge Center will help you to establish your technical diagnostics:
https://businessportal.alcatel-lucent.com/alugesdp/faces/gesdp/integration/KCSKnowledge.jspx
Warning
Each time you are requested to erase or edit a file, it is absolutely necessary to make a copy of the
original.
These operations must be performed by an expert (ACSE) trained on the product. You can also contact
the "Professional Services" team (mailto: professional.services@al-enterprise.com or your local Services
representative).
Note
“crqms…and CR8770-…” are internal anomaly reports references. Check with Technical Support on which
version/patch it is fixed or if correction is important for you.

2 CONTENT OF THE SOFTWARE PACKAGE
2.1 References
The documentation is available on the Alcatel-Lucent Business Portal, in the section Technical Support\
Technical Documentation Library :
https://businessportal2.alcatel-lucent.com/technical_documentation_library
- 8770_3.2.8_im_installationmanual_8al90704usaj
- 8770_3.2.8_am_adminmanual_8al90703usaj
- 8770_3.2.8_am_rtu_metering_8al90712usaf
- 8770_3.2.8_am_securityguide_8al90705usag
- 8770_3.2.8_am_SNMPproxy_8AL90708USAE
- 8770_3.2.8_am_accountvoipticketscollect_8al90709usad
- 8770_3.2.8_am_apiusermanagement_8al90710usad
2.2 Patches
2.2.1 Mandatory patches delivered

In the \Patches\Mandatory folder you will find the following patches:
• Version 3.2.08.10 level of patch A
Reminder:
On server side, all patches located in the Patches\Mandatory folder are automatically installed at the end
of the installation.
Note The manual patches files opening is failing when using the embedded Windows tool. It’s happening
correctly when using an external tool like 7-Zip.
2.2.2 Other optional patches

None

2.2.3 Anomaly Reports fixed in the patches
This list is also included in the “readme” file under “PATCHES\Mandatory” in all deliveries.
[1]
=========================================
Patch name : Patch_320810A_CONF.zip
Delivery date : 15May2018
=========================================
CR8770-8031 swisspro Solutions AG – Headquarter //MTAC_NMC_1893F// 4059 ne peut plus
composer un numéro via l'annuaire erreur certificat
2.3 License file

 To install OmniVista 8770 and to access the various clients, you must have a specific license file for your
PCX network and which describes the available modules.
 In ACTIS, choose one PCX in the network and specify in its configuration that it is the declaration node
for OmniVista 8770 server.
release OV8770 R1.0 R1.1 R1.2 R1.3 R2.0 R2.5 R2.6 R2.6.7 R3.0 R3.1 R3.2
License version 1 2 3 4 5 6 7 7 8 9 10
Note During a R3.2.08.10 fresh server installation, the version 10 license is mandatory (OpenTouch 2.3,
OmniVista 8770 3.2 and OXE 12)
During server upgrade : version 9 is acceptable. However, upgrade to version 10 will be necessary (to be
requested through ACTIS/eBuy).
During the OmniVista 8770 server running mode : versions 9 and 10 are accepted

2.4 Versions of embedded software
Component Version Comment
Apache 2.4.33
Apache Axis 2 1.5.1
Apache Ant 1.8.0
Wildfly 10.0.0
EJBCA 6.5.0.5 PKI Re-enabled
Installshield Premium 2015
Oracle Directory Server Enterprise 11.1.1.7.160719
PHP 5.6.22
OpenJRE(Azul) OpenJRE Update Embedded in the software from
1.8_162 R3.2
MariaDB 5.5.59
MySQL ODBC driver 1.0.6
Python 2.7.4
7 zip (7za – Command Line) 9.20
Wodsftp.dll 3.8.2
Open SSL 1.0.2o
This is not exhaustive

3 PREREQUISITES
This section describes the prerequisites required to install OmniVista 8770 server and client applications.
3.1 Server PC prerequisites
3.1.1 Hardware and software
< 5000 users > 5000 users

Windows7 SP1 Professional (64 bits) Windows 2008 Server R2Std SP1 (not
Windows 2008 Server R2 Std Ed. SP1 recommended, no more supported by
Windows 8 Professional (64bits) Microsoft)
Windows 8.1 Professional (64bits) Windows 2012 Server Std Edition
Windows 2012 Server Std Edition Windows 2012 Server R2 Std Edition
Operating System
Windows 2012 Server R2 Std Edition Windows Server 2012 R2 DataCenter edition
Windows 10 Professional and Enterprise(64bits) Windows Server 2016 Datacenter, Standard
Windows Server 2012 R2 DataCenter edition (with desktop experience)
Windows 2016 Datacenter, Standard (with
desktop experience)
1 processor Dual-Core (frequency near 2 GHz, 1 processor Quad-Core (frequency near 2,2
but dependent on the processor architecture) GHz, but dependent on the processor
Processor architecture)
Processor architecture equivalent or superior
to Haswell is required
RAM (minimum) 6 GB 8GB
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
Internet browser Internet Explorer (version 11)
for the web Mozilla FireFox security (up to version 51)
directory Microsoft Edge (version 20) and Google Chrome from 57
Drives A DVD drive is required

Warning
Due to the new apache version 2.4.20 and VC++2015 redistributable, the following hotfixes and service
packs are mandatory.
Operating System Service Pack or Hotfix Installation

Windows 7 – Windows 2008R2 SP1
Windows 8.1 – windows 2012R2 KB2919442 replaced by The installation order must be done as
KB3021910 – KB2919355 follows :
KB3021910
KB2919355
KB2999226
All OS except Windows 10 KB2999226
Note  From 50000 subscribers, you need the agreement of Alcatel-Lucent (process PCS – Premium Customer
Support).
 From 100 nodes or PCS, you need the agreement of Alcatel-Lucent (process PCS – Premium
Customer Support).
 OmniVista 8770 has been validated in a VMware ESX® environment and Microsoft Hyper-V®.
The hyper-threading option should not be validated on the VM. Configure one CPU with 4 cores and
not 2 CPUs with 2 cores.
 For Accounting, the maximum number of tickets is 30millions.
 It’s not recommended to use the local Client installed on the server. However, if for any reason
this Client is regularly used it’s advised to increase the memory size.
 Windows 2008 Server R2 being no more supported by Microsoft, it’s no more recommended to use
this Operating System.
3.1.2 Software and hardware compatibility

The installation on a dedicated Server PC in accordance with the prerequisite allows a correct operation of
the software. If the number of users is lower than 250 and if the Server PC must support other applications,
you should analyze the compatibility, estimate the performance requirements of other applications and
strictly follow the installation/un-installation procedure. Moreover, the operation of these other external
applications is not supported.
The Security Guide provides a description of parameters to take into account to study compatibility
between an external application and OmniVista 8770 server.
3.1.3 Configuring the Server PC

The space disk requirements and the rules of disks partitioning are described in the Installation manual.
Here are the essential points:
 Hard disk.
A NTFS partition must be set for installing the DSEE Oracle LDAP Server. When installing the server, it is
better to keep the defaults directories and to change only the physical drives.
 The Path environment variable giving the access path to Windows and to its dll, which will receive the
access path to OmniVista 8770 binary must be valid.

 The Path is managed through the System icon of Windows Control Panel.
 If the Path is too long, a blocking can occur during installation.
 The Path must not have obsolete path, ;; doubles or \\ doubles.
 If there is an error message regarding the Path on installation, change its value and keep only the
access path to the operating system.
C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32
\WindowsPowerShell\v1.0\
 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
3.2.1 IP & IP/X25 connections to OmniPCX Enterprise
From OmniPCX Enterprise R6.0 till R12.x and all associated OmniVista 8770 releases the IP connection or
IP/25 connection is ok
Warning
PPP connection is not supported.
OXE Releases OV8770 Releases

R6.0 to R8.0 >= R1.3
R8.0.1 >= R1.0
R9.0 >= R1.0
R9.1 >= R1.0
R10.0 >= R1.0
R10.1 >= R1.1
R10.1.1 >= R1.2
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
Note : OmniPCX Enterprise R12.1 can be managed by OmniVista 8770 R3.2 without new features
Warning : OmniVista 8770 R1.x are no more supported

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

R1.0.1 1.0.100.040 >=R1.0
R1.0.1 1.0.100.060 >=R.1.1
R1.1 1.1.000.080 >=R1.1
R1.2 1.2.000.051 >=R1.2
R1.3 1.3.000.061 >=R1.3
R2.0 2.0.000.90/2.0.100.32/2.0.200.4x >=R2.0 and R2.5
R2.1 2.1.000.092 >=R2.6
R2.1.1 2.1.100.042 R2.6.7
R2.2 & R2.2.1 2.2.017.004 R3.0
R2.2.1 2.2.110.001 R3.1
R2.3 2.3.013.001 R3.2
R2.3.1 2.3.104.003 R3.2.08
Note : OpenTouch R2.3.2 can be managed by OmniVista 8770 R3.2 without new features.

OpenTouch <= R2.1.x are no more supported

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

9.0 Not supported – upgrade to 9.2 >=R1.2
9.2 920/089.001 >=R2.0
10.2 Not supported – upgrade 10.3 R2.6.7
10.3 103/009.002 – recommended: last maintenance version >=R3.0
103/024.001
OXO
Connect
Releases
2.0 02.0/016.003 >=R3.1
2.1 02.1/021.001 >=R3.2
2.2 02.2/012.001 >=R3.2.08
2.2 02.2/012.001 >=R3.2.08.09

OmniPCX Office <= R8.x are no more supported

3.2.4 OmniPCX Enterprise and OpenTouch : software locks
The modules of the OmniVista application are validated by the server license file. On the other hand, the
access to data of the various PCXs requires having appropriate software locks in each PCX:
OmniVista 8770 modules Software locks in OmniPCX Enterprise

Configuration 50 – Configuration
Accounting 42 - Accounting users
98 – Accounting for local calls (for local accounting use)
99 – Accounting for ABC calls(for network accounting use)
Directory (STAP calls) 49 – Directory
Traffic observation 42 - Accounting users
39 – Performance
VoIP 42 - Accounting users

Alarms 47 – Alarms
Secured SSH connection to OmniPCX No specific lock for OmniPCX Enterprise. Security license for
Enterprise OmniVista 8770
OmniVista 8770 modules OpenTouch locks Description

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

mlsnmp
There is no lock for OXO.

3.3 Prerequisites for administration Client PCs
Hardware and Software (Minimum required)
Operating System Windows®7 SP1 Professional (32 or 64 bits)

Windows® 8 Professional (32 or 64bits)
Windows® 8.1 Professional (32 or 64bits)
Windows® 10 Professional and Enterprise (64bits)
Processor Intel® Core 2 GHz
This processor type is given as example. The frequency clock is a minimum
requirement.
RAM 4 GB or higher
Hard drive 40 GB
Graphics board 4 MB video memory with a resolution of 1024 x 768, 16 million colors
Monitor 17 inches (19 inches recommended)
Internet browser Company Directory :
Internet Explorer® (from version 9) : version 11
Mozilla FireFox® (from version 49.0.1) : version 55
Microsoft Edge® : version 20
From Google Chrome® 57 to Google Chrome 62
Network Management via WEB:

From Google Chrome® (from version 57 to version 62)
Mozilla FireFox : version 50 & above
Free disk space OmniVista 8770 client cannot be launched if the free space in the memory
size is below 750MB. Minimum required memory space is to be 750MB to run
the JVM application. Refer: crqms00191548
The use of Clients installed on a Citrix Presentation server XenApp 7.6 is validated.
The number of clients is limited to 4.
A minimum of 8 Gb dedicated RAM is required.
The use of Clients installed on a Citrix server is not possible when we manage OmniPCX Office nodes. The
OMC tool is not compatible with Citrix.
Warning
directory consultation via WEB : “Invalid certificate” message appears. To solve this issue, please see
the KCS article #000040438

4 INSTALLATION AND UPGRADE
4.1 Installation
 Before server installation:

* Consult and apply prerequisites detailed in Installation Manual documentation, Chapter “Installation -
Server Requirements – Collecting Data for the Server”
* Verify that your computer has administrator privilege (local administrator account)
 Starting from Windows 7 or Windows 8, when using an account different from “Administrator”, to start
the server installation or an Upgrade, right click on the ServerSetup.exe file and select the option Run
as administrator. Otherwise the installation would fail.
 OmniVista 8770 server Installation should start with the User Account Control (UAC) setting level “Do not
notify “in Windows 7 professional machine.
 DAP manager support is not released on Windows 10 OS
 From OmniVista 8770 R3.0.13.00.c , new password policy has been introduced and the policy is
applicable for all he password changes which happens during the first login/ password resets. This
password policy is not implemented during installation under 8770 InstallShield.
 The firewall may generate messages asking for allowing communication for Java.exe and bin_ns-
slapd.exe programs. You have to validate these requests.
 It’s mandatory to manage a fix IP address (and not a DHCP one) and also the default gateway before
starting the server installation.
 The server name cannot contain the following characters: «/\[]":;|<>+=,?* _ ». In the opposite case, the
server installation would fail.
- If you use OmniVista 8770 and OmniVista 4760 clients in the same machine then the clients have to be
installed in the following order:
 OmniVista 8770 client
 OmniVista 4760 client
 It is not allowed to modify the default HTTP (80) and HTTPS ports (443) because they are required by SIP
device management. The port 443 has as well to be available for Apache.
 During server installation, directory path should not contain any spaces. Incase other than default path is
used for installation make sure new directory path doesn’t contain any spaces. Refer: crqms00149127
 ZULU error pop up observed when the system goes for ideal state for longer duration, which triggers the
system Memory CPU consumption usage higher than the normal behavior : CR8770-6309 and CR8770-6238
Warning
During the installation, OmniVista 8770 checks the KB3021910 KB2919442 and KB2919355 are well

installed. Otherwise a popup will indicate the hotfix requirements are not installed.
Do not continue : press “Ok” and “No” in the subsequent popup. Then install those kb listed before.
4.2 Server Upgrade
Warning
Make sure that no client in local has opened a session otherwise there is a risk of database corruption.
Warning
The server upgrade from 2.5 releases brings a modification for the VOIP quality supervision application.
The Performance application based on a Vital Suite module has been removed. It has been replaced by a
more simple and integrated module. Reports and data from the previous application will no more be
available after the upgrade to R3.2. The data have to be processed before the upgrade.
The upgrade to OmniVista 8770 R3.2 is available from version 2.6.x (version = 7 in the license).
The upgrade provides upgrade of the OmniVista 8770 database in new version, including scheduled tasks,
administrators accounts, …
Instead of upgrading, it is always possible to reinstall the server : reinstallation allows restarting with fresh
data, and importing archived accounting tickets and custom report definitions.
For OmniVista 8770 servers with a version before 2.6 (version < 7 in the license), the recommendation is
to do a new installation. Direct upgrade is not available, it is necessary to upgrade in two steps :
 For release 1.3.10.00.a (version = 4), an intermediate upgrade in version 2.6.7 is needed, before
upgrading to version 3.1,
 For release 2.0.09.01.a and 2.5.03 (versions = 5 and 6), an intermediate upgrade in version 3.0
(version = 8) is needed.
Reminder: OmniVista 8770 versions before 2.6 (1.3, 2.0, 2.5, …) are no more supported.

You can create an eSR to get an intermediate license 2.6.7 or 3.0 if you really decide for an upgrade from
versions < 2.6, with the current OmniVista 8770 license and the confirmation of the order of the 3.2 or
active SPS contract #.
For more details on the supported releases, please refer to the “Alcatel-Lucent OpenTouch® Suite for Mid &
Large markets RELEASE POLICY INFORMATION ENT_MLE_016065” and “OmniVista 8770 feature list
8AL91400USAA” published on the Business Partner Portal.
4.3 Client upgrade

When a client connects to a server which has been upgraded, a proposal for the client update is suggested.
- Accept the update
- Once the installation file has been retrieved, the client relaunch is required
- To relaunch the client, right click on the client launching icon and select the « run as
administrator » option
- Then accept the next proposals.
Nota : From R3.2.08, java client via applet is no more available

Cf : OmniVista 8770 WBM

5 SERVER UNINSTALLATION
To automatically uninstall all the server components launch the command:
Start\Programs\OmniVista8770\Tools\Uninstall OmniVista 8770 Server
The installation folder is not always deleted during the automatic server un-installation. In this case it has
to be deleted before starting a new installation.
In case of server un-installation failure it could be necessary to remove some registry keys. This can be done
using the script 8770Cleanup.vbs from the DVD folder Tools\8770Cleanup.

6 MIGRATION FROM OmniVista 4760
The goal of the OmniVista 4760 to OmniVista 8770 migration is to export the following data from an
OmniVista 4760 R5.2 server to import them in a new OmniVista 8770 server.
If an upgrade to OmniVista 4760 R5.2 from previous releases is required, a temporary license can be asked
by an eSR.
The following data is retrieved:
 PCX tree and related management
 Company Directory
 Accounting carriers data
 Personalized reports definitions
 Accounting organization by levels
To retrieve the accounting tickets from an OmniVista 4760 server you need to archive them, and then
restore them in the OmniVista 8770 server. (For the Restore operation the option “Label for records
(tickets)” has to be equal to “Loaded records”)
For the complete migration procedure, refer to the Installation Manual.
Warning
The Migration tool does not allow retrieving the directory replication management from OmniVista 4760.
It has to be managed completely in OmniVista 8770 servers.
In addition, during migration, the replicated sub-suffixes from OmniVista 4760 are created as normal
entries in the OmniVista 8770 company directory. That’s why when the sub-suffix is created to reproduce
the replication with the same name the system throws “The entry already exists”.
The workaround for the issue is
After migration :
1. Export the entries under the sub-suffix entry in the company directory (For eg., if it is a
department sub-suffix, then export the department and its children).
2. Then delete the replicated entries (For eg., department sub-suffix and its children in this case)
from the company directory.
3. Now create the sub-suffix with the same name using the replication procedure. This will create the
corresponding entry in the company directory.
Then import the entries which were exported during step 1

7 SPECIFIC MANAGEMENT
7.1 SNMP Proxy feature

If SNMP service is not started in the machine during OmniVista 8770 server installation, SNMP proxy registry
entries are not created and hence SNMP proxy will not be installed.
Then Windows SNMP service need to be started and script called inmcsnmpproxy.vbs (in the path:
\8770\bin\) has to be run to create SNMP proxy entries in the registry : \8770\bin\inmcsnmpproxy.exe -v2
7.2 Users management and OmniPCX Enterprise profiles

You need to validate the following parameter on OmniPCX Enterprise :
“System\Other System Param\System parameters\Use profile with auto. Recognition=yes.”
Otherwise no data will be inherited from the profile at a user creation.

7.3 Server IP address or server name modification
In order to change an OmniVista 8770 server name, you need to perform the following operations:
 Backup the server data
 Confirm the Directory Manager account password (launch the tool 8770\bin\ToolsOmnivista.exe)
 Uninstall the server
 Change the server name
 Install the server taking the same installation paths than on the previous server as well as the same
company directory root name. The password entered at the installation time (Directory Manager and
other accounts) has also to be the same as the previous one.
 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.
Note
The MSAD plug-in must be regenerated and installed again on the Active Directory server after rehosting.
7.4 MSAD synchronization and CMISE security

In the case where a secured access for configuration is managed for an OmniPCX Enterprise PCX, the user
“MSAD8770Admin” has to be added to the authorized users list at PCX side. This is mandatory to allow users
creation from the Web client that can be launched from the MSAD server.
Warning
The password of the account MSAD8770Admin must not be changed in the Security application
7.5 Backup on network drive
Network drives can’t be seen from Maintenance application.

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

The Security guide describes the preliminary operations management for the backups on network drives.
7.6 Internet Explorer configuration

When Internet Explorer 11 is the default web browser, the option "Use Microsoft compatibility lists" has to
be enable and the server name or it’s IP address had to be added in the proposed list.
For users creation from the MSAD Web client, the OmniVista 8770 server name has to be inserted in the
Trusted sites list.
Warning
Languages can be downloaded on BPWS

8 NEW FEATURES IN 3.2.08
8.1 Support of Video P2P SIP seplos on OTC PC

This feature concerns the escalation to video of conversations established by OTCt users with
OTC PC (main or secondary device).
This is applicable to OmniPCX Enterprise 12.1 MD1 and OTMS 2.3.1. The requirement doesn't address OTBE
2.3.1.
New parameters are manageable to support video capability of the OTC PC
- Video codec : limited to H264
- SBC encryption for remote worker
The parameters are available whatever the OmniPCX Enterprise / Open Touch release : it is under the
responsibility of the administrator to activate or not the feature from OmniVista 8770. However by default,
video is not activated.
Video parameters are available in update or creation mode, from Users or Devices applications, in unitary
user creation/device association, from mass provisioning file, for main or secondary device in a multi-device
configuration, in device profile for direct usage or in metaprofile association.
There is no provision to automatically activate the Video capability when upgrading the OmniPCX
Enterprise/OpenTouch that support this feature.
The definition of a device profile with video parameters and its application in creation or update mode can
help migration case and save operating time.
8.2 8008 DeskPhone support in NOE mode (without SIP hospitality and IPv6)
This feature is the typical support of a NOE device in the Graphical View application.
The 8008 is a low-range IP phone, small 4-lines screen with 2x3 keys for softkeys, navigation keys and 5
additional hard keys.
The support of the new device is transparent from the OmniVista 8770 point of view : dedicated phone set
name is associated to this new set, generic OmniPCX Enterprise Configuration.

8008 device
Support of the 8008 as an IP Touch device in OmniVista 8770 :
- UUM application : The value IP Touch 8008 is added to the list of the available device types for an
OXE user. However as this list is independent of the OmniPCX Enterprise release, the creation of the
user will be rejected for OmniPCX Enterprise running releases < OXE 12.
This new value is also available from ADClient and OpenAPI with the same restriction.
- RTU KPI calculation : The IP Touch 8008 device is counted in the KAT109 (STD USER IP DEVICE). KPI
definitions are updated in accordance
8.3 8018/28s DeskPhone SIP Seplos support in business mode

This is the standard support of SIP device on a SIP Extension. 8018 DeskPhone is already supported in hotel
mode but new settings have to be defined for programmable keys and user name/language parameters have
to be added in configuration files. As the devices have common SIP layer, the parameters are the same
(same datamodel/schema file). Anyhow they are managed as distinct devices for basic inventory feature.
The features provided by OmniVista 8770 are :
- Management of the 8018/8028s associated to an OXE "SIP Extension" user from all OmniVista 8770
applications (Users, Device management Mass provisioning files, AD Client, Open API) with full list of
settings, using profile or metaprofile
- Support of the auto-discovery of the MAC address : the device can be managed from the OmniVista
8770 application with or without its MAC address. Declaration of the MAC address is incompatible
with the usage of a metaprofile
- Deployment of configuration files and binary files through HTTPS
- Authentication of the device through a certificate including the MAC address as the certificate
common name element
- Binary deployment per groups of devices
Restrictions :
- Inventory is not supported, except IP address and MAC address, retrieved from OmniPCX Enterprise
parameters
- No management of phonebook
- No management of programmable keys

8.4 Web Client - Web for user provisioning
The Network Management WebClient is the new client interface for the OmniVista 8770 Server.
In OmniVista 8770 3.2.8, the OmniVista 8770 Web Based Management Client is focused on the Users
application & more precisely on the OXE/OTCt user.
8770 WBM is accessible via Google Chrome (Google Chrome 57 & above).
The NMC home page can be accessed using the below given URL format :
https://<8770_Server_IP or FQDN>
OmniVista 8770 WBM client can be accessed directly using the below given URL format :
https://<8770_Server_IP or FQDN>/nmclient/

Administrator can login to 8770 WBM using the same administrator accounts used for OmniVista 8770 server
login.
Web Based Management Features :
- Supported browser : Google Chrome (version > 54)

- Login as administrator with All rights in UUM, Directory, OmniPCX Enterprise configuration (Note :
administrator to be defined in Security application)
- Change language from login window
- Change language from homepage (restriction : RE1)
- Change password from homepage
- Notification of errors/warnings with pop up
- Notification list
- Log out

- User creation
o Create a user without telephone services (NONE type)
o Create an OXE user with any station type supported by OmniPCX Enterprise (ex : IPTouch
XXXX, GAP+, …)
o Create an OXE user with station type=SIP Extension + SIP Deskphone (ex : 8001)
o Create a CT user with any station type supported by OmniPCX Enterprise + voicemailbox on
OpenTouch
o Create a CT user with station type=SIP Extension + OTC PC (softphone)
o Create a CT user with OTC smartphone
- User edition
o Edit/Read the attributes of a NONE user
o Edit/Read the attributes of an OXE user
o Edit/Read the attributes of a CT user
o Read the attributes and icon of a SIP DeskPhone
o Read the attributes and icon of an OTC PC
o Read the attributes and icon of a secondary set
o Read the attributes and icon of an OTC smartphone
- User update
o Modify attributes of a user (lastname, firstname, cost center, entity, gui password, …)
o Add a OpenTouch voicemailbox to an OXE user by updating an OXE user : add Application
and voicemailbox on OpenTouch
o Add a OpenTouch voicemailbox to a CT user by updating a CT user : add OmniPCX Enterprise
voice mail directory number and add voicemail server (+ profile)
o Remove voicemailbox by removing Application from CT user with or without device (CT user
is converted to OXE user)
o Remove OTC PC from CT user
o Remove SIP Deskphone from CT/OXE user
o Remove OTC smartphone from CT user
- User deletion
o Multi select several users with or without devices from grid and delete them
o Delete a user with or without device from user edition. (restriction RE2)
- Search for User
o Navigate in the tree (open/close the levels or user breadcrumb)
o Simple search (restriction: RE3)
o Advanced search (restriction : RE4)
o Locate a user from user edition to tree
Known restrictions :
RE1 : some labels are not translated (in English or in technical label)
RE2 : user deletion fails if the user to be deleted is automatically selected by switching from detail to grid
display mode
RE3 : searching for more than 2000 users + otc smartphone doesn’t return all matching users (~5% are
missing) and notification list doesn’t provide the number of users found.
RE4 : search for users is limited to user attributes (names, email, …). Impossible to search for users with
filter on OmniPCX Enterprise/OpenTouch attributes.
RE5 : some refresh issues
RE6 : GUI resizing has a few issues.
RE7 : Messages in notification area/popup, Country code in tree are not translated and will be displayed in
English irrespective of the login language

RE8 : 8770 WBM client war deployment fails in Windows server 2016 due to Windows defender which is
installed by default(Refer CR8770-6662) & CR8770-6839
WorkAround: Stop Wildfly and remove the tmp folder under location C:\8770\wildfly\standalone and
restart Wildfly.
RE9 : Change language will not work after refreshing the page and session will get expired(Refer CR8770-
6795)
RE10 : After login, there is a delay to load and display users : test done with one client connected= around
100 users display by second.
Features not supported :

- Internet Explorer browser not supported
- Firefox browser not supported – will be supported in a maintenance delivery
- OpenTouch Conversation users management (create, read, update, delete)
- User Creation
o Create an OXE/CT user with secondary sets
- User update
o Add a device (SIP DeskPhone, OTC smartphone, OTC PC) to a user
o Add/Remove a secondary set to/from an OXE/CT user
o Update the attributes of a device (ex: set GSM number of an OTC smartphone)
o Change the voicemail attributes (server, profile)
o Delete the voicemailbox from a CT user without converting it to an OXE user
- User delete
o Delete a user with secondary sets
- Search for User
o Advanced Search for users with filter on OXE/OpenTouch attributes
8.5 Grid limitation in Users Application

It is now possible to display up to 1000 users in the Users Application grid from “search” or “tree display”.

8.6 Multi Device Management improvement in Users Application
The Multi Device Management improvements in Users Application address the both following points :
- Add a secondary set (until 4)
- Remove a secondary set
No need to go on OmniPCX Enterprise management
Restriction :
- Mass Pro is not supported
- MSAD is not supported
- OpenAPI is not supported
8.7 OTCt Smartphone configuration improvement

The aim of this feature is to provision the OTCt user with a Smartphone in one step.
This point addresses the full creation of a Remote Extension, association as a tandem to the real
user, creation of an abbreviated number, … in addition to the Smartphone provisioning.
In R3.2.08, there is no more restriction regarding OTCt Smartphone creation via Mass Provisioning, MSAD and
OpenAPI.
8.7.1 Creation of users + OTCt Smartphone through metaprofiles from the Users application
The metaprofile is enriched with the parameters needed to create the OTCt Smartphone and the associated
elements on OmniPCX Enterprise (OpenTouch ≥ 2.3) in order to automate the selection of the additional
directory numbers. The automation is based on a building rule where some (0, 1 or more) starting digits
from the user main directory number are replaced by other prefix digits.
Example : main directory number as 4300, remote extension as A300, device number as 99300,
abbreviated number as BD300
- OpenTouch directory number device : prefix for automatic build from main user directory phone,
this number is also used to create the OXE SIP device in case of Wifi connectivity
- Remote Extension on OmniPCX Enterprise : prefix for automatic build from main user directory
phone
- Abbreviated number : prefix for automatic build from main user directory phone
- Digits to remove from main directory number of the user in order to build the other numbers
These attributes are optional. They are useful only in case OTCt Smartphone is attached to the user created
from this metaprofile.
For information, a solution based on free number ranges (OmniPCX Enterprise or OpenTouch) won't work in
some cases

(network connectivity but GSM number given later by end-user) when the abbreviated number is
mandatory but can't be reserved on OmniPCX Enterprise for a later creation by OpenTouch. Even if it could
be possible to force the administrator to give an abbreviated number explicitly, this would not have been
possible from AD Client.
The OTCt Smartphone device profile is removed from the metaprofile : it will be selected at the time of the
user creation if needed. This prevents the duplication of metaprofile for multiple connectivity cases (OTCt
Smartphone in Cellular mode only, in dual mode or Wifi mode only). And even the duplication of
metaprofile for user with or without OTCt Smartphone.
During 2.6/3.0/3.1 to 3.2.8 migration,

- OTCt user metaprofiles with OTCt Smartphone device profile are updated : OTCt Smartphone device
profile is removed and metaprofile is marked as inactive. New attributes are proposed from User
applications and can be filled. At least Administrator's validation is requested to move the
metaprofile back to active mode.
- These updates apply to all OTCt metaprofiles, whatever the OpenTouch release.
- Already, migration to 3.2 has removed the OTCt Smartphone profile
8.7.2 Management of the users/devices from the Users application
Already in 3.2, the creation of a user is possible from the Users application and the administrator
can create the OTCt user in several ways.
- In several steps : creation of the OXE user (with or without metaprofile, with or without an OXE
profile), then addition of the OpenTouch properties (with a profile), creation/association of an OTCt
Smartphone device (with or without a device profile).
- In one step : creation of an OXE user and selection of a mobile device profile. Depending on the
OpenTouch release, additional parameters are requested that have to be filled in explicitly : device
directory number, remote extension directory number, abbreviated number (optional), gsm number
(optional)
In OmniVista 8770 3.2.8 and OpenTouch ≥ 2.3, the Administrator can create a user + the Smartphone by
selecting a metaprofile where additional directory numbers for mobile have been preconfigured (free
number ranges or building rules). When he selects an OTC Smartphone profile, the additional numbers are
automatically calculated and displayed in the creation grid for edition. In case no pre-configuration exists in
the metaprofile, the previous creation mechanism is used : the administrator has to fill these numbers
explicitly. In case no OTC Smartphone profile is selected the metaprofile pre-configuration is ineffective.
As a summary, in case of an OTCt metaprofile usage, the administrator can request the creation of an OTCt
Smartphone by selecting an OTCt Smartphone profile. At this time, the administrator will be requested to
fill some additional parameters :
- the GSM Number (optional) : mandatory for OpenTouch < 2.3. For OpenTouch ≥ 2.3, this value is
optional, even for a GSM or dual connectivity, it can be given by end-user from the Client
application
- the Device directory number and the Remote Extension directory number are automatically
generated based on the metaprofile rules but are editable. Visible only if OpenTouch ≥ 2.3

- depending on the connectivity mode of the selected device profile, the directory number for the
Abbreviated Number is displayed or not : automatically generated, based on the metaprofile rule
but is editable. Visible only if OpenTouch ≥ 2.3
- In case no rule is defined in the metaprofile for one of these directory numbers, the creation will be
refused as long as a value is not given by the administrator.
As a reminder the connection mode of the OTCt Smartphone is managed through a device profile to be
applied to several devices and hidden from creation/update grid parameters in Users application.
8.7.3 Management of the users/devices from the AD Client
From the AD Client, the full creation of an OTCt user with OTCt Smartphone device is possible thanks to the
metaprofile usage. Only few parameters are added to the user settings :
- selection of the OTCt Smartphone profile
- GSM number (optional)
Additional directory numbers (OpenTouch device, Remote extension, Abbreviated number) are calculated
from metaprofile rules. If one of the rule is not defined in the metaprofile, the creation will fail.
8.7.4 Management of the users/devices from the OpenAPI
From OpenAPI, the full creation of an OTCt user with OTCt Smartphone device is possible thanks to the
metaprofile usage. Only few parameters are added to the user schema :
- selection of the OTCt Smartphone profile
- GSM number (optional)
- the directory numbers for the device, the remote extension and the abbreviated number are
optional : no value in the create request means they will be automatically generated from the
metaprofile rules.
From the OpenAPI, it is possible to create/associate an OTCt Smartphone to a user. The device
schema is enriched with
- directory number for the OXE remote extension
- directory number of the abbreviated number
The configuration of the directory numbers is unchanged : the value is given in the request.
8.7.5 Management of the users/devices from mass provisioning files
The new attributes related to the OTCt Smartphone are present in User header line (export template
operation). The usage of metaprofile for the OTCt Smartphone creation is supported in OmniVista 8770 3.2.8
:
if the OTCt Smartphone profile attribute is valued in addition to a metaprofile, the other OTCt

Smartphone are now optional
- Directory numbers (OpenTouch SIP device, OXE remote extension, OXE abbreviated number) :NULL
value means that the values are built from the metaprofile rules
- GSM number : optional, can be edited by the end-user from the OTC Client
8.7.6 Management of the users/devices from 8770 WBM
It is possible to create the user + OTC Smartphone in one step.
8.8 8001 DeskPhone remote management

OmniVista 8770 is not reachable "per construction" (OmniVista 8770 in service management zone and not
reachable from customer secured zone). SIP devices should fetch/download their configuration file and
Binaries from OmniVista8770 through reverse proxy.
General Topology
When the GET request goes through the reverse proxy, the device certificate is authenticated by the
reverse proxy and replaced by the reverse proxy certificate in the secure management zone.

Configuration files download by remote devices
The solution consists in declaring a list of Reverse Proxy in the OmniVista 8770 server and to check in the
OmniVista 8770 that the owner of certificate attached to the GET configuration files request is either the
device itself (authenticated by its MAC address is case of a direct connection to the OmniVista 8770 server),
either one of the trusted reverse proxies registered in OmniVista 8770 (private FDQN).
This topology doesn't prevent the auto-discovery of the MAC address by the OmniVista 8770 device
management, so that even in such a case the Administrator can declare the remote devices without
declaring the MAC addresses.
Support of SIP phone (8001) behind SBC with automatic provisioning through OmniVista 8770
The Binary and configuration file is updated from OmniVista 8770

The Deployment is almost as simple as on the LAN

- Client authentication on Reverse Proxy through client certificate on SIP phone (factory or custom
certificate)
- MAC@ autodiscovery on the phone
Manual Procedure to update CTL file on 8770
a. From the 8770 server, get the CTL file: 8770/data/DM/deploy/VHE8082/ctl_VHE8082
b. Rename the file with another name: ctl_VHE8082_remote for example
c. Delete the 8770 signed data in ctl_VHE8082_remote file

Edit the file and suppress signed data
The file Contains only list of certificate:
example of file:
-----BEGIN CERTIFICATE-----
MIIEBjCCAu6gAwIBAgIQTQQhGG1woYtCsMzfN9pRyDANBgkqhkiG9w0BAQUFADBe
MQswCQYDVQQGEwJGUjEQMA4GA1UEChMHQWxjYXRlbDEWMBQGA1UECxMNUEtJIEF1
dGhvcml0eTElMCMGA1UEAxMcQWxjYXRlbCBFbnRlcnByaXNlIFNvbHV0aW9uczAg
Fw0wNTA5MjgxMDAzNDJaGA8yMDU1MDkyODEwMTEwOFowXjELMAkGA1UEBhMCRlIx
EDAOBgNVBAoTB0FsY2F0ZWwxFjAUBgNVBAsTDVBLSSBBdXRob3JpdHkxJTAjBgNV
BAMTHEFsY2F0ZWwgRW50ZXJwcmlzZSBTb2x1dGlvbnMwggEiMA0GCSqGSIb3DQEB
AQUAA4IBDwAwggEKAoIBAQCoW+RtCCV4bVFyajRkHX6mci2W/vkFqYy0OZOFKO86
IbSro6iXXiY8CnBGC6YUPg5OsBqwQcKFrpX7gxd36yDGjn7oeIWHe6SYj+LJN4dZ
wrout2x6P3ggpYCIxSJn61OqZVblt8UFcd23iL4IToHgxzPURh+KSHwM4vmfL89P
o7GGqCwpdzP/SAMo7MbFsLS1YO1OEJp9x/LRJY76A0Kga7ZQAoyM492ylmx2AbOE
nIypL/o8RYH8BHFgCfeCwdwsDgpH3FAq4icLfi4ww+ErnBHElkpHQIZp72sBDisw
g3MCvyVrgfh7mxhzJcYNKsUS3x5mg9GinvOluyo8TpCNAgMBAAGjgb0wgbowDgYD
VR0PAQH/BAQDAgEGMA8GA1UdEwEB/wQFMAMBAf8wHQYDVR0OBBYEFLcfTkW1AN3z
x5qXYgQI0ZpMukoNMBAGCSsGAQQBgjcVAQQDAgEAMGYGA1UdIARfMF0wWwYJKwwC
h25JAAABME4wTAYIKwYBBQUHAgIwQB4+AFAAQwAgAEEAbABjAGEAdABlAGwAIABF
AG4AdABlAHIAcAByAGkAcwBlACAAUwBvAGwAdQB0AGkAbwBuAHMwDQYJKoZIhvcN
AQEFBQADggEBAA3G62EdwvjmM+s/1wKgWA18v70MJ5b0JMJgpOBNITG1ocXzdDkb

HCLPO/tJIbdeneaPVbFHunOjREVjEaHaKzPyO/jFlYsp+Y0YYpgmAtbcf9CRuZ1x
uPym3mj0ReLP8QBzwHKB2KmNZz/7fdDnuy3YFFl6QIkc79+2GbNXLnidGnm0dtfz
jGLmajyfkz43ENlY+kY9Uv14z2l4vIltSjRqdtBUyw7zbJYeEu9KTaL/YEXG9j3x
FDjgI7nuv/vWKhKY/lMkb7A5RjMmLYULdqp6sw/NeIcC1qA9Fmk8VFgNENTmeGR7
n7nc1SCVb6Q6IAQgW6UsRn/3E7CUFII4/FQ=
-----END CERTIFICATE-----
…….
-----BEGIN CERTIFICATE-----
MIIDpzCCAo+gAwIBAgIJAOI79QAOV8EpMA0GCSqGSIb3DQEBCwUAMGoxCzAJBgNV
BAYTAkZSMREwDwYDVQQIDAhCcml0dGFueTEOMAwGA1UEBwwFQnJlc3QxDDAKBgNV
BAoMA0FMRTEqMCgGA1UEAwwhb3QtYnN0ZGV2LTEuYWxlLWludGVybmF0aW9uYWwu
Y29tMB4XDTE3MDYyMDE1MDAxN1oXDTE4MDYyMDE1MDAxN1owajELMAkGA1UEBhMC
RlIxETAPBgNVBAgMCEJyaXR0YW55MQ4wDAYDVQQHDAVCcmVzdDEMMAoGA1UECgwD
QUxFMSowKAYDVQQDDCFvdC1ic3RkZXYtMS5hbGUtaW50ZXJuYXRpb25hbC5jb20w
ggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC6vxucsBwwRePV6yJb7Dcp
j4/mBmKYCKvGaINIec2KbQ/M4FlWnTGjLnAWejXZkBEP+uX+iWb11KDQdOaUBQ0v
FLv6TqRyYRuhqgOjG71rgMzg6YizWXZWMGlwpMhZ7AQ5oUZLIM/t3xEeHUVa557Y
E6bFMBoI68dvFsI7GTfDS7lVrff198bomb3jzkoyUTzXAIg9exP237d7TQoc4RN1
TskNgRpGv88U4WwArU6oBLeUjv3tx1HRCtzDyhbZnzPKLVdwDTCpY+Hyq+CKY1nW
p8E9EFnkH3hhnrsPPzucchbzl1y4rcuExiEjv9FV3z5SeGbZCBgI2RzfyWSPR+7T
AgMBAAGjUDBOMB0GA1UdDgQWBBQTm69oTuT0CXwn3U1GWsuepOsevDAfBgNVHSME
GDAWgBQTm69oTuT0CXwn3U1GWsuepOsevDAMBgNVHRMEBTADAQH/MA0GCSqGSIb3
DQEBCwUAA4IBAQCujMQu34DmYOTTYFquypcz41M2Qrkuksqlah8VSLJgk49Zve+f
K1r0WaE0ovqR8D0wF71FEOtzLs4I9v6eng3pb9Pp9Gz+n9PV+5m21tRBggT9iMx9
irkY7eOZEIRfPugrd8C2BAasKztFcLV1BcKA5Z78ali1tuJIZw1EFhOD/jGhmNo/
9rIzA94gnmderLodazPHgvbDswI6HrnWf1tC/P2aJbkRK2vgQeP9W4fInVu6dbzC
zo3laGD/BMHOExC2Nxz4yUCiIAJBKOtB3arfPt6QurNJtTHHb2k6ZV3YoKI/wU45
vFkuRCmUPhrfWQbKIXab8CNQkWY6Vl0No1R8
-----END CERTIFICATE-----
d. Add the Reverse Proxy certificate in the ctl_VHE8082_remote File

From the Reverse Proxy server, get the public certificate (rootCA_Public.pem)
Edit the file and copy the certificate
Add it in the ctl_VHE8082_remote File
e. The new CTL file must be signed with a VHE connected to an OT.
Rename and copy the ctl_VHE8082_remote file on a USB KEY in: /trust_store/ ict8000ctl.pem
Plug the USB KEY in the VHE which was used to auto signed CTL for this OT (must be the Auto Signed
VHE of the OT).
On VHE and in admin mode, go to security, and start the CTL auto-signed procedure
(Security/Certificate). CTLActicateCADeployment at first, and CTLActivateSigning after.
The USB KEY contains a new ict8000ctl.xml which is signed with the Reverse Proxy certificate.
Get the @ MAC of the used VHE device

f. Rename the ict8000ctl.xml to ctl_VHE8082_remote, and copy it to the 8770 server
g. Using external tool, and from the CTL file, get the CTLMD5 (example:
e6ce0f8d802b7b96a00327e9ef659acc). Under windows 7 the commande is : CertUtil –hashfile c:\ctl_VHE8082
MD5
h. On 8770 Server, via an editor, update the configuration file of the device with:
CTLMD5 = the ctl MD5 calculated with the external tool
CTLMAC: set the MAC of VHE used for CTL signing
CTLURL="/DM/VHE8082/ ctl_VHE8082_remote "
Take care that this step must be done at each time 8770 server generates the file (when an administrator
update the device, or data user used in the device configuration file).
8.9 RTU_MULTI-DEVICES_KPIS
With introduction of the multi-devices capabilities in OXE R12, KPIS for OTEC Offer must be enriched to
better serve the multi-devices pricing model.
KPIs related to devices are duplicated to explicitly count devices in tandem configuration as secondary sets.
Other KPI are not affected, still count devices as standalone set, main set or secondary set : definitions
remain unchanged (KAT008 : STD USER DIGITAL DEVICE RTU, KAT109 : STD USER IP DEVICE RTU, KAT010 :
STD USER SIP DEVICE RTU, KAT012 : STD USER DECT DEVICE MOBILE RTU, KAT013 : STD USER WLAN DEVICE
MOBILE RTU, KAT039 : STD IP-DESKTOP / IPDS-AGENT-OPTION RTU)
Note that Analog sets and SIP devices can't be defined as part of a multi-tandem configuration. It is no sense
to duplicate KPI about pure cellular user which counts users not defined as part of a tandem configuration.
Therefore the new KPIs are :
- KAT208 : TDM IN TANDEM
- KAT209 : IP DEVICES IN TANDEM
- KAT210 : SIP EXTENSION IN TANDEM
- KAT212 : DECT IN TANDEM
- KAT213 : WLAN DEVICE IN TANDEM
- KAT239 : IPDS IN TANDEM
8.10 Support Windows Server 2016

This feature addresses the installation of the OmniVista 8770 R3.2.8 on Windows Server 2016.
Windows Server 2016 is available in 2 editions : Datacenter, Standard. Difference mainly resides in the
capacities of virtualization (number of possible VM)
For Datacenter and Standard edition, please use the installation option ”Desktop Experience”.

Restrictions :
 CR8770-7126 : OmniVista 8770 installation not possible (win2016) if a http connection (port 80) is
established
 Active Directory not supported on Windows Server 2016
 SNMP Proxy not supported on Windows Server 2016
8.11 OmniPCX Enterprise 12.1 support

The support of a new OmniPCX Enterprise release is transversal to all the OmniVista 8770 applications.
OmniPCX Enterprise Help :

From the Help menu, the OmniVista 8770 administrator can consult the OmniPCX Enterprise help (Help >
Help OmniPCX
Enterprise)
When no OmniPCX Enterprise Configuration application is launched (no connection to an OmniPCX
Enterprise), the OXE 12.1 help is displayed.
When the OmniPCX Enterprise Configuration application is active (connection to an OmniPCX Enterprise),
the Help menu displays the help associated to the release of the connected OmniPCX Enterprise, as well as
the help on the attribute.
New boards supported :

In OXE 12.1, new boards are introduced, CPU8 and CS-3.
8.12 PKI availability

PKI is available again in the OmniVista 8770.
This goes with the integration of a new release of the EJBCA compatible with the JRE version.
Restriction :
- After rehosting (Even in case of OTBE), PKI is not working. Refer CR8770-6842

9 NEW FEATURES IN 3.2.08.09
9.1 Omni Vista 8770 Web Management evolution

- 8770 WBM is accessible in Google Chrome & Mozilla Firefox browsers
Browser Name Supported version

Mozilla Firefox 50 & above
Google chrome from version 57 to
version 62
- 8770 Home page can be accessed using the below URL format
https://<8770_Server IP or FQDN>:8443/
- 8770 WBM can be accessed directly using the below URL format
https://<8770_Server IP or FQDN>:8443/nmclient
- Administrator can login in to 8770 WBM using the same administrator accounts used for 8770 server
login
- With the OmniVista8770 WBM following operation can be performed :
 Tree
Represents the organizational structure as defined in the Company Directory application of
OmniVista 8770.
 Grid/Detail
Displays user based on selection of organization unit in grid mode when several users are available
and for unique user will be displayed in detail mode.
Detail mode will display user attributes related to OXE,OT and devices.
 Create/update
Common User
Standard OXE users (OXE users without OpenTouch properties)
Connection users (OXE users with OpenTouch properties)
Associate of voicemail to OXE and OTCt users
 Delete
Common User
Standard OXE users (OXE users without OpenTouch properties)
Connection users (OXE users with OpenTouch properties)
 Association of device to OXE/OTCt user only during creation of user.

 Disassociation of single device from OXE/OTCt user.
 Search
Quick Search with First name, Last name, UID and directory number.
Advance search with different user attributes and organizational units.
 Administration Operations
Password and language can be changed for the logged in administrator.
 Notification Area
Read and manage event notification of current session.
Logout will clear all the notification of previous sessions.
Restrictions
- [8770 NMClient] Unable to delete the OXE with OT user(with smartphone) Refer: CR8770-7405
- [8770 NMClient] Dissociation of device fails with error message “Template string to be parsed"
Refer: CR8770-7450
- [8770 NMClient] OXE user creation with device association get failed After OXE user deletion Refer:
CR8770-7451
- 8770 WBM client war deployment fails in Windows server 2016 due to Windows defender which is
installed by default Refer CR8770-6662 & CR8770-6839
Workaround: Add C:\8770\wildfly\standalone\tmp exception in windows defender service

10 NEW FEATURES IN 3.2.08.10
No new feature for this maintenance release.
This maintenance delivery contains bug fixing.
11 MISC INFORMATION & RESTRICTIONS
Note
All the “CR8770-…” ref. mentioned below are internal anomaly reports references. Check with Tech.
Support on which version/patch it is fixed or if correction is important for you.
In this chapter you will find misc information about applications, components that could be useful plus
some restrictions.
11.1 RTUM
The Date and time of OmniVista 8770 server and OpenTouch server should be synced for KPIs update in
RTUM reports afterOpenTouchPartial sync (Global/Separate) : Refer: crqms00475759
Recently the Russian Govt has changed the Timezone from utc+3.00 to utc+4.00 because of which there
would be a delay of an hour in RTUM counter calculation. To solve the issue Microsoft has recommended the
patch Windows8.1-KB3162835-x64 to be installed to bring back the time zone in utc+3.00 after which the
RTUM counter calculation will be ok.
11.2 Users Application

General Information:
 To create OmniPCX Enterprise/OpenTouch Connection user based on profiles, OmniPCX

Enterprise/OpenTouch synchronization needs to be performed first to get the OXE profiles /OpenTouch
templates in Users Application.

 A mandatory attribute “OXE Profile Name” has been added for OpenTouch Connection User creation in
the Users Application. This attribute is populated by selecting an entry from a drop down. In order for
the drop down list to be populated, the profile(s) need to be created in the OXE associated with Site
being used for OpenTouch Connection user creation and then synchronized.

 Admin creates a metaprofile for connection users with a free number range. This free number range is
previously created in OXE configuration :
Max.number parameter is very sensitive : it limits the number of first free directory numbers
returned by OmniPCX Enterprise when a consultation is requested. If admin sets a very high value by

ignorance or by thinking that this is the range size (possible misunderstanding), the consultation
time increases a lot.
Example: the time to get the first 3000 free number range is about 3-4 seconds.
The problem is that such consultation is done during the creation of a connection user creation from
a metaprofile. Several seconds can be easily wasted because of a too high Max.number parameter.
Workaround:
o The recommendation is to set 10 or even less. In such case, the consultation of free directory
numbers is immediate and the user creation is therefore optimized.
Restriction:
 CT user export of more than 1K fails in UUM. Refer : CR8770-5782
 Memory limit exceeds with oxe user search of more than 1K users. Refer : CR8770-6607
 Refer CR8770-7190: "remove" action before "dissacioated device"

Way to delete a secondary set :
After remove a secondary set which have had an OTC PC, if we want to re-use the same QMCDU as
secondary set, and same URI Sip as OTC PC device, the administrator has to:

o If the secondary set has been created with same name as the main set
 Delete the QMCDU on the OXE side (from OXE Configuration)
 Delete the OTC PC device (from the Device Management)
o If the secondary set has been created with another name (UserName_tandem for example).
 After the remove, a UserName_tandem has been automatically created in User Application,
then the administator has to unassociate the OTC PC, and delete the user
11.3 Device Management (DM):

 OpenTouch/OmniVista 8770 rehosting: MYICPCSIP cannot connect - the OTCT MYICPCSIP DM files keep
the old domain name value explaining that: The SIP URI value will be filled by the administrator during
association of MYICPCSIP device to OTCt user. So administrator has to update SIP URI manually based on
the new OpenTouch host name after rehost. Refer: crqms00194838
 No more support for MIC Android, MIC Blackberry, MIC Windows and MIC Nokia mobile devices. Ref:
crqms00192940 :Devices: MIC Android, MIC Blackberry, MIC windows ,MIC Nokia devices to be removed
from devices application
 In devices application, maximum number of devices in the grid is limited to 70

Workaround is to select the device entry from tree or perform a table filter search, which will release
the memory occupied. Refer:CR8770-6646
 For overall Terminals tests performed in OmniVista 8770 with “device profile” has given the status
below:
Without
Profile(Normal With
Device Node Deployment) Profile Binary used for the testing
VHE(8082) OXE OK OK R300_01_15_17.zip
VHE(8082) OT OK OK R300_01_15_17.zip
MyICphone_8002_8012_R110_
VLE (8002/8012) OXE OK OK 03_059_0.zip
MyICphone_8002_8012_R110_
VLE (8002/8012) OT OK OK 03_059_0.zip
8001 OXE OK OK 8001-R200.4.2.0.8.zip
8068/
8038 OT OK OK 8068_R220_3_31_30.zip
8088_R301.03.011.2.2211-
8088 OT OK OK signed.zip
OXE :
8088_R301.03.007.0.2169.zip
OT :
8088 OXE OK OK 8088_R301.03.007.0.2169.zip
OTC-android-smartphone-
OTC smart phone OT 2.11.05.0.apk

Note: No hardware devices available for 8028s, 8058s, 8068s, 8078s; we have checked the graphical view of
the display. This would work in OXE 12 onwards.
11.4 OpenTouch Configuration

OpenTouch node number entered during the OpenTouch declaration should be numeric value.
Otherwise the topology synchronization with the Performance application will fail.
Templates Tab is changed to Profiles in OpenTouch Configuration object tree.
User creation, the TUI password should not be trivial for security reason. It should not be of cyclic,
repetition, increasing or decreasing fashion.
services -> Security -> Password Management -> Allow trivial TUI check this attribute to allow trivial values
to be used for TUI password. Uncheck this attribute doesn’t permit using trivial value
for TUI password.
For OTVM- Automatic creation of persons in directory is applicable for only for OmniPCX Enterprise with
OTVM users.
The connect operation of OpenTouch from Omnivista 8770 will not work with the root user and password.
The maintenance credentials should be used for login.
While configuring OpenTouch server, if ERROR_REMOTE_EXCEPTION error occurs then check following :
- Add the FQDN of OpenTouch in the hosts file of windows where the OmniVista 8770 server is
installed
- Restart of Wildfly service
A new tab „feature‟ is available for OpenTouch nodes which have the version greater than OpenTouch R 2.1.
Tree will be segregated according to Tasks.
New mass provisioning rules are implemented in R 3.1 to ease export/import operations.
Improvements include:
- Import/export with minimum set of attributes
- New enhanced template
- “Action” attribute in first column, “displayname attribute” in second column
- No reference to internal OpenTouch id.
Restriction:
 OpenTouch Configuration: Scheduled export failure with StringIndexOutOfBoundsException. Refer
CR8770- 3835

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

OmniPCX Enterprise and OmniPCX Office VoIP performance is now taken care of by NMC loader and other
legacy applications. OpenTouch VoIP tickets are not handled.
11.7 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
Restriction:
 Audit detailed system records will not be displayed in OmniVista 8770 with OmniPCX Enterprise
releases>=M1
Refer CR8770-6606: 8770 R3.2.08.04: Audit system details are not available in audit application for
OmniPCX Enterprise>=OXE 12.
11.8 Alarms
OpenTouch Alarms will not be received if two OpenTouch's have same username but different parameters
(like encryption password, passphrase, etc..).To receive the OpenTouch alarms from all the declared
OpenTouch nodes, there are two possible configurations:
- 1st option: use the same SNMP v3 user name and same associated parameters (security level, user
password, passphrase, …) for all the OpenTouch nodes
- 2nd option : use a different SNMP v3 user name for each OpenTouch node
Topology : Dashed Line style between two network elements will be supported with IE version 11 and above.

11.9 OmniPCX Office and OXO Connect Configuration
Restriction:
 OXO Cloud Connect alarms are not received. Refer crqms00207552

 OXO:R2.1 Alarms updated for Rainbow not received in 8770 Refer: CR8770-7086
11.10 MSAD - Active Directory Synchronization & Light Client for User
Provisioning
 MSAD Sync: During the MSAD Access Info Configuration, the entire user Dn (Example :
Cn=ladmin,CN=Users,DC=Company X,DC=com)needs to be entered instead of the username
alone.
 MSAD: Deleted user information getting display in another browser; Refer: crqms00203486
 MSAD: Performance Issue creations and modification of user in AD taking long time then general. Refer:
crqms00202955
 AD Web Client: Page refresh not happening after OmniPCX Enterprise/OpenTouch metaprofile
selected from the IE8&9 browser.
Workaround: The Active Scripting needs to be enabled in the IE browser Internet Options
Enable the Active Scripting as follows:

Open Internet Explorer, click the "Tool" button in the menu bar, select the "Internet
Options” “Security” tab
To enable JavaScript for all sites:
Select the "Internet" area, select "Custom Level" and "Security Settings - Internet Zone" box
gets launched.
Enable "Active Scripting" under the “Scripting” section and then click the OK button to apply
the settings. Restart your browser when finished to apply the settings and enable
JavaScript.
 MSAD Client: OmniVista 8770 Administrator is not allowed change the default password assigned to
the MSAD8770Admin account. Changing the password will make AD Client inoperable.
Workaround : If MSADAdmin password is changed then restart the Widfly service in OmniVista 8770
server.

Restriction:
 MSAD: OXE user modification with cost center is not working; Refer: CR8770-8068

11.11 SNMP Proxy
 OmniVista 8770 SNMP proxy will be installed as a part of OmniVista 8770 installation if windows SNMP
Service are present in that machine.
 If SNMP service is already installed in a machine before installing 8770, then during OmniVista 8770
installation SNMP proxy will be installed by creating necessary registry entries.
 If SNMP service is not installed in the machine, then during OmniVista 8770 installation SNMP proxy
registry entries are not created and hence SNMP proxy will not be installed. So, to use SNMP proxy
feature then Windows SNMP service need to be installed and script called inmcsnmpproxy.vbs (in the
path: \8770\bin\) has to be run to create SNMP proxy entries in the registry
 External tools like TrapReceiver and iReasoning MIB Browser should not be installed to receive the traps
from the OmniVista 8770 server side rather we could install them in the client side machines.
o These tools by default take the port number 162 and due to this OmniVista 8770 will not receive
OpenTouch Alarms. This may be due to the port conflict between these two.
11.12 CITRIX Presentation server

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

The requirement addresses the need for a full UTF8 support in all applications for User names and
firstnames. The objective is to manipulate user names/firstnames in UTF8 characters in the whole
OmniVista 8770 management platform and all the connected elements (OmniPCX Enterprise/OpenTouch) as
well as an external corporate directory,from all the OmniVista 8770 applications, Users as well as Directory,
... WebDirectory included, in both ways, meaning from OmniVista 8770 to other elements as well as from
network elements to OmniVista 8770.
The requirement is driven by the capability of the UA/NOE device to display non ASCII characters and the
OmniPCX Enterprise management restrictions where the OXE User attributes vary from Directory name and
firstname to UTF8 name and firstname depending on the character set used for the name/firstname.
In OmniVista 8770 and OpenTouch, priority is given to UTF8 names, meaning UTF8 names are used
preferably, at least in all Directory-based applications.
11.14 SECURITY : PKI

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

Restriction:
 superadmin.p12 certificate is always generated with default password not with modified password.
Refer CR8770-6841
11.15 SECURITY : POODLE Vulnerability

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

SHA2 certificate would be installed by default during fresh installation of OmniVista 8770
For OmniVista 8770 upgrades from R2.6 SHA1 certificate would only be available. If administrator wants to
migrate to SHA2 he should use toolsOmnivista.exe
11.17 LIMITATION for displayed entries following a search by device type on

OpenTouch
In the Devices application, the maximum of displayed entries following a search by device type is limited to
70.
This evolution has been made mandatory to prevent from a memory overload following some OpenTouch
data model modifications.
Coming back to the previous limitation to 200 entries needs some developments that will be available in a
next version.

11.18 8082 MyIc Phone on OmniPCX Enterprise and Https requests
Http requests from 8082 MyIc Phone to OmniVista 8770 server are no more supported from OmniVista 8770
R2.6.7.8.
Https requests are now mandatory. The OmniVista 8770 server is checking the device certificate at each file
downloading request.
Warning A particular care has to be taken before doing an upgrade to R3.1. Make sure the devices are doing
https requests and not http
Refer to KCS article “000040438 : 8770- Directory client consultation via WEB : Invalid certificate.”
11.19 VOIP quality supervision

The Performance application based on a Vital module being removed from the product as of 2.5 release.
The reports and data from this application will no more be available after an upgrade to R2.5 and next
releases.
So they have to be used before the upgrade.
The VOIP quality supervision is now managed thanks to predefined reports definitions included in the
Reports application.
The VoIP reports are only available for OmniPCX Office and OmniPCX Enterprise (version superior or equal to
8.0)
11.20 USERS application

Users creations fail when the Entity 1 does not exist on the OmniPCX Enterprise.
The reason is that the user creation by profile is failing in this case. The system tries first to create the
user, using the default parameters (including missing entity 1) before applying the profile’s parameters.
11.21 Upgrade
Warning Case of an upgrade with a local client already started ! it is mandatory to check that all the clients are
stopped !!!
Preconisation : if possible, reboot the server before doing the upgrade

12 KNOWN PROBLEMS IN 3.2.08.10
Here is the list of the problems that are not yet fixed.
These are the problems detected in the current version R3.3.08.10 :
Issue key Summary Priority

8770 : Certificate error is observed in the browser after upgrade
CR8770-8090 of 8770 Major
8770 Maintenance jobs initiated but the services have not
CR8770-8073 restarted again Major
CR8770-8068 MSAD : OXE user modification with cost center is not working Major
CR8770-8010 Import of OTC PC fails when imported with a device profile. Minor
CR8770-8009 OTC PC should not be associated to pure OXE user. Minor
These are the major problems detected in R3.2.08.09 :
CR8770-8025 OTC PC/CT/After DECT adding to MDV user, he sees incorrect Major
routing profile in OTC PC
CR8770-7964 [Report] : customization of alarm headers doesn't work Major
CR8770-7839 otbe backup failed Major
CR8770-7817 API : partial creation on OXE after an error on the licences Major
CR8770-7779 [Report] : MSAD synchronization seems to be limited to 1000 Major

users only in 3.2.08.09
CR8770-7767 ALE PROD: 8001 over Internet does not work with auto- Major
provisioning
CR8770-7760 [Report] : config file badly generated for a 8001 set (random Major
issue)
CR8770-7759 OXE UPGRADE : remote download feature with the R12 Major
CR8770-7757 [Report] : Critical vulnerabilities XSS Major
CR8770-7550 The update from 3.1 failed with FAILURE: Replace_Attributelist Major
error
CR8770-7516 In toolsomnivista, Jboss is still mentioned in menu 1 Major

CR8770-7456 8770 HappyAxis to be disabled Major
CR8770-7442 Directory: primary link not autoset if the CD entry is added in the Major
mcs customer

Follow us on Facebook and Twitter
Stay tuned on our Facebook and Twitter channels where we inform you about:
 New software releases
 New technical communications
 AAPP InterWorking Reports
 Newsletter
 Etc.
twitter.com/ALUE_Care
facebook.com/ALECustomerCare
Submitting a Service Request

Please connect to our eService Request application.
Before submitting a Service Request, make sure that:

 In case a Third-Party application is involved, that application has been certified via the AAPP
 You have read through the Release Notes which lists new features available, system requirements,
restrictions etc. available in the Technical Documentation Library
 You have read through the Troubleshooting Guides and Technical Bulletins relative to this subject
available in the Technical Documentation Library
 You have read through the self-service information on commonly asked support questions, known
issues and workarounds available in the Technical Knowledge Center
- END OF DOCUMENT -


Readme G

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Readme G

Hochgeladen von

Copyright:

Verfügbare Formate

Release Note OmniVista 8770

TC2458 ed. 01 Release 3.2

Installation Procedure for version 3.2.08.10 –

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

4 INSTALLATION AND UPGRADE .............................................................................................................. 16

OmniVista 8770 - Release 3.2

11 MISC INFORMATION & RESTRICTIONS ................................................................................................ 41

11.1 RTUM ........................................................................................................................................... 41

OmniVista 8770 - Release 3.2

OmniVista 8770 - Release 3.2

OmniVista 8770 - Release 3.2

2.2.1 Mandatory patches delivered

2.2.2 Other optional patches

OmniVista 8770 - Release 3.2

2.3 License file

OmniVista 8770 - Release 3.2

This is not exhaustive

OmniVista 8770 - Release 3.2

3.1 Server PC prerequisites

3.1.1 Hardware and software

< 5000 users > 5000 users

OmniVista 8770 - Release 3.2

Operating System Service Pack or Hotfix Installation

3.1.2 Software and hardware compatibility

3.1.3 Configuring the Server PC

OmniVista 8770 - Release 3.2

3.2 PCX compatibilities

3.2.1 IP & IP/X25 connections to OmniPCX Enterprise

OXE Releases OV8770 Releases

Warning : OmniVista 8770 R1.x are no more supported

OmniVista 8770 - Release 3.2

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

Warning : OmniVista 8770 R1.x are no more supported

OmniVista 8770 - Release 3.2

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

Warning : OmniVista 8770 R1.x are no more supported

OmniVista 8770 - Release 3.2

OmniVista 8770 modules Software locks in OmniPCX Enterprise

VoIP 42 - Accounting users

OmniVista 8770 modules OpenTouch locks Description

OAMP_PERFKPI and SNMP data sending

OmniVista 8770 - Release 3.2

Hardware and Software (Minimum required)

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

Network Management via WEB:

OmniVista 8770 - Release 3.2

 Before server installation:

OmniVista 8770 - Release 3.2

4.2 Server Upgrade

OmniVista 8770 - Release 3.2

4.3 Client upgrade

Nota : From R3.2.08, java client via applet is no more available

OmniVista 8770 - Release 3.2

OmniVista 8770 - Release 3.2

OmniVista 8770 - Release 3.2

7.1 SNMP Proxy feature

7.2 Users management and OmniPCX Enterprise profiles

OmniVista 8770 - Release 3.2

7.4 MSAD synchronization and CMISE security

7.5 Backup on network drive

Network drives can’t be seen from Maintenance application.

OmniVista 8770 - Release 3.2

7.6 Internet Explorer configuration