Tc2142en-Ed01 Release Note for Omnivista 8770 Release 2.6.7

8/16/2019 Tc2142en-Ed01 Release Note for Omnivista 8770 Release 2.6.7

1/40

Legal notice:

The information presented is subject to change without notice.

ALE International assumes no responsibility for inaccuracies contained herein.

Copyright © ALE International 2016.

Release Note OmniVista 8770TC 2142 ed. 01 Release 2.6.7

R ELEASE NOTE FOR OMNI V ISTA 8770 R ELEASE 2.6.7

V ERSION 2.6.07.06.B

Omnivista 8770 version 2.6.07.06.b is released today.

This document describes the installation procedure for OmniVista 8770 version 2.6.07.06.b.

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

reference 3BH11670 AGAD.

Revision History

Edition 1: January 29, 2016 creation of the document


2/40

OmniVista 8770 - Release 2.6.7

Release Note for OmniVista 8770 Release 2.6.7 Version 2.6.07.06.b.7 TC 2142 ed. 01 Copyright © ALE International 2016 page 2/40

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 ........................................................................................................................ 6

2.3 License file ....................................................................................................................................... 6

2.4 Versions of embedded software ......................................................................................................... 6

3 PREREQUISITES ..................................................................................................................................... 7

3.1 Server PC prerequisites ..................................................................................................................... 7

3.1.1 Hardware and software ............................................................................................................... 7

3.1.2 Software and hardware compatibility ........................................................................................... 8

3.1.3 Configuring the Server PC ........................................................................................................... 8

3.2 PCX compatibilities ............................................................................................................................ 8

3.2.1 IP, IP/X25, connections to OmniPCX Enterprise ............................................................................ 8

3.2.2 OpenTouch ................................................................................................................................ 9

3.2.3 OmniPCX Office .......................................................................................................................... 9

3.2.4 OmniPCX Enterprise and OpenTouch software locks ..................................................................... 9

3.3 Prerequisites of administration Client PCs ......................................................................................... 10

The use of Clients installed on a Citrix Presentation server XenApp 7.6 is validated. ................................. 10

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


3/40



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 IN 2.6.07.06.b ............................................................................................................. 18

There is no new feature in 2.6.07.06.b. ................................................................................................. 18

9 NEW FEATURES IN 2.6.07.05.a ............................................................................................................. 18

9.1 New PCX versions supported ........................................................................................................... 18

9.2 8038 Premium Deskphone support for OpenTouch ........................................................................... 18

9.3 8001 DeskPhone support for OpenTouch ......................................................................................... 19

9.4 Support of Chrome web browser for OmniVista 8770 web Client ........................................................ 19

9.5 New settings for 8088 Deskphone in hospitality mode for OmniPCX Enterprise ................................... 19

9.6 Topology application enhancements ................................................................................................ 19

9.7 Enhancement of the person’s automatic creation process in the directory .......................................... 20

9.8 Manage OmniPCX Enterprise devices key profiles in Metaprofiles ....................................................... 21

9.8.1 Key profile creation in the OmniPCX Enterprise ........................................................................... 21 9.8.2 User creation in OmniVista 8770 ................................................................................................ 22

9.8.3 User creation from AD client, Open API or Mass Provisionning file ............................................... 22

9.9 Identification of new types of ALE Deskphones ................................................................................. 22

9.9.1 Devices creation in the USERS application .................................................................................. 22

9.9.2 Keys management using a graphical view .................................................................................. 23

9.9.3 Support of the new devices in RTU ............................................................................................ 24

9.10 New RTU KPIs .............................................................................................................................. 24

9.10.1 OpenTouchT ID ...................................................................................................................... 24

9.10.2 OmniPCX Enterprise OMS ........................................................................................................ 24

9.10.3 Fax pages .............................................................................................................................. 25

9.10.4 Automated Attendant ports numbers ....................................................................................... 25 9.10.5 Call Centers ............................................................................................................................ 26

9.11 Security: POODLE vulnerability ...................................................................................................... 27

10 RESTRICTIONS ................................................................................................................................... 29

10.1 Management from a Web client is not working ............................................................................... 29

10.2 8082 MyIc Phone on OmniPCX Enterprise and Https requests .......................................................... 29

10.3 VOIP quality supervision ................................................................................................................ 29

10.4 Client launching failure on Windows7 ............................................................................................. 29

10.5 Topology ...................................................................................................................................... 30

10.5.1 Loss of customized topology views after an upgrade ................................................................. 30

10.6 USERS .......................................................................................................................................... 30 10.7 OmniTouch 8400 ICS users management ....................................................................................... 30

10.8 OmniVista 8770-MSAD synchronization .......................................................................................... 30

10.9 OpenTouch alarms display ............................................................................................................. 30

11 DEFAULTS FIXED in R2.6.07.06 ........................................................................................................... 32

12 KNOWN PROBLEMS ............................................................................................................................. 37


4/40



1 GENERAL

This document describes the installation procedure for OmniVista 8770 version 2.6.07.06.b.

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 8770maintenance. 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, youcan contact the "Professional Services" (mailto:[email protected] or your localServices representative).

https://businessportal2.alcatel-lucent.com/https://businessportal2.alcatel-lucent.com/https://businessportal2.alcatel-lucent.com/https://businessportal2.alcatel-lucent.com/https://businessportal.alcatel-lucent.com/alugesdp/faces/gesdp/integration/KCSKnowledge.jspxhttps://businessportal.alcatel-lucent.com/alugesdp/faces/gesdp/integration/KCSKnowledge.jspxmailto:[email protected]:[email protected]:[email protected]://businessportal.alcatel-lucent.com/alugesdp/faces/gesdp/integration/KCSKnowledge.jspxmailto:[email protected]://businessportal.alcatel-lucent.com/alugesdp/faces/gesdp/integration/KCSKnowledge.jspxhttps://businessportal2.alcatel-lucent.com/https://businessportal2.alcatel-lucent.com/


5/40



2 CONTENT OF THE SOFTWARE PACKAGE

2.1 References

- OmniVista 8770 Release 2.6.7 package : 3BH11669 AGAD

- OmniVista 8770 software DVD which contains: : 3BH11670 AGAD

Version Release 2.6.07.06.b

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_260706A_JAR.zip crqms00175145 impossible to access to voicemail hotel mode with 8082 / 8088

Patch_260706B_EXE.zip crqms00181624 Randomly OXE link unavailable on 8770 UUM

Patch_260706C_EXE.zip crqms00186281

crqms00184472

2.6.05.01/SNMP service on 8770 to be restarted manually for sendin

Traps/1-182571481

Alias is not updated immediately in Telephonic Device

Patch_260706D_EXE.zip crqms00183340 8770 R2.6.7.1/Configuration/node is regularly automatically deleted fro

configuration application /1-182415945

Patch_260706E_SQL.zip crqms00186515 8770 2.6.07.04/Topology/Modified image in topology is not take in accou

after save/1-181224708

Patch_260706F_WAR_V1.zip crqms00187033 NMC Service manager crashes after server upgrade

Patch_260706I_APACHE.zip

This patch is not installed automatically.

Refer to the procedure below.

crqms00166355 Apache server randomly no more accessible

Reminder:

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


6/40



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

ote 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 specific patches can be available on the DVD-ROM, Version\Paches\Manual folder.

The patch “Patch_260706I_APACHE.zip” has to be installed after a new server installation or upgrade.

The goal is to get rid of some random accesses to the Web server occurring with the Apache 2.4.12 defaultinstalled version.

This patch will replace the 2.4.12 version with the 2.4.17 one.

For servers with Windows 20012 R2 et Windows 8.1 it’s mandatory to first install the following Windows Updates: Windows8.1-KB2919442-x64.msu (https://www.microsoft.com/en-us/download/details.aspx?id=42153)

Windows8.1-KB2919355-x64.msu (https://www.microsoft.com/en-in/download/details.aspx?id=42335)

The patch has to be copied to the 8770\Install\Patches folder.

Then, launch the 8770\Install\PatcInstaller.exe command.

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 PCXnetwork 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®

https://www.microsoft.com/en-us/download/details.aspx?id=42153https://www.microsoft.com/en-us/download/details.aspx?id=42153https://www.microsoft.com/en-us/download/details.aspx?id=42153https://www.microsoft.com/en-in/download/details.aspx?id=42335https://www.microsoft.com/en-in/download/details.aspx?id=42335https://www.microsoft.com/en-in/download/details.aspx?id=42335https://www.microsoft.com/en-in/download/details.aspx?id=42335https://www.microsoft.com/en-us/download/details.aspx?id=42153


7/40



1.7.0_80-b15 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

Operating System

Windows®7 SP1 Professional (64 bits)Windows® 2008 Server R2 Std Ed. SP1

Windows® 8 Professional (64bits)Windows® 8.1 Professional (64bits)

Windows® 2012 Server Std EditionWindows® 2012 Server R2 Std Edition

Windows® 2008 Server R2Std SP1Windows® 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

of Hard Disk80 GB 120 GB (disk: RAID5)

Graphics board 128 MB

Network card Ethernet 10/100Base-T

Partition 1 NTFS partition for installation of the LDAP server

Internet browser Internet Explorer® (version 9/10/11)Mozilla FireFox® (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 andnot 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.


8/40



3.1.2 Software and hardware compatibility

The installation on a dedicated Server PC in accordance with the prerequisite allows a correct operation of thesoftware. 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 followthe 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 anexternal 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 betterto 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 have the following characters: ., -, +,_ (dot, dash, plus, underscore). Youmake 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


9/40



OV8770 Releases PCX Releases Software version equal to or higher than IP Connection or IP/X25

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

OV8770Releases

OXOReleases 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


10/40



Accounting 42 - Accounting users98 – Accounting for local calls (for local accounting use)99 – Accounting for ABC calls(for network accounting use)

Directory (STAP calls) 49 - Directory

Traffic observation 42 - Accounting users

39 - Performance VoIP 42 - Accounting users

Alarms 47 - Alarms

Secured SSH connection to OmniPCX

Enterprise

No specific lock for OmniPCX Enterprise. Security license for

OmniVista 8770

OmniVista 8770 modules Open Touch locks Description

Configuration OAMP_CONFIG Configuration GUI

Alarms OAMP_ALARMS Alarms sending

Performance OAMP_VOIPPERFOAMP_PERFKPI

and mlsnmp

VOIP tickets sending

SNMP data sending

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 GHzThis processor type is given as example. The frequency clock is a minimumrequirement.

RAM 4 GB

Hard drive 40 GB

Graphics board 4 MB video memory with a resolution of 1024 x 768, 16 million colors

Monitor 17 inches (19 inches recommended)

Internet browser Internet Explorer® (version 9/10/11)Mozilla FireFox® (version 41)

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 OMCtool is not compatible with Citrix.


11/40



3.4 Prerequisites of Client PCs for directory consultation via WEB

HARDWARE AND SOFTWARE (Minimum)Operating System All Windows versions

Internet browser Internet Explorer® (version 9/10/11)

Mozilla FireFox® (version 41)Google Chrome® R43 to R45


12/40



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 asadministrator. Otherwise the installation would fail.

The firewall may generate messages asking for allowing communication for Java.exe and bin_ns-slapd.exeprograms. 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 startingthe server installation.

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

If a previous Java version is already installed on a machine, it will be updated to Java 7 during OV8770 serveror client installation.

As a consequence, to have OmniVista 8770 and OmniVista 4760 clients in the same machine then the clientshave 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 thePerformance 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.06.b 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 2.6.07.05.a


13/40



Starting from Windows 7, when using an account different from “Administrator”, to start the serverinstallation or an Upgrade, right click on the ServerSetup.exe file and select the option Run asadministrator. 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 bedeleted before starting a new installation.

In case of server uninstallation failure it could be necessary to remove some registry keys. This can be done usingthe 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 OmniVista4760 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 themin 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.

arning The Migration tool does not allow retrieving the directory replication management from OmniVista


14/40



4760. It has to be managed completely in OmniVista 8770 servers.

In addition, during migration, the replicated sub-suffixes from OmniVista 4760 are created asnormal entries in the OmniVista 8770 company directory. That’s why when the sub-suffix is createdto 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 adepartment 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 createthe corresponding entry in the company directory.

Then import the entries which were exported during step 1.


15/40



7 SPECIFIC MANAGMENT

7.1 SNMP Proxy featureIf 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 PKIapplication.

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 InternetExplore: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 samecompany directory root name. The password entered at the installation time (Directory Manager and otheraccounts) 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.


16/40



7.5 MSAD synchronization and CMISE security

In the case where a secured access for configuration is managed for an OXE PC X, the user” MSAD8770Admin” hasto be added to the authorized users list at PCX side. This is mandatory to allow users creation from the Web clientthat 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.

NoteIn windows 7, if the Java update parameters are not displayed in the Java control panel, you have to do the fol lowing:

Click Start. In the Start Search box, type command.

http://server_name/shared_drivehttp://server_name/shared_drivehttp://server_name/shared_drivehttp://server_name/shared_drive


17/40



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 theTrusted sites list.


18/40



8 NEW FEATURES IN 2.6.07.06.b

There is no new feature in 2.6.07.06.b.

There are two evolutions:

- A new Java version is installed: 1.7.0_80-b15- Topology: multiple links and squared links

9 NEW FEATURES IN 2.6.07.05.a

9.1 New PCX versions supported

OpenTouch™ UP TO 2.1.1

OmniPCX Enterprise up to 11.2

OmniPCX Office up to 10.2

9.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 storedin 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.


19/40



- Management from mass provisioning files

9.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 OmniVista8770 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 thedevices.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 themanagement 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

9.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).

9.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.

9.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.


20/40



9.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/OXEmanagement 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 issearched 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 theautomatic 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.

ote When the Call by Name attribute is not validated at OmniPCX Enterprise side, the corresponding person iscreated 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 systementry (OXE or OT user).

In the OmniVista 8770 2.6.7, the additional automatic criteria addresses only the OXE users, in order to avoidthe 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 OXEand 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.


21/40



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)))

9.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”.

9.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


22/40



9.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

9.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.

9.9 Identification of new types of ALE Deskphones

9.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


23/40



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 queryor 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 –OXEsynchronization and given the device recognition is requested on OXE side, through the parameter System\OtherSystem Param.\System parameters\Force Type Identification option.

9.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.


24/40



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/8029phone 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.

9.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)

9.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.

9.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 OXECPU 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.

9.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.


25/40



ID NAME OFFER DESCRIPTION TYPE

KAT058 NB OF OMS RTU OT.EC 2.0 Number of OMS (software Media Server)

declared by admin

Integer

9.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

Server

Integer

The OpenTouch values can be checked here:

9.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..

ID NAME OFFER DESCRIPTION TYPEKAT056 AA PORT NUMBER OT.EC 2.0 Number of port configured Integer

The OpenTouch values can be checked here (AA ports):


26/40



9.10.5 Call Centers

The new metrics for Call servers are:


KAT040 CALL CENTER AGENT

BASE USER RTU

OT.EC 1.3 CCD Agents: Number of logged CCD agents Integer

KAT041 CALL CENTER CCA

OPTION RTU

OT.EC 1.3 CCA Agents: Number of logged CCA agents Integer

KAT042 CALL CENTER WFM

OPTION RTU

OT.EC 1.3 Use of WMI : 0 if not used, number of CCD

Agent if used

Integer

KAT043 CALL CENTER CRI

OPTION RTU

OT.EC 1.3 Use of CRI : 0 if not used, number of CCD

Agent if used

Integer

KAT044 CALL CENTERSOFTPANEL OPTION

RTU

OT.EC 1.3 Use of Soft Panel: 0 if not used, number ofCCD Agent if used Integer

KAT045 CALL CENTER

SUPERVISOR LIGHT

USER RTU

OT.EC 1.3 CCS Light : Number of connected CCS Integer

KAT046 CALL CENTER

SUPERVISOR MONO

USER RTU

OT.EC 1.3 CCS Mono: Number of connected mono-site

CCS

Integer

KAT047 CALL CENTER

SUPERVISOR MULTI

USER RTU

OT.EC 1.3 CCS Multi: Number of connected multi-sites

CCS

Integer

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.


27/40



9.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 andOpenTouch), 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 layerused 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.


28/40



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.


29/40



10 RESTRICTIONS

10.1 Management from a Web client is not workingThe OV8770 server management launched from an Internet browser is not working in this version.

Only the installed Clients can be used.This restriction will be removed with the next release.

10.2 8082 MyIc Phone on OmniPCX Enterprise and Https requestsHttp 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.

10.3 VOIP quality supervisionThe Performance application based on a Vital module being removed from the product as of 2.5 release. Thereports 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 Reportsapplication.The reports are only available for OmniPCX Office and OmniPCX Enterprise (version superior or equal to 8.0)

10.4 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, theprobability 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


30/40



10.5 Topology

10.5.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.

10.6 USERSUsers 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.

10.7 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.

10.8 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. Otherwisethe 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 webclient.

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”

10.9 OpenTouch alarms display

OT Alarms will not be displayed if two OpenTouch have same “SNMP v3 user name” but different parameters (likeencryption password, passphrase, etc..).To receive the OT alarms from all the declared OT nodes, there are twopossible 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.


31/40



In-case either authentication password or encryption password includes quotes then OV8770 will not receive

alarms from OT.


32/40



11 DEFAULTS FIXED in R2.6.07.06

List of the defaults fixed only in this version for cases found in previous versions.

id headline TSref

crqms00109353 OT Configuration: Memory limit exceeded error message is displayed during device filtersearch

crqms00129521 Parameter regexp must be take in account for no mandatory attribute in models

crqms00155694 topology: time to display a custom view or expand the tree is too long

crqms00160037 8770 R2.5/password in history to translate to french/1-166806131 1-166806131

crqms00161691 8770 Audit Optimization: Increased records load time from webclient and remote client

crqms00164067 [8770] Link attribute defined for the domains works wrong in models

crqms00164067 The user cannot create an OTC Smartphone

crqms00164213 8770 R2.5.4/Migration tool/4760 company directory export ldif file unable to importsome users in 8770/1-172660853

1-172660853

crqms00164393 device:Modification of created device with same device number NOKcrqms00164586 Benchmark: Launch or Close of applications takes more time than usual during alarm

refresh

crqms00166355 8770 R2.6/Apache server randomly no more accessible/1-174192814 1-174192814

crqms00166525 Imcomplete data when Importing 8770Application ldif 1-172766678

crqms00166724 8770 R2.6/strings translation problems/1-174557901 1-174557901

crqms00168036 OV 8770 2.5.0.4.00/ Configuration/Omnivista 8770 inserts Analog phone type as adefault/ 1-172582673

1-172582673

crqms00170582 Radius authentication 1-175397611

crqms00170660 8770 Topology : Topology tree keeps on loading after refresh

crqms00171988 8770 - device application - 2 entries for same binary delivery

crqms00173499 accounting process set to no in PABX still sets are retrieved in Accounting module 1-176132801

crqms00173609 8770 alarms : WBM option is missing in alarms and topology

crqms00173659 8770/users : Exception should be improved for Non configured Key Profiles

crqms00173973 topology: Zoom in-out must be done from the center of the visible part of topology

crqms00174353 8770 alarms : Mutiple filter hidden after resizing the windows frame

crqms00174550 8770 R2.6/topology/links ergonomy problems/1-178504340. 1-178504340

crqms00174908 8770 R2.5.04.00.a/ Directory / Wrong DID construction / 1-177875411 1-177875411

crqms00175157 8770 DM: latest 8770-oxe-tpl and dm model jar files are missing in the package

crqms00175162 8770 2.6.05/configuration/OXE nodes disappears suddenly from the network/1-178508021

1-178508021

crqms00175267 OV8770 // Radius Authent failing if password length = 16 characters 1-172523061

crqms00175565 8770 R2.0.09.01/Topology/Deleted OXE in configuration application still present intopology application/1-178787941

1-178787941

crqms00176701 8770:Proper Error message for 8770 DB restore failed

crqms00176849 2.6.05.01/alarm Generation when an account gets locked 1-174469131

crqms00177147 8770 DM: Node level search for device profile in OT returns just a batch of entry and notcomplete list available in LDAP.

crqms00177439 8770 - alarms - no feedback on task treatment when search items on bug set of alarms


33/40



crqms00177882 A4645: 8770 backup not working when 600 hours of voice mail is filled in

crqms00178058 8770 - config oxe - locate multi selection -> only one entry located

crqms00178210 //8770 Certificate Validity for MSAD plugin is for 1 year only 1-179024141

crqms00178222 topology: after having added a network element, the current cursor turns automaticallyinto a "Select object" cursor type while "create NE" mode is still enabled

crqms00178371 8770 - locate set of instances of prefixes in config OXE tree -> initial set in grid ischanged

crqms00178504 8770 - topologye - space problem in topology view when big set of OT nodes - nameoverlapping

crqms00178551 DM-The behaviour of integer and long attributes are not ok when they are validated withan empty value.

crqms00178612 8770 - device application - unallowed proposal in value for filtering

crqms00178631 8770 - device application - package name for not supported equipement

crqms00178898 8770 Audit : Unable to select nodes at network level in Audit application

crqms00179013 8770 - device application - switch from grid to sheet on one instance-> nothing occursand exception

crqms00179140 OXE Configuration: Local_DID_number object under OXE configuration container is nottranslated and throws exception on selection.

crqms00179256 8770 DM: Grid filter search fails in parameters tab of device management for OT andOXE.

crqms00179267 8770 topology : It is nice to have single scroll bar for alarm Retargetting review

crqms00179453 8770 - device application - about pre defined filter for select Tel package name -homogeneity

crqms00179480 8770 Sync:Synchronization is crashed and exception in RTU counter calculation

crqms00179512 8770 - modify package Tel.application file -> 2 instances

crqms00179632 [SSL vulnerabilities - key length] - 8770

crqms00179717 8770 - config OT - application profile - window bad sized to select device application

crqms00179727 8770 - config Ot - delete Application profile -> display view with structure of object andexception

crqms00179729 8770 - config OT - filter on item on tree - class selection view not at good location

crqms00179737 Issue with OTC PC configuration file name for windows desktop on OXE users

crqms00179917 8770 - config OT - delete user with device 8088 -> exception

crqms00180081 Creation of View is showing "map created" in english in french language.

crqms00180100 877 alarms : Signature contains "-" are not dislayed properly in alarm filters

crqms00180102 2.5.04/Complete Synchronization of OXE not possible//1-177325422/ 1-177325422

crqms00180111 8770 R2.6/Server installation failure/Ldap does not restart/1-179728392 1-179728392

crqms00180166 8770 Audit : Bad node is displayed instead of NMC in filter panel

crqms00180181 8770 Alarams: Event Tabs keep on loading when no events are available

crqms00180261 users: importing a mass pro file with an unknown otUserProfile fails with java exception

crqms00180296 8770 - device application - french langage - no homogeneity in filtering labels labels

crqms00180309 Scheduler: Empty job added in daily job with cn=IJS70

crqms00180313 OV8770: 2.5.04 - LCL threshold crossing detection takes very much time by report to4760

1-180999091

crqms00180358 Configuration: In 8770 configuration application, Search, 8x devices are not displayed inthe drop down.


34/40



crqms00180450 8770 DM: Update package deletes associated binary and application ids in the package

crqms00180535 8770 R2.6.07.04/Directory/In Google chrome the custom themes sreach windows inright side/1-181115102

1-181115102

crqms00180654 8770 - rtu predefined reports - no separtion between ahead data and expected data

crqms00180804 8770 - device application - delete a package with user/device attached -> bad errormessage

crqms00180812 8770/topology : custom view selected elements are not properly displayed

crqms00180813 8770 / Impossible save SBC WAN for smartphones

crqms00180906 8770 R2.6/Directory replication/initialize and schedule operations are not happening/1-181191955

1-181191955

crqms00180931 8770 - device application - application tab- template word not fully translated in french

crqms00180934 8770 - device application - application tab - about first item label of filtering

crqms00180949 8770 - device application - application tab - french - some bad translate for firmware

crqms00181039 8770 R2.6.05.01.f/Administration/Value of automatic inheritance are not translatedcorrectly/1-181153361

1-181153361

crqms00181280 OT Configuration: validate and cancel options are not available during modification ofcombo box attributes (non mandatory)

crqms00181316 OV8770 2.6.7.05: topology - performance problem: displaying of content is too slow. 1-181500809

crqms00181337 8770 - config OT -seracgh 8082 device -> exception

crqms00181389 8770 2.6.05.01.f/Diagnostic tool/Error message while executing the Diagnostic tool/1-181153368

1-181153368

crqms00181448 8770 topology : Navigation should be same in both the standard and custom view oftopology

crqms00181453 DM: Always taking device reference value from tree instead of last updated value.

crqms00181512 8770 R2.6.7/topology/native peer dead unexpectively when zooming in/1-181600411 1-181600411

crqms00181527 8770 DM : On updating OT device profile in grid mode, the corresponding OT node label

is renamed to the profile name that is being updated.crqms00181544 8770 users: In grid mode sip password visible

crqms00181560 2.0.09.02/Directory/filter in the directory-search results to be retained/1-180152973 1-180152973

crqms00181624 Randomly OXE link unavailable on 8770 UUM 1-180473751

crqms00181648 8770 R2.6.07.05/users appli/uncorrect label for 8038 phone/1-181636553 1-181636553

crqms00181672 devices:During grid creation of MIC Android,Blackberry and OTC smartphone tabattributes changes and the mandatory tab is not starred

crqms00181677 Validate and cancel button is disabled during creation of 8002/8012 devices under oxe ifhotel attribute is enabled or disabled

crqms00181679 devices:Unable to select bulk device profile under OXE

crqms00181731 devices:Changes made in the device number is not reflected in the tree

crqms00181810 Reports: Missing translation in the Report Footer of Refport definition designer.

crqms00181833 OT synchronization: audit phase not done in case of irrelevant errors

crqms00181835 8770 R2.6.07.05/topology/icons for server services not displayed in the right window/1-181758000

1-181758000

crqms00181873 8770 remove device failed with error " Could not call Client device Manager"

crqms00181953 8770 - users Application - create user - value of field OT User Profile not visible aftersuccessful creation


35/40



crqms00182072 8770/users: Metaprofile error message key is displayed

crqms00182108 8770 topology : Discard changes function is still working even after the icon is grayedout

crqms00182263 8770 topology : Resizing frame issues

crqms00182273 delete a package -> bad formed error message

crqms00182428 8770 topology : Details mode shows alarms of node with no alarmscrqms00182514 8770 : error not translated in french

crqms00182522 8770 2.6.07.05/topology/loss of customized icons after an upgrade/1-182093821 1-182093821

crqms00182596 name for 8038 could be same rule as other phone like 8068

crqms00182734 8770 topology: random case of switching immediately to custom during opening ofapplication is nok

crqms00182761 Issue with automatic creation of directory entries. 1-181579181

crqms00182861 8770: client folders not deleted after uninstallation

crqms00183204 8770 R2.6.07.05.a -DM 8001 for OXE deployment - Wrong url for auto provisionning 1-182420031

crqms00183226 ALARMS reports: need to define "no filter" and they are some alarms for day 0 that isnot possible

crqms00183340 8770 R2.6.7.1/Configuration/Automatically node is deleted from configuration applicationregularly/1-182415945 1-182415945

crqms00183404 8770 - device application - non homogeneity when selecting tel applications file inpackage creation

crqms00183699 Modification of days not saved in reports preferences 1-182600551

crqms00183704 Performance problems when Oxe user or OT users are created from UUM 1-179984431

crqms00183782 2.6.07.01 /Patches cannot be installed/1-180905743 1-180905743

crqms00183983 8770 R2.6/Audit/the files FTP transfert is sometimes failing/1-182900871 1-182900871

crqms00184022 8770 R2.6.7.1/Web directory/Search key functionality is different of OV4760 andOV8770/1-182545931

1-182545931

crqms00184247 device application: device type- 8001 deskphone issue related to period parameter ofauto provision

1-183064954

crqms00184341 8770 - synchro - loose from a day to next day of device profiles in device application

crqms00184345 8770 - device application - deploy package - no change on OTC smarphone on OXEdevices

crqms00184383 configuration application exports all user options instead of selected 1-182365251

crqms00184417 devices:OTC smartphone devices are not removed in the Deployment package if thetype of Mobile is changed or the device is disassociated

crqms00184448 Over-counting of devices KPIs in contact-center context

crqms00184472 OV8770: Alias is not updated immediatly in Telephonic Device 1-168903941

crqms00184741 8770 R2.5/The cost center value is not displayed in the web directory page for ananonymous connexion/1-183311863

1-183311863

crqms00184820 Filter window is too small in French 1-183401341

crqms00184927 8770 - users application - create a user - indication of bad sip password

crqms00185055 topology:Long Description is not displayed for the link when mousehover on the link incustom topology

crqms00185056 8770 alarms: alarm detail mode : color of the alarm is not updated.

crqms00185058 8770: Enhancement of License Agreement information updated which is displayedduring installation

crqms00185071 Alarm&Topology Enhancements

crqms00185071 curved links and square links in topology application


36/40



crqms00185072 OXE link disappear on 8770 UUM for some OXE users with OT attributes 1-182677571

crqms00185101 8770 : Adminnmc paasword is visible when 8770exportforDAP batch file is executed forexport of OXE

crqms00185121 The 8770 SNMP proxy stopped sending traps 1-183406611

crqms00185279 OT 8770 host backup failed. 1-183273883

crqms00185394 8770 R2.6/alarm reports/design problems/1-183812231 1-183812231crqms00185829 8770 MassPro : Import OTCT users with mass provisionning randomly failed for some

users

crqms00185959 impossible to access to voicemail hotel mode with 8082 / 8088 1-174026830

crqms00186043 devices - unexpected behaviour when the table validated in grid mode.

crqms00186076 2.6.07.01/SNMP service restart needed in 8770 server for sending Traps/1- 1-183053650

crqms00186162 8770 R2.6.07.05/Configuration/Automatically node is deleted from configurationapplication regularly/1-184237747

1-184237747

crqms00186195 OT user profile 1-183259141

crqms00186201 The Backup operation of one OT node (10.0.000.042) failed in maintenance application 1-183405901

crqms00186208 alarms & topology Sprint : Network elements are duplicated in custom topology

crqms00186281 2.6.05.01/SNMP service on 8770 to be restarted manually for sending Traps/1-182571481

1-182571481

crqms00186299 8770:Upgrade failed on duplicate key ini action

crqms00186475 8770 Upgrade:upgrade from 2.0.09.02 to 2.6.07.06 we are getting a popup like tocontinue close the java applications

crqms00186490 8770:Alarm and Topology application is not launching in Upgrade from 1.3.11.00 to2.6.07.06

crqms00186515 8770 2.6.07.04/Topology/Modified image in topology is not take in account after save/1-181224708

1-181224708

crqms00186593 8770 R2.6.07.05/some primary links are not created/1-183061716 1-183061716

crqms00186708 Ldap replication ST_REPL_INITIALIZE. 1-184379958

crqms00186708 ST_REPL_INITIALIZE instead of a user friendly button 1-184379958

crqms00186967 8770 2.6.7.01: After migrating from 4760 to 8770, The SNMP service is not stable. 1-180160951

crqms00187033 8770 Service : NMC Service manager crashes after server upgrade

crqms00187650 8770 Topology : Network nodes were completely deleted from standard topology


37/40



12 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

crqms00180237 "Select all" highlights only OXEs of same version in 4760 but not in 8770 1-180250053

crqms00181577 [8770] Different behaviors for the DNS attribute with minOccurs for a device

crqms00188616 icon is greyed out 1-185420021

crqms00186348 2.6.07.05/ Disable RC4 on 8770/1-181760701 1-181760701

crqms00188211 2.6.07.05/8770 Installation/Cannot install OmniVista 8770 R2.6.07.05.a on

Windows 7 Pro SP1 x64 Russian OS/1-184000121

1-184000121

crqms00188088 8082 backlight is not turned off when phone is checked in 1-181934536

crqms00171230 8770 - alarm - diagnostic bad formed in alarm 4009

crqms00182277 8770 2.6.07.01/UUM/Not Possible to change Users TUI Password to the same

digits once modified locally on the phone/1-180967171

1-180967171

crqms00180818 8770 2.6.07.04/topology/Modified image in topology is not take in account after save/1-181224708

1-181224708

crqms00187005 8770 2.6.07.05/Audit/shell data from the stdby CPU are not loaded into the

DB/1-183333721

1-183333721

crqms00170890 8770 alarms : alarm Service restarting during bulk import of network nodes

crqms00185611 8770 Fails to update many PCS 1-181873533

crqms00187100 8770 filter window is too small when filtering passwords 1-184773931

crqms00182218 8770 OpenAPi - automatically created users not respecting schema 1-181873371

crqms00184189 8770 OpenApi - updating autogenerated user breaks the user 1-181916151crqms00185234 8770 OpenApi - updating std user with applications = ot removes OT user 1-183205134

crqms00188517 8770 OpenAPI: GUI password change does not work 1-185350091

crqms00186991 8770 R2.6.07.05/Audit Auth data randomly failing to load/1-181074791 1-181074791

crqms00185396 8770 R2.6.07.05/OXO synchro fails 1 time over 2/1-183484431 1-183484431

crqms00185766 8770 R2.6/Accounting costs for specific french called numbers is not correct/1-183949081

1-183949081

crqms00188538 8770 slow done when there are ldap activities like synchronization. 1-185097091

crqms00186692 8770 topology : Length of label,short decription and long description should berestricted

crqms00155509 8770 upgrade: "please insert disk 1" 1-169303651

crqms00173279 8770/users : DECT OXE users display are not translated properly in UUM

crqms00164143 About launched application icons in 8770 application

crqms00186541 alarms&topology Sprint: alarm bubble position changes after modifcation of links

crqms00186296 alarms&topology Sprint: Square link between netwrok elements should be restricted

crqms00184995 Audit synchronization crashs the synchro Server 1-183484481

crqms00179489 Audit: sorting a column is done with click-right mouse button instead of click (left)button


38/40


39/40

Om

Documents

Tc2142en-Ed01 Release Note for Omnivista 8770 Release 2.6.7