8770 Installation Procedure Release 2.6.7

Release Note OmniVista 8770
TC 2105 ed. 01 Release 2.6.7
INSTALLATION PROCEDURE FOR OMNIVISTA 8770

RELEASE 2.6
Omnivista 8770 version 2.6.07.05.a is released today.
It is available on Alcatel-Lucent Business Portal (https://businessportal2.alcatel-lucent.com) and on DVD-ROM with the

reference 3BH11670 AGAC.
Revision History
Edition 1: October 23, 2015 creation of the document
Legal notice:
The information presented is subject to change without notice.
ALE International assumes no responsibility for inaccuracies contained herein.
Copyright © ALE International 2015
Table of contents
1 GENERAL ................................................................................................................................................ 4
2 CONTENT OF THE SOFTWARE PACKAGE .................................................................................................. 5
2.1 References ....................................................................................................................................... 5
2.2 Patches ............................................................................................................................................ 5
2.2.1 Mandatory patches delivered with the DVD-ROM version ............................................................... 5
2.2.2 Optional patches ......................................................................................................................... 7
2.3 License file ....................................................................................................................................... 7
2.4 Versions of embedded software ......................................................................................................... 7
3 PREREQUISITES ..................................................................................................................................... 8
3.1 Server PC prerequisites ..................................................................................................................... 8
3.1.1 Hardware and software ............................................................................................................... 8
3.1.2 Software and hardware compatibility ........................................................................................... 8
3.1.3 Configuring the Server PC ........................................................................................................... 9
3.2 PCX compatibilities ............................................................................................................................ 9
3.2.1 IP, IP/X25, connections to OmniPCX Enterprise ............................................................................ 9
3.2.2 OpenTouch............................................................................................................................... 10
3.2.3 OmniPCX Office ........................................................................................................................ 10
3.2.4 OmniPCX Enterprise and OpenTouch software locks .................................................................... 10
3.3 Prerequisites of administration Client PCs ......................................................................................... 11
The use of Clients installed on a Citrix Presentation server XenApp 7.6 is validated. .................................. 11
3.4 Prerequisites of Client PCs for directory consultation via WEB ............................................................ 11
4 INSTALLATION AND UPGRADE .............................................................................................................. 12
4.1 Installation ..................................................................................................................................... 12

4.2 Server Upgrade ............................................................................................................................... 12
4.3 Client upgrade ................................................................................................................................ 13
5 SERVER UNINSTALLATION .................................................................................................................... 13

6 MIGRATION FROM OmniVista 4760 ........................................................................................................ 13
6.1 Description ..................................................................................................................................... 13

7 SPECIFIC MANAGMENT ......................................................................................................................... 15
7.1 SNMP Proxy feature ........................................................................................................................ 15
7.2 Users management and OXE profiles ................................................................................................ 15
7.3 PKI ................................................................................................................................................ 15
7.4 Server IP address or server name modification ................................................................................. 15
7.5 MSAD synchronization and CMISE security ....................................................................................... 16
7.6 Backup on network drive ................................................................................................................. 16
7.7 Disable Java update ........................................................................................................................ 16
OmniVista 8770 - Release 2.6.7

Installation Procedure for OmniVista 8770 Release 2.6.7 TC 2105 ed. 01
Copyright © ALE International 2015 page 2/37
In windows 7, if the Java update parameters are not displayed in the Java control panel, you have to do
the following: .................................................................................................................................... 16
7.8 Internet Explorer configuration ........................................................................................................ 17
8 NEW FEATURES .................................................................................................................................... 18
8.1 New PCX versions supported ........................................................................................................... 18
8.2 8038 Premium Deskphone support for OpenTouch ............................................................................ 18
8.3 8001 DeskPhone support for OpenTouch .......................................................................................... 19
8.4 Support of Chrome web browser for OmniVista 8770 web Client ........................................................ 19
8.5 New settings for 8088 Deskphone in hospitality mode for OmniPCX Enterprise ................................... 19
8.6 Topology application enhancements ................................................................................................. 19
8.7 Enhancement of the person’s automatic creation process in the directory ........................................... 20
8.8 Manage OmniPCX Enterprise devices key profiles in Metaprofiles ....................................................... 21
8.8.1 Key profile creation in the OmniPCX Enterprise ........................................................................... 21
8.8.2 User creation in OmniVista 8770 ................................................................................................ 22
8.8.3 User creation from AD client, Open API or Mass Provisionning file ................................................ 22
8.9 Identification of new types of ALE Deskphones ................................................................................. 22
8.9.1 Devices creation in the USERS application .................................................................................. 22
8.9.2 Keys management using a graphical view................................................................................... 23
8.9.3 Support of the new devices in RTU ............................................................................................ 24
8.10 New RTU KPIs .............................................................................................................................. 24
8.10.1 OpenTouchT ID ...................................................................................................................... 24
8.10.2 OmniPCX Enterprise OMS ........................................................................................................ 24
8.10.3 Fax pages ............................................................................................................................... 25
8.10.4 Automated Attendant ports numbers ........................................................................................ 25
8.10.5 Call Centers ............................................................................................................................ 26
8.11 Security: POODLE vulnerability ....................................................................................................... 27
9 RESTRICTIONS ..................................................................................................................................... 29
9.1 8082 MyIc Phone on OmniPCX Enterprise and Https requests ............................................................ 29
9.2 VOIP quality supervision .................................................................................................................. 29
9.3 Client launching failure on Windows7 ............................................................................................... 29
9.4 Topology ........................................................................................................................................ 30
9.4.1 Loss of customized topology views after an upgrade ................................................................... 30
9.4.2 Time to display the data ............................................................................................................ 30
9.5 USERS ............................................................................................................................................ 30
9.6 OmniTouch 8400 ICS users management ......................................................................................... 30
9.7 OmniVista 8770-MSAD synchronization............................................................................................. 30
9.8 OpenTouch alarms display ............................................................................................................... 30
10 DEFAULTS FIXED in R2.6.07 ................................................................................................................ 32

11 KNOWN PROBLEMS ............................................................................................................................. 35

1 GENERAL
This document describes the installation procedure for OmniVista 8770 version 2.6.07.05.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 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
The following Technical Communications relative to OmniVista 4760 could as well help for the OmniVista 8770
maintenance. However we do not guaranty the full compatibility with the OmniVista 8770 product.
TG0029 Trouble shooting Guide
TG0033 OmniPCX Enterprise Interworking
TCV020 Emails sending by OmniVista 4760
TCV039 License management
TCV060 Directory Management
TCV061 Alarms filtering from OmniPCX Enterprise to OmniVista 4760
TC0846 Accounting: Investigation elements
TC0858 Traffic observation: Investigation elements
TC1520 ed2 User Management with the USERS Application
TC1521 ed3 OTmass users and devices import
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. In the opposite side, you
can contact the "Professional Services" (mailto:professional.services@alcatel-lucent.com or your local
Services representative).

2 CONTENT OF THE SOFTWARE PACKAGE
2.1 References
- OmniVista 8770 Release 2.6.7 package : 3BH11669 AGAC
- OmniVista 8770 software DVD which contains: : 3BH11670 AGAC
 Version Release 2.6.07.05.a
 Installation Manual : 8AL90704USAG Ed.1.0
 Security Guide : 8AL90705USAE Ed.1.0
The documentation is no more provided on a CD.

It’s available on the Alcatel-Lucent Business Portal, in the section Technical Support\ Technical Documentation
Library.
https://businessportal2.alcatel-lucent.com/technical_documentation_library?
 Administrator Manual : 8AL90703USAG Ed.1.0
 Installation Manual : 8AL90704USAG Ed.1.0
 Security Guide : 8AL90705USAE Ed.1.0
 SNMP Proxy : 8AL90708USAD Ed.1.0
 Accounting and VoIP ticket collector : 8AL90709USAB Ed.1.0
 Users management API : 8AL90710USAA Ed.1.0
 OpenTouch™ Suite RTU Metering Feature : 8AL90712USAC Ed.1.0
2.2 Patches
2.2.1 Mandatory patches delivered with the DVD-ROM version

In the \Patches\Mandatory folder you will find:
File name Fixed crms Fixed anomaly
Patch_260705A_JAR_V2.zip crqms00179613 RTU PURGE and RTU Counter Calculation Failed in Daily and Weekly Job
crqms00175145 DM: latest 8770-oxe-tpl and dm model jar files are missing in the package
Patch_260705B_JAR_WAR.zip crqms00179184 Last zoomIn/Out are not saved in topology view
crqms00179060 DM: Grid filter search fails in parameters tab of device management for
OT and OXE
crqms00179142 Topology : Inter-node links are not properly linked between nodes
crqms00179421 Topology: after resizing the topology grid, a graphical shift appears
between network elements and the background map
Patch_260705C_JAR_WAR.zip crqms00179413 Topology : Navigation should be same in both the standard and custom
views
crqms00180075 R2.0.09.02.a/Topology/error message “nullcommand”/1-178645979
crqms00180067 Alarms : Connect and Configure from grid throws exception
crqms00180069 Alarms - Could not update the alarm tree
crqms00180085 latency in alarms diplays in Alarm module
Patch_260705D_SQL.zip crqms00179465 RTU: Duplicate Adminnmc folder is created during upgrade
Patch_260705E_JAR_AAR.zip crqms00180306 OT R10.0 [UUM]: Some issues when creating users in UUM
crqms00180305 Column labels not displayed for OT attributes in grid view

crqms00180139 8770 : Audit Filter issues
crqms00180167 Open API: OVApplException error thrown during Get all request on users
crqms00180101 Unable to create OXE with OT users in web client in grid view
Patch_260705F_WAR.zip crqms00180180 Topology:no switching to Highlight mode for alarms display
Patch_260705G_EXE.zip crqms00180168 Audit System data processing taking longer time
crqms00180176 Audit: audit server crashes when reading an audit file
Patch_260705H_JAR_AAR_EXE.zip crqms00178869 OXE Configuration:During user creation, set type attribute is by default not
filled with analog
crqms00176886 OT Configuration:locating of a node is not working when we locate at the
time of creation of user
crqms00180153 Impossible save SBC WAN for smartphones
crqms00180572 GUI for keys management –wrong picture for 8082 phone
crqms00180680 Alarm Service Crash
crqms00179702 T Configuration: Client becomes non responsive (blank screen) after
creation of devices(Only specific scenario)
crqms00179647 OT Configuration: Directory Number Range should not update while device
is created with device number
crqms00180368 Device Association get failed to Existing OT user
Patch_260705I_WAR.zip crqms00179451 Topology: after having added a network element, the current cursor turns
automatically into a "Select object" cursor type while "create NE" mode is still
enabled
Patch_260705J_JAR_AAR.zip crqms00180943 cut and paste to and from a replicated suffix is not possible/1-181281706
config OT -search 8082 device -> exception
crqms00179680 SIP password security policies problem
crqms00179136 SIP password management not take into account if I allow trivial SIP
crqms00180885 passwords
Patch_260705K_WAR_V1.zip crqms00181513 Keep on validating custom topology will discard all custom elements from
the topology
crqms00178957 Topology - alarm bubbles are moved far from its element
crqms00181493 Topology application : going back from alarms , the custom topology is not
displayed
crqms00181497 8770 Topology: Sub Branches not listed in the tree
crqms00181342 8770 topology - syntax error in french on service name
crqms00181329 Short description of custom elements was not displayed in topology
crqms00181328 Resizing the tree side window results in hiding the tree panel in both
standard and custom topology
crqms00181308 topology - space problem in topology view when big set of OT nodes -
name overlapping
Patch_260705L_EXE.zip crqms00180387 OT config failure after restore with rehosting/1-181070841
Patch_260705M_JAR.zip crqms00180988 OXE configuration/it takes too much time to display a search result/1-
181292239
crqms00171473 Users/devices : Association of existing device throws error in few cases
Patch_260705N crqms00181978 Topology : Alarms page is opened in Topology application

crqms00180731 Topology/Mouse is not leaving in topology std and custom/1-181193661
crqms00182007 Topology/native peer dead unexpectively when zooming in/1-181600411
crqms00181932 Topology:standard view mixed with custom one
Patch_260705O crqms00178396 Topology : Network nodes ar not updated at subnetwork level in standard
tree
crqms00182536 Topology/switching from Topo to Alarms not working in Custom view

Patch_260705P crqms00181271 Archiving of accounting records fails
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 Optional patches

Some patches, specific to rarely used applications can be available on the DVD-ROM, Tools\Optional
Patches folder. (No specific patch delivered in this version)
2.3 License file

For more details, refer to the technical communication TCV039-Ed07 OmniVista 4760 licenses.
 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
License version 1 2 3 4 5 6 7 7
Note For maintenance reasons, it’s possible to keep the same license to upgrade a server to release n+1.
In this case the new features controlled by license will not be available in the new release
2.4 Versions of embedded software

JRE® LDAP Oracle® MariaDB® Apache® PHP®
1.7.0_b147 11.1.1.5.0 5.5.35 2.4.12 5.3.29
Tomcat® JBOSS® EJBCA® 7-Zip
7.0.56 6.1 4.0.10 9.2

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

Windows®7 SP1 Professional (64 bits)
Windows® 2008 Server R2 Std Ed. SP1
Windows® 2008 Server R2Std SP1
Windows® 8 Professional (64bits)
Operating System Windows® 2012 Server Std Edition
Windows® 8.1 Professional (64bits)
Windows® 2012 Server R2 Std Edition
Windows® 2012 Server Std Edition
Windows® 2012 Server R2 Std Edition
Processor 1 processor Dual-Core 2 GHz 1 processor Quad-Core 2.5 GHz
RAM (minimum) 4 GB 6 GB
Minimal characteristics
80 GB 120 GB (disk: RAID5)
of Hard Disk
Graphics board 128 MB
Network card Ethernet 10/100Base-T
Partition 1 NTFS partition for installation of the LDAP server
Internet browser Internet Explorer® (version 9/10/11)
Mozilla FireFox® (version 41)
Drives A DVD drive is required
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.
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/uninstallation 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\System
32
\WindowsPowerShell\v1.0\
 The name of the computer must not have the following characters: ., -, +,_ (dot, dash, plus, underscore).
You make sure that the "NetBios name of the computer" is the same as the "name of the computer". To
read the "NetBios name of the computer", click on the button Other from modification window of the
name of the computer.
3.2 PCX compatibilities
3.2.1 IP, IP/X25, connections to OmniPCX Enterprise
OV8770 Releases PCX Releases Software version equal to or higher than IP Connection or IP/X25
>=R1.3 6.0 to 8.0 F1.602.3.i to G1.302.6.q yes
>=R1.0 8.0.1 G1.503.35.h Yes
>=R1.0 9.0 H1.301.50.a Yes
>=R1.0 R9.1 I1.605.39 Yes
>=R1.0 R10.0 J1.410.53.a Yes
>=R1.1 R10.1 J2.501.19.a Yes

>=R1.2 R10.1.1 J2.603.29.b Yes
>=R1.3 R11.0 K1.400.30.f Yes
>=R2.0 R11.0.1 K1.520.22.b Yes
R2.5 and R2.6 R11.1 L1.301.17.f Yes
R2.6.7 R11.2 L2.300.20.x Yes

Warning PPP connection is not supported.
3.2.2 OpenTouch
OV8770 Releases PCX Releases Software version equal to or higher than …

>=R1.0 R1.0.1 1.0.100.040
>=R.1.1 R1.0.1 1.0.100.060
>=R1.1 R1.1 1.1.000.080
>=R1.2 R1.2 1.2.000.051
>=R1.3 R1.3 1.3.000.061
>=R2.0 and R2.5 R2.0 2.0.000.90/2.0.100.32/2.0.200.4x
>=R2.6 R2.1 2.1.000.092
R2.6.7 R2.1.1 10.0.000.042
3.2.3 OmniPCX Office
OV8770 OXO
Releases Releases Software version equal to or higher than …
>=R1.2 5.1 510/063.001

>=R1.2 6.1 610/051.001
>=R1.2 7.1 710/096.001
>=R1.2 8.2 820/055.001
>=R1.2 9.0 900/051.001
>=R1.3 9.1 910/021.001
>=R2.0 9.2 920/048.001
>=R2.5 10.0 100/026.001
>=R2.6 10.1 101/014.001
R2.6.7 10.2 102/019.001
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 Number of OmniPCX Enterprise software locks

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 Open Touch locks Description

Configuration OAMP_CONFIG Configuration GUI
Alarms OAMP_ALARMS Alarms sending
Performance OAMP_VOIPPERF VOIP tickets sending
OAMP_PERFKPI SNMP data sending
and mlsnmp
3.3 Prerequisites of administration Client PCs

HARDWARE AND SOFTWARE (Minimum)
Operating System Windows®7 SP1 Professional (32 or 64 bits)

Windows® 8 Professional (32 or 64bits)
Windows® 8.1 Professional (32 or 64bits)
Processor Intel® Core 2 GHz
This processor type is given as example. The frequency clock is a minimum
requirement.
RAM 4 GB
Hard drive 40 GB
Graphics board 4 MB video memory with a resolution of 1024 x 768, 16 million colors
Monitor 17 inches (19 inches recommended)
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.
3.4 Prerequisites of Client PCs for directory consultation via WEB

HARDWARE AND SOFTWARE (Minimum)
Operating System All Windows versions
Google Chrome® R43 to R45

4 INSTALLATION AND UPGRADE
Consult the Installation Manual for the detailed operations for installation and upgrades.
4.1 Installation
 Starting from Windows 7, when using an account different from “Administrator”, to start the
server installation or an Upgrade, right click on the ServerSetup.exe file and select the option
Run as administrator. Otherwise the installation would fail.
 The firewall may generate messages asking for allowing communication for Java.exe and bin_ns-
slapd.exe programs. You have to validate these requests.
 It’s mandatory to manage a fix IP address (and not a DHCP one) and also the default gateway before
starting the server installation.
 The server name cannot contain the following characters: «/\[]":;|<>+=,?* _ ». In the opposite case,
the server installation would fail.
 If a previous Java version is already installed on a machine, it will be updated to Java 7 during OV8770
server or client installation.
As a consequence, to have OmniVista 8770 and OmniVista 4760 clients in the same machine then the
clients have to be installed in the following order:
 OmniVista 8770 client
 OmniVista 4760 client
 It is not allowed to modify the default HTTP (80) and HTTPS ports (8443) for compatibilities reasons with
the Performance application. The port 443 has as well to be available for Apache.
4.2 Server Upgrade
Warning  The server upgrade from 1.3 and 2.0 releases to R2.6.7 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 R2.6.7. The data have to be
processed before the upgrade.
 The server can be upgraded to 2.6.07.05.a from the following versions:

 1.3.11.00.a
 2.0.09.01.a
 2.0.09.02.a
 2.0.09.03.a
 2.5.04.00.a
 2.6.05.01.f
 2.6.07.01.a

 Starting from Windows 7, when using an account different from “Administrator”, to start the
server installation or an Upgrade, right click on the ServerSetup.exe file and select the option
Run as administrator. Otherwise the installation would fail.
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.
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 uninstallation. In this case it has to be
deleted before starting a new installation.
In case of server uninstallation 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
6.1 Description
The goal of the OmniVista 4760 to OmniVista 8770 migration is to export the following data from an
OmniVista 4760 R5.2 server to import them in a new OmniVista 8770 server.
If an upgrade to R5.2 from previous releases is required, a temporary license can be asked by an eSR.
Only 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 MANAGMENT
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.
7.2 Users management and OXE profiles

You need to validate the following parameter on OmniPCX Enterprise :
System\Other System Param\System parameters\Use profile with auto. Recognition=yes.
Otherwise no data will be inherited from the profile at a user creation.
The document TC1520-ed.02 describes the User’s management.
7.3 PKI
A certificate has to be installed in the default browser to be able to launch the Administration page of the PKI
application.
It is located in the 8770\certificates folder (superadmin.p12.
You need to import it in the Personal and Trusted Root certification Authority tabs. (For Internet
Explore:Contents\Certificates).
The required password is the one entered at the server installation time (ejbca by default).
7.4 Server IP address or server name modification

In order to change an OmniVista 8770 server name, we 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 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.5 MSAD synchronization and CMISE security
In the case where a secured access for configuration is managed for an OXE PCX, the user” MSAD8770Admin”
has to be added to the authorized users list at PCX side. This is mandatory to allow users creation from the
Web client that can be launched from the MSAD server.
Warning
The password of the account MSAD8770Admin must not be changed in the Security application
7.6 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.7 Disable Java update

The installed java version must not be updated. The automatic update function must be disabled.
Note
In windows 7, if the Java update parameters are not displayed in the Java control panel, you have to do the following:
Click Start. In the Start Search box, type command.

1. The result list will appear. Right-click Command Prompt in the Programs list.
2. Click Run as administrator
3. To open the Java Control Panel, in the Command Prompt window execute this program:
"c:\Program Files (x86)\Java\jre7\bin\javacpl.exe"
4. In the Java Control Panel, click on the Update tab.
5. Uncheck the automatic updates.
6. Click Apply and then OK to save settings
7.8 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.

8 NEW FEATURES
8.1 New PCX versions supported

 OpenTouch™ UP TO 2.1.1
 OmniPCX Enterprise up to 11.2
 OmniPCX Office up to 10.2
8.2 8038 Premium Deskphone support for OpenTouch
A new phone set 8038 Premium Deskphone is supported in the OpenTouch 2.1.1 as a middle-range SIP
device.
The management of this device is done from the 8770 DEVICES and USERS applications. The 8770 device
management is in charge of configuration and binary deployment. The files (configuration and binaries) are
stored in the OpenTouch server and downloaded from this location by the devices.
The 8038 is counted as an ALU device in the OmniVista 8770.
Provided features
- The device parameters are retrieved in the DEVICES application inventory.
- Auto discovery of the MAC address.
- Binary deployment per group of devices: a binary version and a set of applications can be deployed
for a limited group of OpenTouch devices.
- management from DEVICES and USERS applications, AD Client and OpenAPI
- Management with Mac address (unallocated pool) or with key and password (self-assignment).
- Management with or without profile. Creation and association to OpenTouch user through metaprofile.
- Management from mass provisioning files

8.3 8001 DeskPhone support for OpenTouch
A new phone set 8001 DeskPhone is supported in the OT 2.1.1.

The management of this device is done from the OmniVista 8770 DEVICES and USERS applications. The
OmniVista 8770 device management is in charge of configuration and binary deployment.
The files (configuration and binaries) are stored in the OpenTouch server and downloaded from this location
by the devices.
The 8001 DeskPhone is counted as a non ALU device in the OmniVista 8770.
Limitations
- Auto discovery of the MAC address is not provided by the 8001 DeskPhone device; therefore the
management through metaprofiles is not provided (USERS, AD Client and OpenAPI) nor through
profiles (OpenAPI)
- No management from from AD Client nor OpenAPI.
- The device parameters are not available in the DEVICES application inventory.
- The management of the certificates is done outside the 8770.
- The management of the keys is not available from the DEVICES application.
- Binary deployment per group of devices is not supported : 1 binary per OpenTouch instance for all the
OpenTouch users
8.4 Support of Chrome web browser for OmniVista 8770 web Client
Chrome web browser has been validated as a web Client for Directory only (no Network Management).
8.5 New settings for 8088 Deskphone in hospitality mode for OmniPCX
Enterprise
New settings are available to obtain similar features as the ones available for the 8082 MyIC Phone devices.
8.6 Topology application enhancements

 Zoom in/out and navigating into extended views features have been improved
 The alarms severity display has been changed. It’s now possible to choose (Preferences) between
“bubbles” and a colored border around the icons.

8.7 Enhancement of the person’s automatic creation process in the directory
The Automatic Creation process is part of the synchronization process (complete, partial, or on the fly thru
OT/OXE management notifications).
The general auto-creation mechanism is as follow:
As soon as an entry is added in the Technical Directory (Configuration application), first a matching person is
searched in the Company Directory (same name and firstname).
When such an entry does not exist, the automatic creation process checks if the technical entry matches the
automatic creation criteria defined in the Administration application.
The criteria are related to OXE objects / OT users and (new from 2.6.7) to some attributes values.
Note When the Call by Name attribute is not validated at OmniPCX Enterprise side, the corresponding person is
created in the Directory with Red confidentiality.
If it matches then a Person is created and links are set between the Person (Company Directory) and the
system entry (OXE or OT user).
In the OmniVista 8770 2.6.7, the additional automatic criteria addresses only the OXE users, in order to avoid
the creation of persons for hotel/hospital rooms, desksharing sets and nomadic devices.
To fully check the automatic creation criteria, some additional attributes are synchronized from OXE
and stored in the Ldap directory for further operations:
 Hotel-set operation (room/administrative)
 Set function (desksharing user, desksharing set)
 ghost_Z and ghost_Z_Feature (nomadic)
When the “limit to real users (OXE)” parameter is checked, room sets, ghost sets for nomadic feature,
desksharing virtual sets are excluded from the automatic creation process.
This is done according to a string (Ldap filter format) given in the Expert tab. Edition is reserved to Expert
administrators.

This ldap string can also be modified to exclude the creation of other sets types.
The default string is as follow:
(&(phoneFunction=pbxAdministrative)(|(setRole=Default)(setRole=DSU))
(!(stationType=GAP_ENHANCED))
(!(stationType=MIPT_300))
(!(stationType=Extern_Station))
(!(stationType=GAP_HANDSET))
(!(stationType=UA_VLE_CORDLESS ))
(!(stationType=UA_DECT_2G))
(!(ghostZ=1))
(!(ghostZFeature=NOMADIC_FEATURE)))
8.8 Manage OmniPCX Enterprise devices key profiles in Metaprofiles

The OXE Metaprofile is enriched with a new attribute ( Key Profile), non mandatory, and build as a fixed
enumerated list:
 None (default)
 Company
 Hotel
 Hotel Client
 Agent,
 ACD authorized phone set
 Supervisor
 Company 2
 Company 3

At the OmniPCX Enterprise side the “key profile” is named “Key Function”.
8.8.1 Key profile creation in the OmniPCX Enterprise

1- Create a user that will be used as a Key Profile
 Set function= Profile
 Set type=the set type for which you are creating a Key Profile
2- Manage the Prog. Keys for the user

3- Associate a Key profile directory number to the combination Key function (company, hotel…) + Set
physical type

8.8.2 User creation in OmniVista 8770
1- Create a metaprofile including the key profile, the device type and the OXE profile.
2- Create the user thanks to the metaprofile.
Device Type=4035T + Key Profile=Agent => Profile directory number
8.8.3 User creation from AD client, Open API or Mass Provisionning file
From the AD Client, from the user schema or from the User template file, a “Key function” attribute is added
where the Administrator can overwrite the value from the OXE metaprofile.
8.9 Identification of new types of ALE Deskphones

8.9.1 Devices creation in the USERS application
OmniVista 8770 2.6.07 associated with an OmniPCX Enterprise running at least R11.2 allows to differentiate
between devices from old and new ranges.
 Old range :
IPTouch 4028, 4038, 4068, TDM 4029, 4039, 4069
 new range :
IPTouch 8028, 8038, 8068, TDM 8029, 8039
When creating an OXE user from the USERS application, the drop list that proposes the possible devices is
enriched with the new types (8029, IPTouch 8028, 8039, IPTouch 8038) to replace the old ones (4029/8029,
4039/8038).

Old types New types
However the list displayed is independent from the OXE release, meaning some device types may be proposed
that doesn’t exist on a given OXE; the device type as managed on OXE is got after synchronization.
For example, in case the Administrator selects an 8029 device while the target OXE knows only about
4029/8029, the user will be created with 4029/8029 device type and this value will be returned from OXE
(configuration query or synchronization).
The same list is also available from AD Client and OpenAPI with the same remarks.
Note that after an OXE upgrade to R11.2, the device type is updated in 8770 applications only after OV8770–
OXE synchronization and given the device recognition is requested on OXE side, through the parameter
System\Other System Param.\System parameters\Force Type Identification option.
8.9.2 Keys management using a graphical view

The goal is to use a graphical view of the sets to easily manage the keys of these sets, identified by their
location on the device and not only by their number.
The areas where the keys are displayed are clickable and give access to the content of the keys.
The Software keys (virtual add-on) are accessible through the navigation keys mapped on the
image.
The physical add-ons are also manageable from this application in separate tabs.

From the OXE release 11.2 (OXE L2) new types of devices are added to distinguish new device range from
previous range. It means that when the 8770 is managing an OXE running this release (and upper) the
graphical view displays the proper image of the managed device.
Note that when the 8770 is managing an OXE running previous releases, the images of the old range sets are
used to manage new range sets. This means also that for these OXE instances, the 4 physical keys of the
8028/8029 phone sets are managed as software keys, accessible from the navigation keys.
From OXE k1 (OXE 11), the number of keys on the virtual add-on can be set to 40 instead of 72 :
this is done through a global system option : System > Other System Parameters > Spec.Customer
Features Parameters > x89 40 keys AOMV.
This parameter is read at the Graphical View application start to determine the number of
virtual keys.
8.9.3 Support of the new devices in RTU

The KAT008 (STD USER DIGITAL DEVICE) KPI definition is updated to take into account the new TDM devices
types (4029, 8029, 4039, 8039).
Similarly the KAT109 (STD USER IP DEVICE) KPI definition is updated to take into account the new device
types (IPTouch 4028, IPTouch 8028, IPTouch 4038, IPTouch 8038, IPTouch 4068, IPTouch 8082, IPTouch
8068)
8.10 New RTU KPIs

Some new KPIs are added for OpenTouch ID, OmniPCX Enterprise OMS Media Services, Fax pages number,
Automated Attendant ports, Contact Center connections.
Raw data are collected from OmniPCX Enterprise and OpenTouch nodes during the daily synchronization.
8.10.1 OpenTouchT ID
The Opentouch Id is retrieved from the OpenTouch node during the synchronization.
It is exposed in the header part of the RTU grouped report and MCS grouped report in the same place as the
OXE CPU ID. No identification of the value (no KATxxx).
This KPI is available only from OT 2.1.1. For lower OT releases, the field is left blank in the reports.
8.10.2 OmniPCX Enterprise OMS

The KPI is evaluated by counting the number of OMS declared on the OXE node (Rack with
attribute “OXE Media Server” enabled). It is available in all the reports (grouped or consolidated, normal or
MCS) as KAT054.
This KPI can be evaluated only from OXE R10. For the OmniPCX Enterprise running older releases, the KPI is
not evaluated.

ID NAME OFFER DESCRIPTION TYPE
KAT058 NB OF OMS RTU OT.EC 2.0 Number of OMS (software Media Server) Integer
declared by admin
8.10.3 Fax pages

For remind the OmniVista 8770 R2.0 already exposes the Fax Users KPI.
With a similar synchronization mechanism, the OT gets the number of pages sent from the Fax Server and
makes it available so that the 8770 gets it during synchronization. The value is retained when it is marked as
consistent by the OpenTouch.
The KPI is added in the RTU reports, consolidated or grouped for OpenTouch part, with max, min, average
and samples depending on report types.
The value exposed by OpenTouch is a per day value; meaning the max value is the max value calculated on a
day. The total number of sent pages can be got with the average and the number of samples.
This KPI is available only from OT 2.1. For lower OpenTouch releases, the KPI is not evaluated.

KAT057 FAX SENT PAGES RTU OT.EC 2.0 Number of FAX pages sent from the Fax Integer
Server
The OpenTouch values can be checked here:
8.10.4 Automated Attendant ports numbers

As a reminder OmniVista 8770 R2.6 already calculates the KPI KAT055 related to the activation of the
Automated Attendant.
The new KPI is related to the number of ports configured to support the Automated Attendant
The OmniVista 8770 gets this value during synchronization.
The KPI is added in the RTU reports, consolidated or grouped for OT part, with max, min, average and
samples depending on report types.
This KPI is available only from OpenTouch 2.1.1. For lower OpenTouch releases, the KPI is not evaluated..

KAT056 AA PORT NUMBER OT.EC 2.0 Number of port configured Integer
The OpenTouch values can be checked here (AA ports):

8.10.5 Call Centers
The new metrics for Call servers are:

KAT040 CALL CENTER AGENT OT.EC 1.3 CCD Agents: Number of logged CCD agents Integer
BASE USER RTU
KAT041 CALL CENTER CCA OT.EC 1.3 CCA Agents: Number of logged CCA agents Integer
OPTION RTU
KAT042 CALL CENTER WFM OT.EC 1.3 Use of WMI : 0 if not used, number of CCD Integer
OPTION RTU Agent if used
KAT043 CALL CENTER CRI OT.EC 1.3 Use of CRI : 0 if not used, number of CCD Integer
OPTION RTU Agent if used
KAT044 CALL CENTER OT.EC 1.3 Use of Soft Panel: 0 if not used, number of Integer
SOFTPANEL OPTION CCD Agent if used
RTU
KAT045 CALL CENTER OT.EC 1.3 CCS Light : Number of connected CCS Integer
SUPERVISOR LIGHT
USER RTU
KAT046 CALL CENTER OT.EC 1.3 CCS Mono: Number of connected mono-site Integer
SUPERVISOR MONO CCS
USER RTU
KAT047 CALL CENTER OT.EC 1.3 CCS Multi: Number of connected multi-sites Integer
SUPERVISOR MULTI CCS
USER RTU
These KPI are available from OmniPCX Enterprise 10.1.1 (j2.603) in files downloaded during daily
synchronization.
For OmniPCX Enterprise nodes, running lower versions, the KPI are not shown in the reports.
For non CC nodes, but running the correct version, the KPI are valued as 0.
In the consolidated reports, the values are added up over the OmniPCX Enterprise.

8.11 Security: POODLE vulnerability
This release addresses the POODLE (Padding Oracle On Downgraded Legacy Encryption) vulnerability (CVE-
2014-3566) linked to the support of the obsolete SSLv3 protocol. The global solution is to remove the support
of this protocol (and older SSLv2 too) to use only TLSv1.0 and upper.
This has an impact on the whole environment (network elements such as OmniPCX Enterprise, OmniPCX
Office and OpenTouch), SIP devices and external servers (Active Directory, mail server, Radius server, SNMP
hypervisor, …). Meaning as long as all the eco-system is not TLS compatible, it is not possible to fully disable
the support of SSLv3 from OmniVista 8770 server.
The solution is then to enable only TLS in fresh installation, to remove support of SSlv3 during OmniVista 8770
upgrade and to provide a tool that will enable/disable the SSLv3 protocol depending on the eco-system.
Restriction:
The Poodle vulnerability is not fixed in the Oracle Directory Server release embedded in the OmniVista 8770
2.6.7 (ODSEE 11.1.1.5). The update to ODSEE 11.1.1.7.2 will fix it in OmniVista 8770 R3.0.
The status for ALE equipments is given in the below Erreur ! Source du renvoi introuvable. (for the SSL
layer used by OmniVista8770)
Eco system Status

4018/4028 OXE SIP device SSLv3/TLSv1.0 supported
NOE: 4.33.20 SIP mode: not supported
8001 OXE SIP device SSLv3/TLSv1.0 supported.
8012 OXE SIP device R110.3.54.1
SSLv3/TLSv1.0 supported
SSLv3 removed from R300.01.015.9
SSLv3 removal planned for Q12015
MyICPC SIP Vulnerable.
extended support is provided only in the last release
where the vulnerability is fixed (6.7.400.300.d).
Thomson ST20xx Vulnerable
OXE Vulnerable, but SSH and SFTP are not concerned by
the Poodle vulnerability
OT SSLv3/TLSv1.0 supported.
SSLv3 removed from OT 2.1.1
OXO Vulnerable up to OXO 9.2
The tool 8770\bin\ToolsOmnivista allows to enable/disable the SSL protocol.

This operation changes the Apache configuration (8770-httpd-ssl.conf), store the status in the Director Server
(cn=OmniVista 8770, o=nmc, attribute sslv3=0) and restart the services.
The Apache configuration is now saved during a server backup.

9 RESTRICTIONS
9.1 8082 MyIc Phone on OmniPCX Enterprise and Https requests

Http requests from 8082 MyIc Phone to OmniVista 8770 server are no more supported.
Http requests are now mandatory. The OmniVista 8770 server is checking the device certificate at each file
downloading request.
A particular care has to be taken before doing an upgrade to R2.6. Make sure the devices
are doing https requests and not http ones.
9.2 VOIP quality supervision

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

At client starting, the Java application is requiring by default one 1 Gb contiguous memory range. This value is
defined is the client launching file: Client8770 R2.0\bin\runnmc.bat (-mx1024m).
The Windows7 operating system being reserving more memory than Windows XP for all applications, the
probability to not get the sufficient memory size is more important.
In this case, the following message is displayed:
The proposed workarounds are:

- Insert the OV8770 client in the programs list to be automatically launched at Windows starting.
- Modify the minimum required size for Java at starting. (Client8770 2.0\bin\runnmc.bat, javaw.exe" -
Xmx1024m)
- Warning: decreasing this value may result in reduced client performances (to be reserved for limited
uses)
- Close other applications

9.4 Topology
9.4.1 Loss of customized topology views after an upgrade
The Topology application has been re-designed in R2.0.
The customized views from releases older than R2.0 will be lost after an upgrade from these releases to R2.O
and next versions.
9.4.2 Time to display the data

The time to display the tree and the view after opening the application is around 1 minute.
The first display for the other view (Custom or Standard) is near the same.
Next switches from one view to the other are then happening normally.
9.5 USERS
Users creations fail when the Entity 1 does not exist on the OmniPcx Enterprise.
The reason is that the user creation by profile is failing in this case. The system tries first to create the
user, using the default parameters (including missing entity 1) before applying the profile’s
parameters.
9.6 OmniTouch 8400 ICS users management
Warning An OXE user with ICS rights will be counted for 2 users at the license level.
This is not managed by ACTIS.
9.7 OmniVista 8770-MSAD synchronization

 The « user name » field managed at the Access Info level should contain the full DN and not the
simple user’s name.
Example : Cn=admin,CN=Users,DC=Alcatel-Lucent,DC=com
 The MSAD8770Admin account password should not be modified in the Security application.
Otherwise the MSAD web client will not work.
 In the synchronization rules, it’s forbidden to select the MSAD directory root as MSAD Location.
When this level is selected for one of the rules, the synchronization fails.
 It’s not allowed to create users whose name contains specific characters (UTF8) using the MSAD
web client.
 The attributes « manager » and « assistant » can only be synchronized from MSAD to OV8770
 When using Internet Explorer 8 or 9, it’s mandatory to validate the « active scrpting » to allow
the web client refresh after a meta-profile selection.
Tools\Internet Options\Security\Internet\Custom level \scripting\enable “active scripting”
9.8 OpenTouch alarms display

OT Alarms will not be displayed if two OpenTouch have same “SNMP v3 user name” but different parameters
(like encryption password, passphrase, etc..).To receive the OT alarms from all the declared OT nodes, there
are two possible configurations:

1. 1st option: use the same “SNMP v3 user name” and same associated parameters (security
level, user password, passphrase, …) for all the OpenTouch nodes
2. 2nd option : use a different “SNMP v3 user name” for each OT node
Special character quotes (") will not be accepted by the SNMP.

In-case either authentication password or encryption password includes quotes then OV8770 will not receive
alarms from OT.

10 DEFAULTS FIXED in R2.6.07
List of the fixed defaults for cases found in all 2.6 versions.
id headline TSref
crqms00158523 Unified User mngt : grid edit slow 1-170905951
crqms00169406 2.6.05.01/Alarms/Cyclic restart of Alarm service/1-172919271 1-172919271
crqms00164415 8770 R2.6.05.01/USERS/it takes a too long time to display users in the grid/1- 1-173551611
173551611
crqms00166585 On 8770 add a user in the user group doesn't work as define. 1-173625539
crqms00166156 OV8770 2.6 Topology: "Erreur pendant la validation, se reporter au fichier 1-173755248
d'erreur" - 1-173755248
crqms00170785 2.6.05.01/2.5.04/Alarms/No config module loading1-173968161 1-173968161
crqms00168520 8770 : Missing tooltip on UUM for SIP password 1-174452911
crqms00166558 8770 R2.6/Topology/zoom/desynchro between colored background and 1-174489261
network elements/
crqms00166560 8770 R2.6/Topology/zoom/moving to subentries in the tree/1-174489400 1-174489400
crqms00166610 8770 R2.6/Topology/horizontal scrolling bar disappears/1-174515651 1-174515651
crqms00166633 8770 R2.6/Topology/incorrect behaviour adding a colored background/1- 1-174517162
174517162
crqms00166638 8770 R2.6/topology/alarm piles are overlapping/1-174517261 1-174517261
crqms00166641 8770 R2.6/Topology/Alarm pile size difference/1-174517414 1-174517414
crqms00173288 2.6.05.01/Accounting/PurgePeriod/1-174777371 1-174777371
crqms00169530 8770 R2.6.05.01/Problem to import via migration tool R2.6.05.01/1-175435953 1-175435953
crqms00168562 8770 R2.6/Server installation failure/1-175498503 1-175498503
crqms00169319 2.6.05.01/FREAK and JBOSS jmx-remoting.sar vulnerability/1-175576211 1-175576211
crqms00168716 770 R2.6/USERS/filter on 4019 returns also IpTouch 4018/1-175583011 1-175583011
crqms00172508 Security issue on OpenTouch after a security scan 1-175685221
crqms00178066 Scheduled OXE import fails on 8770 1-175728361
crqms00169497 8770 R2.6/Audit loading low performance and reliability/1-175842391 1-175842391
crqms00170708 In scheduler, daily job failed because of Audit restarting 1-176412923
crqms00171962 MSAD plugin : after creation of user , the phone number is not displayed 1-176452301
crqms00172722 8770 R 2.6.05.01 / Issue with Latvian characters in report 1-176531001
crqms00170936 8770 : In UUM, modification using copy/paste produces the lost of the ice link. 1-176650011
crqms00172149 8770 R2.6.05.01/After migration 1.3.11 to 2.6.05.01 8770 data backup job is 1-176797715
missing and executing job date changed/1-176797715
crqms00172249 Alarmserver and Syncldappabx restarting constantly 1-176813673
crqms00172760 8770 R2.6.05/Audit service is crashing at every loading attempt/1-176918019 1-176918019
crqms00171283 OXE configuration, the banner is missing when we consult devices settings. 1-176970267
crqms00176101 ISDN number wrongly constructed 1-177417234

crqms00172465 8770 R2.6.05/Alarm server is regularly restarting//1-177573821 1-177573821
crqms00174787 Deletion of PBX users via contextmenu is not possible via 8770 configure 1-177574931
option.
crqms00174372 /OV8770 R2.6.05.01f - Accounting report,issue with the (Address and City) 1-177689551
fields of the cost center.
crqms00180085 latency in alarms diplays in Alarm module 1-177811491
crqms00173887 Contacts are no longer displayed in Directory/Address Book after migration 1-177871364
crqms00173551 english syntax not correct 1-177901401
crqms00173642 error message syntax not proper English 1-177901455
crqms00176184 In security application :not possible to enter values in the Misc fields 1-178173641
crqms00174618 8770 2.6.05/Configuration/ Unable to view the german umlaut letter in device 1-178232951
graphical view (programmed key)/1-178232951
crqms00175964 8770 R2.6/OXE configuration/Validate and Cancel buttons are sometimes not 1-178447761
available/1-178447761
crqms00175161 8770 2.6.05/configuration/Unable to delete a single or multiple objects in 8770 1-178464161
main window grid (right side), it doesn't enable cancel or submit butt
crqms00178158 8770 R2.6/OXE configuration/using the arrows keys does not return the 1-178499740
expected result/1-178499740
crqms00176032 8770 R2.6/Topology/configure user actions returns an exception/1-178504166 1-178504166
crqms00175781 OT new device 8038 label not homogeneous 1-178935789
crqms00176484 contractnumber syntax not adequate 1-178984465
crqms00176503 From /8770/bin, ntsvcexClient tool doesn't work. 1-179253980
crqms00177400 OV-8770 R2.6.7.3.a issue with restore of Omnivista 8770 database. 1-179718107
crqms00177460 Topology : The icons tools are not well displayed and are cut. 1-179762031
crqms00181493 Topology application : going back from alarms, the custom topology is not 1-179776273
displayed.
crqms00179184 Last zoomIn/Out are not saved in topology view 1-179790030
crqms00177777 not possible to create OT user in OT 2.1.1 1-179800788
crqms00177714 8770 R2.6.07.03/PKI application is not starting/1-179891761 1-179891761
crqms00177725 OV 8770 - 2.6.7.03: topology with blank page (empty page) - 1-179891771. 1-179891771
crqms00177953 8770 R2.6.07.03/Audit/no data displayed in the Operations tab/1-180042151 1-180042151
crqms00178957 OV8770 2.6.7.04 - Topology - alarm bubbles are moved far from its element. 1-180322062
crqms00181501 OV8770 2.6.7.04 - Topology - element positions on map are not well saved. 1-180460871
crqms00179742 Accounting application and 8770 freezes when we try to create a time zone in 1-180752303
Carrier setting
crqms00180387 8770 R2.6.07.04/OT config failure after restore with rehosting/1-181070841 1-181070841
crqms00180572 OV8770 R2.6.7 : GUI for keys management - 8082 set management in NOE 1-181129541
mode : wrong picture (8088)
crqms00180799 8770 2.6.07.04/Topology/Scrollbar is present in standard but not in custom/1- 1-181224601
181224601
crqms00180885 SIP password management not take into account if I allow trivial SIP 1-181244433
passwords.

crqms00180947 8770-R2.6.07.05. the daily job remain blocked on load audit records task since 1-181281446
01:30 am,
crqms00180988 8770 R2.6.7/OXE configuration/it takes too much time to display a search 1-181292239
result/1-181292239
crqms00181417 8770 : OXECS telephone settings are not populated 1-181533679
crqms00181741 8770 R2.6.07.05/Topology/ background creation_dialog box is proposed 1-181707254
twice/1-181707254
crqms00181807 8770 R2.6.07.05/Topology/loss of customized data/1-181753431 1-181753431
crqms00182271 8770 R2.6/cut and paste to and from a replicated suffix is not possible 1-181831704
crqms00181978 Topology : Alarms page is opened in Topology application
crqms00180731 Topology/Mouse is not leaving in topology std and custom/1-181193661
crqms00182007 Topology/native peer dead unexpectively when zooming in/1-181600411
crqms00181932 Topology:standard view mixed with custom one
crqms00178396 Topology : Network nodes ar not updated at subnetwork level in standard tree
crqms00181271 Archiving of accounting records fails

11 KNOWN PROBLEMS
Here is the list of the problems that are not yet fixed. These are the problems detected in the current version
and in the previous 2.6 ones.
id headline TSref
crqms00175267 OV8770 // Radius Authent failing if password length = 16 characters 1-172523061
crqms00166355 8770 R2.6/Apache server randomly no more accessible/1-174192814 1-174192814
(a workaround solution is available on the demand)
crqms00176849 2.6.05.01/Alarm Generation when an account gets locked 1-174469131
crqms00172405 Synchronization issue between OXE and ICS. // 1-174788081 // 1-174788081
crqms00173499 accounting process set to no in PABX still sets are retrieved in Accounting 1-176132801
module
crqms00171596 Export of user data via access by Webclient fails : not enough menory to execute 1-177029401
request
crqms00176823 Alarms:SNMP component will not accept the double quotes special character in 1-177353081
passphrase
crqms00174167 8770 R2.6/OXE configuration/search in multiple nodes often fails/1-178229091 1-178229091
crqms00178210 //8770 Certificate Validity for MSAD plugin is for 1 year only 1-179024141
crqms00180845 8770 2.6.7.01: After migrating from 4760 to 8770, The SNMP service is not 1-180160951
stable.
crqms00180629 MySQL errors return daily in the Windows event logs 1-180193081
crqms00180237 "Select all" highlights only OXEs of same version in 4760 but not in 8770 1-180250053
crqms00181517 8770 R2.6.07.01.a/Reports/Customized graph in personalized 4760 report-lost of 1-180250081
defined XY axis values after migration to 8770 / 1-180250081
crqms00181624 Randomly OXE link unavailable on 8770 UUM 1-180473751
crqms00181119 is it possible to get "1.3.6.1.4.1.637.64.4760.9.1.16" (notifClearIncident). for 1-180645871
OTMS service restart?
crqms00182277 8770 2.6.07.01/UUM/Not Possible to change Users TUI Password to the same 1-180967171
digits once modified locally on the phone/1-180967171
crqms00181267 2.6.07.01/Multiple Vulnerabilities/1-181027321 1-181027321
crqms00180535 8770 R2.6.07.04/Directory/In Google chrome the custom themes search 1-181115102
windows in right side/1-181115102
crqms00181039 8770 R2.6.05.01.f/Administration/Value of automatic inheritance are not 1-181153361
translated correctly/1-181153361
crqms00181389 8770 2.6.05.01.f/Diagnostic tool/Error message while executing the Diagnostic 1-181153368
tool/1-181153368
crqms00180906 8770 R2.6/Directory replication/initialize and schedule buttons not easy to 1-181191955
select/1-181191955
crqms00181228 In configuration of Oxe, exporting TG shows fail error message though Export is 1-181274421
successful.
crqms00181232 8770 R2.6.7/link display disappears when mouse is over it/1-181448241 1-181448241
crqms00182410 8770 2.6.7.01: Tickets Archive is failing - 1-181461281

crqms00181316 OV8770 2.6.7.05: Topology - performance problem: displaying of content is too 1-181500809
slow.
crqms00181648 8770 R2.6.07.05/USERS appli/uncorrect label for 8038 phone/1-181636553 1-181636553
crqms00181959 VOIP total calculation task is failing 1-181700841
crqms00181835 8770 R2.6.07.05/Topology/icons for server services not displayed in the right 1-181758000
window/1-181758000
crqms00182218 8770 OpenAPi - automatically created users not respecting schema 1-181873371
crqms00182359 OV 8770 2.6.7.1: GCSConfig has problem and blocks daily task. 1-182001081
crqms00182516 8770- 2.6.7.01: several purge tasks are failing in the daily job 1-182084711
crqms00182522 8770 2.6.07.05/Topology/loss of customized icons after an upgrade/1- 1-182093821
182093821

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 -


8770 Installation Procedure Release 2.6.7

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

8770 Installation Procedure Release 2.6.7

Încărcat de

Drepturi de autor:

Formate disponibile

Release Note OmniVista 8770

TC 2105 ed. 01 Release 2.6.7

INSTALLATION PROCEDURE FOR OMNIVISTA 8770

Omnivista 8770 version 2.6.07.05.a is released today.

It is available on Alcatel-Lucent Business Portal (https://businessportal2.alcatel-lucent.com) and on DVD-ROM with the

4 INSTALLATION AND UPGRADE .............................................................................................................. 12

4.1 Installation ..................................................................................................................................... 12

5 SERVER UNINSTALLATION .................................................................................................................... 13

6.1 Description ..................................................................................................................................... 13

OmniVista 8770 - Release 2.6.7

10 DEFAULTS FIXED in R2.6.07 ................................................................................................................ 32

OmniVista 8770 - Release 2.6.7

OmniVista 8770 - Release 2.6.7

The documentation is no more provided on a CD.

2.2.1 Mandatory patches delivered with the DVD-ROM version

OmniVista 8770 - Release 2.6.7

Patch_260705N crqms00181978 Topology : Alarms page is opened in Topology application

OmniVista 8770 - Release 2.6.7

2.2.2 Optional patches

2.3 License file

2.4 Versions of embedded software

OmniVista 8770 - Release 2.6.7

3.1 Server PC prerequisites

3.1.1 Hardware and software

< 5000 users > 5000 users

3.1.2 Software and hardware compatibility

OmniVista 8770 - Release 2.6.7

3.1.3 Configuring the Server PC

3.2 PCX compatibilities

3.2.1 IP, IP/X25, connections to OmniPCX Enterprise

>=R1.0 R9.1 I1.605.39 Yes

>=R1.0 R10.0 J1.410.53.a Yes

>=R1.1 R10.1 J2.501.19.a Yes

>=R1.3 R11.0 K1.400.30.f Yes

>=R2.0 R11.0.1 K1.520.22.b Yes

R2.5 and R2.6 R11.1 L1.301.17.f Yes

R2.6.7 R11.2 L2.300.20.x Yes

OmniVista 8770 - Release 2.6.7

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

3.2.3 OmniPCX Office

>=R1.2 5.1 510/063.001

3.2.4 OmniPCX Enterprise and OpenTouch software locks

OmniVista 8770 modules Number of OmniPCX Enterprise software locks

OmniVista 8770 - Release 2.6.7

OmniVista 8770 modules Open Touch locks Description

3.3 Prerequisites of administration Client PCs

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

3.4 Prerequisites of Client PCs for directory consultation via WEB

OmniVista 8770 - Release 2.6.7

4.2 Server Upgrade

 The server can be upgraded to 2.6.07.05.a from the following versions:

OmniVista 8770 - Release 2.6.7

4.3 Client upgrade

6 MIGRATION FROM OmniVista 4760

OmniVista 8770 - Release 2.6.7

OmniVista 8770 - Release 2.6.7

7.1 SNMP Proxy feature

7.2 Users management and OXE profiles

7.4 Server IP address or server name modification

OmniVista 8770 - Release 2.6.7

7.6 Backup on network drive

7.7 Disable Java update

OmniVista 8770 - Release 2.6.7

7.8 Internet Explorer configuration