RELEASE NOTE OMNIVISTA 4760 INSTALLATION R5.2 ... - …

Legal notice:

Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent.

All other trademarks are the property of their respective owners.

The information presented is subject to change without notice.

Alcatel-Lucent assumes no responsibility for inaccuracies contained herein.

Copyright © 2014 Alcatel-Lucent. All rights reserved.

Release Note OmniVista 4760

TC1874 ed.01 Release 5.2

RELEASE NOTE – OMNIVISTA 4760 INSTALLATION

PROCEDURE FOR VERSION R5.2.03.00.C –

RELEASE 5.2

This is a technical release of OmniVista 4760 with the version R5.2.03.00.c

It is available on Alcatel-Lucent Business Portal (https://businessportal.alcatel-lucent.com) .

Technical modes to change the release, corrected defaults, restrictions and problems listed are described in the installation

procedure for version R5.2.03.00.c.

Revision History

Edition 1: November 7, 2013 creation of the document

OmniVista 4760 - Release 5.2

Release Note – OmniVista 4760 Installation procedure for version R5.2.03.00.c – Release 5.2 TC1874 ed.01

Copyright © 2014 Alcatel-Lucent. All rights reserved page 2/59

Table of contents

1 GENERAL ................................................................................................................................................ 6

2 NON STANDARD FEATURES ..................................................................................................................... 7

2.1 Non-operational configuration ............................................................................................................ 7

2.2 Features under PCS (Premium Customer Support) (Complex solutions) ................................................ 7 2.3 Specific process ................................................................................................................................ 7

3 SOFTWARE ............................................................................................................................................. 7

3.1 Binaries ............................................................................................................................................ 7

3.2 Other references ............................................................................................................................... 7

3.3 Patches included. .............................................................................................................................. 7

3.4 License file ....................................................................................................................................... 8

4 PREREQUISITES ..................................................................................................................................... 9

4.1 Server PC prerequisites ..................................................................................................................... 9

4.1.1 Hardware and software ............................................................................................................... 9

4.1.2 Software and hardware compatibility ......................................................................................... 14

4.1.3 Configuring the Server PC ......................................................................................................... 14

4.2 PCX prerequisites ............................................................................................................................ 15

4.2.1 IP, IP/X25, PPP connections to OmniPCX 4400/Enterprise ........................................................... 16

4.2.2 IP, PPP connections to OmniPCX Office ...................................................................................... 17

4.2.3 OMC Release Compatibility with Operating Systems .................................................................... 18

Connection using Kermit protocol to Alcatel Office (4200) .................................................................... 18

4.2.4 OmniPCX 4400/Enterprise software locks ................................................................................... 18

4.3 Prerequisites of administration Client PCs ......................................................................................... 19

4.4 Prerequisites of Client PCs for directory consultation via WEB ............................................................ 19 4.5 Compatibility with SIP Device Management Server ............................................................................ 19

5 DATA COLLECTION OF THE SERVER ...................................................................................................... 20

5.1 List of data to be collected ............................................................................................................... 20 5.2 Company directory .......................................................................................................................... 20

5.3 Carrier configuration ....................................................................................................................... 20

5.4 Security .......................................................................................................................................... 21 5.5 Backup mode .................................................................................................................................. 21

6 INSTALLATION ..................................................................................................................................... 22

6.1 Additional installation of an integrated PC in factory .......................................................................... 22 6.2 Standard server installation procedure.............................................................................................. 22

6.2.1 Mandatory parameters installation ............................................................................................. 24

6.2.2 Restorecontext.ini file ................................................................................................................ 26

6.3 Patches delivered within a version.................................................................................................... 26

6.4 Server post-installation .................................................................................................................... 27




6.5 Client installation procedure ............................................................................................................. 27 6.6 Accessing OmniVista 4760 via a browser .......................................................................................... 28

6.6.1 Installation ............................................................................................................................... 28

6.6.2 Checking the installation ........................................................................................................... 29

7 UPGRADES ........................................................................................................................................... 30

7.1 Prerequisites ................................................................................................................................... 30

7.2 License file update .......................................................................................................................... 30 7.3 Upgrading the OmniVista 4760 server to the version R5.2.03.00.c. .................................................... 31

7.4 Installing a corrective patch ............................................................................................................. 32

7.5 Upgrading the OmniVista 4760 client to the version R5.2.03.00.c. ..................................................... 32

7.5.1 Installing the patch ................................................................................................................... 32

7.5.2 Disabling the automatic upgrades of JRE .................................................................................... 32

8 OmniPCX OFFICE .................................................................................................................................. 33

8.1 Writing rights on dedicated OmniPCX Office directories ..................................................................... 33

8.2 OMC ............................................................................................................................................... 33

9 ALCATEL-LUCENT OFFICE (4200) ........................................................................................................... 34

10 CORRECTIONS .................................................................................................................................... 35

10.1 Corrections in R5.2 ........................................................................................................................ 35

10.1.1 Problems reports fixed in R5.2.03.00.c ..................................................................................... 35

10.1.2 Problems reports fixed in R5.2.02.00.b ..................................................................................... 35

10.1.3 Problems reports fixed in R5.2.01.04.c ..................................................................................... 36

10.1.4 Problems reports fixed in R5.2.01.03.d ..................................................................................... 37

11 RECOMMENDATIONS .......................................................................................................................... 40

11.1 INFRASTRUCTURE / INSTALLATION ............................................................................................... 40

11.1.1 TCP ports to be opened ........................................................................................................... 40

11.1.2 Installation of MOXA driver ...................................................................................................... 40

11.1.3 Use of MOXA equipment .......................................................................................................... 40

11.2 SECURITY ..................................................................................................................................... 40

11.2.1 Password ................................................................................................................................ 40

11.2.2 Rights .................................................................................................................................... 41

11.3 DIRECTORY .................................................................................................................................. 41

11.3.1 Implementing the photos ........................................................................................................ 41

11.3.2 Creating the PCXs ................................................................................................................... 41

11.4 CONFIGURATION .......................................................................................................................... 41 11.4.1 Changing the PCX connection .................................................................................................. 41

11.4.2 Free users name in the PCX ..................................................................................................... 42

11.5 ALARMS........................................................................................................................................ 42 11.5.1 Alarm supervision ................................................................................................................... 42

11.6 TOPOLOGY ................................................................................................................................... 42

11.7 ACCOUNTING ............................................................................................................................... 43

11.7.1 Accounting: Local currency and referenced currency ................................................................. 43




11.7.1.1 Management overview .....................................................................................................................43 11.7.1.2 Installation of country = Default .......................................................................................................43

11.7.2 Cost centers different from those of the PCX ............................................................................ 43

11.7.3 Purging the accounting tickets ................................................................................................. 43

11.7.4 Carrier management ............................................................................................................... 44 11.7.4.1 Tariff: Managing the period ..............................................................................................................44 11.7.4.2 City / Country name: Loss of performance .........................................................................................44

11.8 REPORT GENERATOR .................................................................................................................... 44 11.8.1 Weekly accounting report ........................................................................................................ 44

11.9 SCHEDULER .................................................................................................................................. 45

11.9.1 Tasks succession order ............................................................................................................ 45

11.10 MAINTENANCE ............................................................................................................................ 45

11.10.1 Rule of partitioning ................................................................................................................ 45

11.10.2 Backing up the databases ...................................................................................................... 45

11.10.3 Backing up the OmniVista 4760 database ............................................................................... 45

11.10.4 Defragmentation of the OmniVista 4760 database ................................................................... 46

11.10.5 Backing up / Restoring OmniPCX 4400/Enterprise ................................................................... 46 11.10.5.1 Backup..........................................................................................................................................46 11.10.5.2 Restore .........................................................................................................................................46

12 ADVANCED MANAGEMENT ................................................................................................................... 47

12.1 INFRASTRUCTURE / INSTALLATION ............................................................................................... 47

12.1.1 Reinstalling the server ............................................................................................................. 47

12.1.2 Change the IP address ............................................................................................................ 48 12.1.2.1 Change procedure ...........................................................................................................................48 12.1.2.2 Add a new IP address ......................................................................................................................48

12.1.3 Change the PC name or the Windows® DNS suffix ................................................................... 48

12.1.4 Change the passwords ............................................................................................................ 48

12.1.5 Re-assignation of accounting tickets to active entities ............................................................... 49

12.2 DIRECTORY .................................................................................................................................. 49

12.2.1 Access the OmniVista 4760 directory through Alcatel 4059 ........................................................ 49

12.2.2 Customize the WEB consultation .............................................................................................. 49 12.2.2.1 Available options .............................................................................................................................49

12.2.3 Customizing the directory field names ...................................................................................... 49

12.3 ALARMS - TOPOLOGY .................................................................................................................... 50

12.3.1 E-mail server .......................................................................................................................... 50

12.4 REPORT GENERATOR .................................................................................................................... 50

12.4.1 Schedule a report export ......................................................................................................... 50 12.4.1.1 Restriction .......................................................................................................................................50 12.4.1.2 Procedure .......................................................................................................................................50

12.4.2 Export to PDF format with specific characters to languages ....................................................... 51

12.4.3 Change of paper format for printing the reports ........................................................................ 51

12.5 MAINTENANCE.............................................................................................................................. 52

12.5.1 Backup on a remote host ......................................................................................................... 52 12.5.1.1 Restriction .......................................................................................................................................52 12.5.1.2 Procedure in a domain .....................................................................................................................52




12.5.1.3 Procedure in a Workgroup ................................................................................................................52 12.6 CONFIGURATION .......................................................................................................................... 53

12.6.1 Simple Configuration Profile ..................................................................................................... 53

13 NEW FEATURES (New R5.02.03.00.c features) ...................................................................................... 54

13.1 INFRASTRUCTURE ........................................................................................................................ 54

13.2 Server Update with Change of Operating System ............................................................................ 54

14 RESTRICTIONS AND IDENTIFIED DEFAULTS ........................................................................................ 55

14.1 INFRASTRUCTURE ........................................................................................................................ 55

14.2 CONFIGURATION .......................................................................................................................... 56

14.3 DIRECTORY .................................................................................................................................. 56

14.4 INSTALLATION ............................................................................................................................. 56

14.5 MAINTENANCE.............................................................................................................................. 57

14.6 SIP DM ......................................................................................................................................... 57 14.7 OTHER ......................................................................................................................................... 58




1 GENERAL

This document describes the installation procedure for OmniVista 4760 version R5.2.03.00.c

It refers to the Installation manual and Administrator manual.

These documents are essential since this procedure does not provide full installation details.

To implement the SIP Device Management server, please refer to the Installation manual of this

product.

SIP Device Management Server must have the version 1.2.000.010 or higher to be

compatible with OmniVista 4760 R5.2. The current version is 1.2.000.020.

SIP DMS is not compatible with Windows® 2008 and Windows® 7

It is also highly recommended to consult on "Alcatel-Lucent Business Portal"

(http://www.businessportal.alcatel-lucent.com/) ; software downloading and technical

communications can contain new information regarding OmniVista 4760 Release 5.2.

Refer to appendixes to respect the recommendations of installation and management.

The following Technical Communications are essential for the OmniVista 4760 maintenance:

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

TC0835 Disks and memory management

TC0846 Accounting: Investigation elements

TC0858 Traffic observation: Investigation elements

TC0953 OmniVista 4760 license on OmniPCX Office: Max users reached, client in deprecated mode

TC1007-Ed02 OmniVista 4760 Installation / Uninstallation

CAUTION

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:[email protected] ).

http://www.businessportal.alcatel-lucent.com/

mailto:[email protected]




2 NON STANDARD FEATURES

2.1 Non-operational configuration

4760 client with Citrix for OmniPCX Office management.

2.2 Features under PCS (Premium Customer Support) (Complex solutions)

Capacities higher than 30000 subscribers or 800 nodes (OmniVista 4760 PCS).

2.3 Specific process Proxy SNMP / Spectrum, HPOV integration .

Creation of limited user accounts to the management of some PCXs (ACI/ACL LDAP).

These features are commercialized and supported by Alcatel-Lucent Professional Services.

3 SOFTWARE

3.1 Binaries There is no package delivered.

Only the binaries to install the version R5.2.03.00.c. will be available on the BPWS.

3.2 Other references Documentation CD: 3BH 11630 AKAB which contains :

Administrator manual : 3BH 19260 ed. 16

OmniVista 4760 Installation manual : 3BH 19261 ed. 15

SIP Device Management Installation manual : 8AL 90701 ed. 01

Security Guide : 8AL 90700 ed. 01

SIP Device Management software DVD: 3BH 11761 AAAD which contains:

Version Release R1.2.000.020

SIP Device Management Installation manual : 8AL 90701 ed. 01

3.3 Patches included.

Under \Patches\Mandatory folder:

Files Crms fixed CR headline

PatchA_aliz.ace Crms00457055 OXO Support R9.1

PatchB_LDIF.ace Crms00457000 OXE Support K1

PatchC_jar.ace Crms00463666 Configuration locked




3.4 License file

For more details, refer to the technical communication TCV039-Ed07 OmniVista 4760 licenses.

To install OmniVista 4760 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 4760 server.

CAUTION

If the declaration node is OmniPCX 4400 R5.0 Ux, you can no more get the OmniVista

4760 license file.

If the declaration node is OmniPCX Office, OmniPCX Enterprise R5.0 Lx, the license file is

produced on BPWS/ELP.

Correspondence between license version and OmniVista release:

License 5 6 7 8 9 10 11 12 13

4760 R3.0 R3.1 R3.2 R4.0 R4.1 R4.2.x R5.0 R5.1.x R5.2

End of corrections 10/05 04/06 10/06 04/07 01/08 05/09 01/10 06/11 11/13

End of support 10/06 04/07 10/07 04/08 01/09 05/10 01/11 06/12 11/14

OmniVista 4760 R5.2 accepts licenses versions 12 and 13.

Versions of embedded software:

InstallShield® JRE SunTM

Directory

Service Enterprise

Edition

Sybase Apache PHP

2008 1.6.0.21 DSEE 7.0 SQL Anywhere 10

10.0.1.4157

2.2.16.0 5.2.14.14




4 PREREQUISITES

This section describes the prerequisites required to install OmniVista 4760 server and client

applications.

4.1 Server PC prerequisites

4.1.1 Hardware and software

Minimum hardware requirement:

Notes

Minimum implies a targeted use of the application. The use of the client PC on the server PC must be

minimum, that is to say with a single module opened.

There is no mass processing (more than 100 entries managed in the grid). Otherwise, the requirements

must be modified to take account of the needs associated with the client application.

In all cases, the performance of the OmniVista 4760 Client part is better if the client application is

started from a remote PC.

Capacities greater than 30000 users and 400 PCX require Alcatel agreement to check your system

configuration and to help you to generate the license file.




Windows® 7 and 2008 are not supported for PPP connectivity and SIP Manager.

For OmniPCX Office, Windows® Vista and Windows® 7 are supported from OXO R7.0, and

Windows® 2008 from OXO R8.x and OXO R9.x.

2 Ghz CPU and 4 GB RAM are strongly recommended for Windows® 2008 R2 server.

Virtual solution validated on VMware ESX®.VMware release supported from 3.5 (VMware itself is not

supported by Alcatel-Lucent),no PPP connection (only IP), SIP manager not supported, maximum 30000

users, Directory replication not supported.

Data Centre and other specific Windows® editions (Enterprise Edition) are not validated. Regarding

Small business edition this Windows® edition is packaged as a Windows® Domain Controller: it

includes Active directory server, an LDAP server which prevent OmniVista 4760 default installation.

For any request regarding such validation, you can contact the Alcatel Professional Services.

Processors types are given as examples. The frequency clock is a minimum requirement.

Maximum size of database supported by 4760 is 10 GB or 30 Million of Tickets

For OmniVista 4760 R5.2 Alcatel-Lucent has selected:

- HP PC Compaq pro 6000 from HP

- DL 380 G7 server from HP










Test environment:




4.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 4760 server.

4.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 SunTM

DSEE Server. When installing the server, it is

better to keep the defaults directories and to change only the physical drives.

RAM.

Check that the virtual memory is correctly set; the size of the maximum virtual memory must be

twice the physical RAM. Moreover the disk using the exchange file must have enough free space.

Refer to the technical communication TC0835 Managing the disk and RAM in Release 4.1.

Another JAVA application can use the Classpath environment variable. In that case, the line of

parameters can exceed the limit size and prevent the installation of the server.




The Path environment variable giving the access path to Windows® and to its dll, which will

receive the access path to OmniVista 4760 binary and to Sybase must be valid.

The Path is managed through the System icon of Windows® Control Panel.

Before installation, you should have only Path = C:\Windows®\system32; C:\Windows®.

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 %systemroot% ; %systemroot%\system32. According to

your configuration, it is:

C:\winnt ; C:\winnt\system32 or

C:\Windows® ; C:\Windows®\system32

The name of the computer must not have the following characters ., -, + (dot, dash, plus). 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.

For the first OmniVista 4760 server installation on a new PC, this one has to be connected to the

IP network. Otherwise the installation would fail during the SunTM

DSEE server installation. The

message in the log file is:

com.iplanet.install.svrutil.wbSvrutil::getHostName: can't determine

host name: java.net.UnknownHostException:

4.2 PCX prerequisites

The compatible OmniPCX 4400 releases depend on the type of PCX Server connection.

The problems related to phase out PCX releases are not fixed (example: the hang-up via STAP is not

available in OmniPCX 4400 Release 3.0).




4.2.1 IP, IP/X25, PPP connections to OmniPCX 4400/Enterprise

Release

4760

Release

PCX

Software version equal to

or higher than

IP or IP/X25

connection PPP connection

1.5 3.0 C1.532.5.w (except STAP) Yes No

1.5 3.2M C1.712.5.c, C1.714.3.a Yes Yes

1.5 3.2 C2 C1.762.21 Yes Yes

1.5 4.1 D1.305.4.f Yes Yes

1.5 4.1.1 D1.311.7.d Yes Yes

1.5 4.2.1 D2.304.4.s Yes Yes

2.0 5.0 Ux D2.313.7.f Yes Yes

2.0 5.0.1 Ux D2.314.7.p Yes Yes

2.0 5.0 Lx E1.604.9.t Yes No

2.1 5.1 E2.404.u Yes No

2.1 5.1.1 E2.502.2.p Yes No

2.1 5.1.2 E2.504.1.ai Yes Yes

3.0 6.0 F1.602.3.i Yes No

3.0 6.0.1 F1.603.1.l Yes Yes

3.1 6.1 F2.500.6.g Yes No

3.1 6.1.1 F2.502.12 Yes Yes

3.2 6.2 F3.301.36 Yes Yes

4.0 7.0 F4.401.13 Yes Yes

4.1 7.1 F5.401.25.b Yes Yes

4.2 8.0 G1.302.5 Yes Yes

4.2 8.0.1 G1.503.23.b Yes Yes

5.0 9.0 H1.301.31.b Yes Yes (1)

5.1 9.0 H1.301.31.b Yes Yes (1)

5.1.1 9.1 I1.605.6.a Yes Yes

R5.2 R9.1 I1.605.22 Yes Yes (2)

R5.2 R10.0 J1.410.39.a Yes Yes (2)

R5.2.02 R10.1 J2.402.12.a Yes Yes (2)

R5.2.03 R11.0 K1.400.19.a Yes Yes (2)

Notes

(1) In R9.0, for using the PPP connection, the version must be H1.301.31.b or higher (crms00169291).

(2) Only with Windows® 2003.

CAUTION

OmniPCX Enterprise whose hostname length greater than 16 characters must be in version

F3.301.36, F2.502.9 (or greater) so that LDAP/PCX synchronization runs properly

(XTSce69070).

PCX Releases are regularly updated. The new values also concerns previous OmniVista

releases.




4.2.2 IP, PPP connections to OmniPCX Office

Releases Software version equal to or higher

than IP connection

PPP connection

(1)

1.0 Not supported No No

1.1 1.0.19.06 (2) Yes Yes

2.0 2.0.32.013 Yes Yes

2.1 210.083.001 Yes Yes

3.0 300/19.1 Yes Yes

3.1 310/038.001 Yes Yes

4.0 400/022.001 (1) Yes Yes

4.1 410/015.005 (1) Yes Yes

5.0 500/030.004 (1) Yes Yes

5.1 510/017 (1) Yes Yes

6.0 600/014.001 Yes Yes

7.0 700/012.001 Yes Yes

7.1 710/022.001 Yes Yes

8.0 800/24.1.a Yes Yes (3)

8.1 810/045.003 Yes Yes (3)

8.2 820/026.005 Yes Yes (3)

9.0 900/054.001 Yes Yes (3)

9.1 910/043.001 Yes Yes (3)

(1)

Windows® 2003 server is mandatory to receive urgent alarms on the fly.

No S0 modems with OminPCX Office 1.x.

1 B channel-ISDN connectivity with OmniPCX Office 400/15.3 and Multitech

ISDN modem.

(2) The check of attached node requires an OmniPCX Office versions 2.0. For

more information, refer to the technical communication TCV039 OmniVista

4760 licenses.

(3) Only with Windows® 2003




4.2.3 OMC Release Compatibility with Operating Systems

OMC Releases

min

Windows® XP

SP2

Windows® 2003

SP1/2 Windows® 7 Windows® 2008

600/14.1.d Yes Yes No No

700/8.1.c Yes Yes Yes No

800/24.1.a Yes Yes Yes Yes





Connection using Kermit protocol to Alcatel Office (4200)

Releases

R4

OmniVista 4760 R4.2 is the last release compatible with Alcatel-Lucent Office

(4200).

OmniVista 4760 R5.2 is no more compatible with Alcatel-Lucent Office (4200).

4.2.4 OmniPCX 4400/Enterprise 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 4760 modules Number of OmniPCX 4400/Enterprise software locks

Configuration 13 – ECS Engine

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 49 - Directory

Traffic observation 42 - Accounting users (do not forget)

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 4760

OmniVista 4760 error messages typical to software lock problem PBX side:

Alarm: Consult the NMCFaultmanager_A4400Service_x.log file

The EFD was not found -> Trying to create it




A CMISE error [2] occurred

Configuration: The "Cmise reject: broken association" message is displayed in the lower part

of the configuration application window.

Accounting: Consult the NMCSyncLdap_x.log file at level of accounting ticket retrieval

(polling_accounting).

4.3 Prerequisites of administration Client PCs

HARDWARE AND SOFTWARE (Minimum)

4.4 Prerequisites of Client PCs for directory consultation via WEB

HARDWARE AND SOFTWARE (Minimum)

Operating System Windows® XP (Service Pack 2or 3)

Windows® 2003 SP1 or 2

Windows® Vista,Windows 7

Internet browser Mozilla Firefox 11 or 12

Internet Explorer version 6 or 7 or 8

4.5 Compatibility with SIP Device Management Server

SIP Device Management Server must have the version 1.2.000.010 or higher to be compatible with

OmniVista 4760 R5.2. The current version is 1.2.000.020.

SIP DM is not compatible with Windows® 2008 and Windows® 7.




5 DATA COLLECTION OF THE SERVER

5.1 List of data to be collected

The table below supplies the information to be collected before installing the server and clients:

Windows® data Installation data Management data

IP Address

Host name

DNS domain name

License file

Passwords

Directory root

Connection to PCXs

Directory

Carrier configuration

Type of accounting (global /

detailed)

Access security

Backup mode

Windows® data.

They are used to integrate the server PC in client computer network.

Installation data.

They are essential to undertake the server installation.

Management data.

They are used to define with the client the information to be completed after installation.

5.2 Company directory

The company directory management is described in the technical communication TCV060 Directory

Management.

5.3 Carrier configuration

The Code book import function is used to automatically import all accounting carrier parameters in a

database from previously created text files.

Refer to Administrator Manual Section 4 – Accounting/Traffic/VoIP, to create these text files in required

formats.

An A4715/A4740 -> A4760 carrier migration tool can be used to retrieve the carrier data of the

same tariff area. This tool operates only from version 4_4.14x of Alcatel 4715/A4740. Its functioning

is described in the technical communication TCV002 Alcatel 4715/4740 carrier data migration to

OmniVista 4760.

An A4755 -> A4760 carrier migration tool can be used to retrieve the carrier data of the same tariff

area. Its functioning is described in the technical communication TCV017 Carrier data migration from

Alcatel 4755 to OmniVista 4760.




CAUTION

Each Code book import must be followed by a cost recalculation. It can be scheduled or run

manually. The recalculation process can take several hours depending on the number of tickets.

There are ten Code book files. Generally, they are located in a directory which has the carrier

name:

Information file : .inf,

Area file : .rgn,

City / Country file : .ccn,

Direction file : .dir,

Tariff file : .trf,

Calendar file : .cal,

Installation file : .itl,

Adjustment file : .adj.

ISDN services file : .fct

Trunk groups file : .trg (starting from R4.2)

The .inf ; .itl ; .dir ; .ccn files must be changed depending on the site.

The .cal file must be completed with local holiday days.

In the .itl file, the node names must be exactly the same as declared in the system directory;

ensure the correct case.

Note

The import never deletes an object. It can only create or update the objects information in the files. The

needed deletion is carried out manually or with the ‘Clean Carrier Configuration’ application in the

scheduler. These cleans are needed to keep the OmniVista 4760 performances.

5.4 Security

The Security Guide provides all useful information to integrate OmniVista 4760 into a secured

company network.

Establish with the client, the access security to manage inside the application:

access security to OmniVista 4760 modules,

access security when configuring the various PCXs.

5.5 Backup mode

Establish with the client:

the backup period,

the backup location on the disk or on the network.




6 INSTALLATION

6.1 Additional installation of an integrated PC in factory

Only Operating System and JRE are factory installed on the PC delivered by Alcatel. Disabling the On-

access scan mechanism can provide a real installation time gain.

6.2 Standard server installation procedure

The complete procedure is described in the Installation Manual.

Before beginning the installation, prepare the Server PC accordingly to section 2 Server

requirements.

The installation fails if the operating system is not running in SP1 at least.

Refer to technical communication TC1007-Ed02 OmniVista 4760 Installation /

Uninstallation chapter 6.14.

On W2003, hot fix KB956572 must be removed (freeze TOMCAT installation) and

must be replaced by the KB971812.

It is recommended to stop all Antivirus programs. Especially the Etrust software (Computer

Associates) prevents the installation of JRE.

If the PC has Dell Open Management services, close these services and copy the JTC1012.dll

file from 4760\bin directory to c:\Program Files\Dell\openmanage\oldiags\bin directory before

confirming the reboot of the PC when the installation is completed.

If the application has been installed previously and you must restart with an empty database, refer

to Appendix 3.

Main installation steps are given below (for more details refer to Installation Manual):

Preliminaries

Create debug.lock file to prevent rollback. Under Temp directory:

Default: Document Settings/Administrator/Local Settings/Temp/ (W2003

or XP)

Users/Administrator/Appdata/Local/Temp (W2008 or Win7)

This folder is hidden by default in Windows® Explorer:

select from Tools/Folder options/View: Show hidden files and folder

Unset hide protected operating system files.

To set trace mode installation, after copying 4760 software on hard disk, modify

ServerSetup.ini:

replace 1=/v REINSTALL=ALL REINSTALLMODE=vamus ALLUSERS=2 /Lie

by 1=/vREINSTALL=ALL REINSTALLMODE=vamus ALLUSERS=2 /L*v




On 4760 Server:

Installation log file on server is in:

Document Settings\Administrator\Local Settings\Temp\

Omnivista4760_install.log for Server ( XP or Win2003)

Document Settings\Administrator\Local Settings\Temp\

Omnivista4760Client_install.log for Client ( XP or Win2003)

Users\Administrator\Appdata\Local\Temp (W2008 or Win7)

Client log connections are:

4760\Client\bin\4760Client.log on server

Client4760\bin\4760Client.log on client

To get an extended uninstallation log, launch:

msiexec /uninstall {C3CF0589-B127-4C15-A347-E0DCCBC74E87} /L*v

“%TEMP%\OmniVista4760_uninstall.log”.

By default, on a DVD, data (directories and files) of the version must be located under the

root.

For copying more versions on a same DVD, you should modify the

\Setup\fix_media_source.vbs file to ispecify the actual path:

Example:

“MediaPackage”, “\4760_R5.2.03.00.c\Setup\”.

Then the version must be burnt under the 4760_R5.2.03.00.c directory.

Any error management at this level generates the “Insert Disk 1” message when

installing or updating.

Installation

To install or upgrade a remote server using a Terminal Server or Remote

Desktop connection, it is mandatory to start the session as “console “

(command mstsc.exe /console (Windows® 2003, Windows® XP SP2) or

mstsc.exe /admin (Windows® XP SP3, Windows® Vista, Windows® 7 and

Windows® 2008).

Otherwise the operation will fail.

In the installation fails, contact the Technical Support by providing the OmniVista

4760_install.log.

If an installation fails, refer to the technical communication TC1007 OmniVista 4760

Installation / Uninstallation for a possible “manual” uninstallation.




6.2.1 Mandatory parameters installation

Parameter Type Name values valid if

Company name String Always valid. Special characters are

escaped

Destination directory Directory Directory exists, is empty and is not a root

directory such as C:\

SunTM

DSEE destination

directory

Directory Directory exists, is empty and is not a root


Sybase ASA server

destination directory



Database data destination

directory



Server archives destination

directory



Hostname and domain (or

dns suffix)

FQDN DNS domain exists

Hostname less or equal to 15 characters

Mail server name or IP

address

Name or IP address Name can be resolved

Localization country Country name

See Table: OmniVista 4760 supported

countries

Localization language Language name See Table: OmniVista 4760 supported

countries

Application administrator

logon

Default: AdminNmc ASCII characters

Characters not in: ,+”\<>;#&%|^

Database administrator

logon

Fixed: DBA Characters in ASCII letters and digits and

_$#

Password ASCII characters

Length is at least 8

LDAP constraint: characters not in:

,+”\<>;#&%|^ and <space>

ASA constraint: characters not in

!”%&’()*+,-./:;<=>?\^`{|}~ and

<space>

LDAP port Default: 389 In [1-1024] and [5000-65535]

HTTP port Default: 80 In [1-1024] and [5000-65535]

LDAPS port Default: 636 In [1-1024] and [5000-65535]

TOMCATport Default: 8090 In [1-1024] and [5000-65535]

1 Start the PC and connect as local administrator of PC.

2 Launch ServerSetup.exe .

Under WINDOWS®7, right clic on ServerSetup.exe then choice “Run as administrator”




After starting ServerSetup.exe, the system checks if software is already installed by

searching this registry entry:

HKEY_CLASSES_ROOT\Installer\Products\9850FC3C721B51C43A740ECDBC7CE478

If the hostname has more than 15 characters, the LDAP installation will fail. The limitation to

15 characters is written in the registry.

The registry key is found in the place:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog.

During installation, the setup files are extracted and copied in the %Temp% folder. If the space

in the %Temp% folder is less than required, then it will not copy all the files in the %Temp%

folder. So to make sure that there is enough space in %Temp% folder a check has been done

during installation. The setup will not continue to install if the temp size is less than 100 MB.

The threshold value is maintained at 100 MB to make sure that it has enough space to keep

the extracted files from the setup during installation. The estimation is calculated from the

space occupied by the installation files in the %Temp% folder. This space checking is only

applicable for Server.

3 If the correct Java Runtime Environment (JRE) (1.6.0_21) is not detected, its installation will

start automatically.

4 Indicate the location of the xxyyyzza.sw4760 license file, supplied on diskette or in a

directory in the PC. The setup will check coherency of the supplied file.

5 Specify:

the Company Name which will be used as directory root,

the installation directory of OmniVista 4760 (this access path must not have space as

“Program Files”), of Sun ONE Directory server, of Sybase software and database SQL.

Sybase software should never be installed in the same directory as OmniVista

4760; the upgrade towards a higher version will fail.

6 Specify the backup directory then click on Next.

7 Specify:

The numbers of the LDAP, LDAPS , HTTP and TOMCAT ports are standardized. Do not

change them unless you need to.

8 Enter the unique password which will be set for the 4 accounts:

Directory manager

Admin

Adminnmc

dba

Unauthorized characters are listed in the table above.

9 Enter:

the “IP name / address of the e-mail server” if used,




choose the Country that gives the Language, the paper size and the

currency (parameters used for the accounting),

The Cost Centers management method.

10 For a standard installation, do not pre-configure the system.

Click on Install to launch the installation.

Click View log file to displays the log file of installation (Omnivista4760_report.log).

The log file is useful in case of installation error. This file displays the performed

installations steps (log localization: %Temp% for Vista).

11 The patches available under 4760/Install/Patches are installed.

The View log for Patches button opens the patch log window. The patch log window

displays information about patch installation (log localization: installation

repertory\4760\install\patch installer.log).

12 At the end of installation, confirm to reboot the PC.

6.2.2 Restorecontext.ini file

This file is created/updated with software operations (installation/upgrade).

Option name Description

DATE Installation date, format MM-DD-YY

NmcVersion Version that has been installed

SvDomain DNS domain

svNMCDirInst Install directory

SvNMCName Host name (without domain)

svPortApache Httpd server port

svPortLDAPS Secured LDAP port

svPortTomcat TOMCAT port

svServerPort LDAP server port

svSuffix Company name

szAsaDir Sybase ASA installation directory

szDataBase Database files directory (*.db)

szNetscape SunTM

DSEE installation directory

TIME Installation time, format HH:MM:SS

nmcInitialVersion Current version at install time (never changed) (created with installation)

nmcPreviousVersion Version that has been upgraded (created when upgrading)

6.3 Patches delivered within a version

The patches delivered with a version will be automatically installed at the end of the installation

procedure of the product.

Patches are in .ace format.

This type of patch can carry out the following processes:

Control (stop / start) one or several Windows® services.




Execute a SQL script.

Import a LDIFF file.

Extract an archive (4760 helps for example).

Copy files.

Launch an application.

Replace a string in a file.

The patches installation generates a log under \4760\install\patch_installer.log.

The installed patches list is under \4760\install\patch_history.ini.

6.4 Server post-installation

Post-installation is described in the Installation manual. Carry out in more the operations described

below.

When the installation and the configuration are finished, we recommend performing a server

data backup on a networked disk or on a CDROM.

Manage the sharing of archive directory of tickets to allow the restoration of these tickets.

Example: Name of sharing: 4760_ARC, Reading right for “Everyone”.

In order to retain the correct version of JRE, you should disable the automatic check of

upgrades.

In the Control Panel, use the standard display (the default display of Windows® XP masks some

icons):

Click on java,

In the Update tab, disable Check for update automatically.

6.5 Client installation procedure

Install the client in a new c:\4760client or c:\Program Files\4760client

directory. Do not use an existing directory (c:\Program Files).


Check that the Client PC and the Server PC can reach together on the network.

Client PC end, run:

ping <Server_Name>.

ping <Server_Name>.<Server_DNS_Suffix_Name>

Server PC end, run:

ping <Client_Name>

ping <Client_Name>.<Client_DNS_Suffix_Name>

If it is not the case, ask the network manager to correct the DNS management or to complete host

file (under winnt or Windows®\system32\drivers\etc\) of Client PC and Server PC with:

IP_Address Host_Name Host_Name.DNS_Suffix_Name




Example: 155.166.123.156 OmniVista OmniVista.alcatel.fr

Method 1

1 Launch ClientSetup.exe.

2 If the correct Java Runtime Environment (JRE) (1.6.0.21) is not detected, its installation will start

automatically.

3 Accept “Alcatel License agreement”.

4 Enter the installation path.

5 Click on Install to start the installation

6 In order to retain the correct version of JRE, you should disable the automatic check of

upgrades.


icons):

Click on java,


With a 4760 client installed under Vista, a warning message is displayed. Select the Don’t show

this message again option.

Method 2

When the server is already installed you can download the client installation file using this url:

http:/server_name/cgi-bin/OmniVista4760Client.exe (replace server_name by your OmniVista 4760

server name).

For more information, refer to the Installation Manual.

6.6 Accessing OmniVista 4760 via a browser

6.6.1 Installation

Contact the client network manager to authenticate the OmniVista 4760 server with its name and

its IP address in intranet sites.

If a request of proxy authorization occurs during this procedure, you will probably not be able to

access the application since the network manager does not allow this type of connection.


1 Use your WEB browser to access the OmniVista 4760 home page.

Run the browser.

Enter the Domain.Name_Server of your server in the address

2 In the browser security properties, accept the cookies:

Under Internet Explorer 7.0 or 8.0:

http://nom_serveur/cgi-bin/OmniVista4760Client.exe




Menu Tool/Internet Options/Privacy tab,

Manage the different options you will find after clicking on Site and Advanced buttons.

Under Internet Explorer 6.0:

Menu Tool/Internet Options/Privacy tab,

Select a different level of Block All Cookies or manage with the Modifier button

the authorization for the 4760 server.

Under Mozilla Firefox 11.0 or 12.0:

Menu Tools/Options/Privacy ,

Use custom settings for history, then Accept cookies from sites.

3 Following management will prevent from a language switch after search in the directory. In this

case the No such object error message is also displayed.

The management described concerns Internet Explorer 6.0. An equivalent management has to be

done for other browsers.

menu Tool/Internet Options/Privacy tab

click on Advanced button

select Override automatic cookie handling, accept option for First-Party

Cookies and Third-party Cookies and validate Always allow session

cookies

4 Before accessing the JAVA page of the network management, install the JAVA Plug-in:

If the correct JRE version (1.6.0.21) is already installed on the station, go to the point 5.

On the home page, click on the before using the Alcatel-Lucent OmniVista

4760 NMS for the first time or from a new server, please install JRE.

Then click here to start the installation procedure of JRE.

Select the standard installation procedure.

Reboot the PC after installation.

5 Before logging on to Network management, initialize the JAVA Plug-in:

On the home page, click on the To open Java application writing rights link.

Then click here.

6.6.2 Checking the installation

If the Java plug-in installation and the initialization with an OmniVista 4760 server occurred correctly,

check in the Documents and Settings/Your connection login directory, that the .java.policy file

contains the address returned by the server in text mode.

Example: Server named OmniVista installed in the alcatel.fr domain.

Grant codeBase « http :// OmniVista.alcatel.fr /-« {

permission java.security.AllPermission ;

} ;

grant codeBase « http :// OmniVista /-« {




permission java.security.AllPermission ;

If from the PC, you cannot ping to OmniVista.alcatel.fr, there is a name or domain problem.

Check the hosts file or the addresses of the DNS server.

If the hosts file is used (without DNS), it must contains a line like below:

ip_address server_name server_name.domain

Example

155.166.123.156 OmniVista OmniVista.alcatel

7 UPGRADES

Perform OmniVista 4760 Server data backup then a defragmentation before starting upgrade.

7.1 Prerequisites

Close all Windows® opened before starting server upgrade but do not stop

NMC Services.

The installation fails if the operating system is not running in SP1 at least.

On W2003,hotfix KB956572 must be removed and replaced by KB971812.

Stop if necessary the SIP DM Server services.

Temp4760 folder

This folder will be created under the %Temp% folder. During the upgrade it makes a backup of the

data and then uninstalls and reinstalls and finally makes an import of the data backup. So during the

backup operation the Temp4760 folder is used to keep the backup files. It stores the files in ace

format. Currently ten ACE files are stored. The Temp4760 folder is created depending upon the path

given during installation of LDAP, Sybase or 4760.

If the path drive letter for the LDAP is E: then Temp4760 will be created in the path

E:\Temp\Temp4760\.

During the LDAP database backup the Save_Ldapbasesfiles.ace file will be stored in the path

E:\Temp\Temp4760\. If the Sybase is installed in path drive D: then the

Save_ASAdatabasefiles.ace file will be available in the path D:\Temp\Temp4760.

7.2 License file update

1 Close the NMC service manager with the OmniVista 4760 service manager.

2 As soon as the dependent services have all been closed, copy the field of type

xxyyyzza.sw4760 supplied by Actis, renaming it nmc.license after renaming old




nmc.license file (and not nmc.license.txt). Check this name by right clicking

\Properties. Then move this file in the 4760\etc installation directory.

3 Restart NMCService Manager.

4 Check that the licenses have been updated: Help\About menu.

7.3 Upgrading the OmniVista 4760 server to the version R5.2.03.00.c.

The minimum versions susceptible of being upgraded to R5.2 are:

Releases Versions

R5.0 5.0.07.02.b/5.0.07.03.c/5.0.07.05.b

R5.1 5.1.04.00.b

R5.1.1 5.1.06.03.c

R5.2 5.2.01.03.d/5.2.01.04/5.2.02.00.b

These versions are available on the BPWS.

Versions lower than R5.0 cannot be upgraded in R5.2. Actis will propose a license update of the

nmc.license file but this does not allow an upgrade of the server. You need to reinstall a new

application R5.2 or perform an upgrade with an intermediate allowed version.

Procedure for versions before R5.0

Backup parameters (PCX in System Directory, Logins,Company Directory, Carriers definitions,

accounting tickets).

Reinstall if necessary a new operating system compatible with OmniVista 4760 R5.2.

Install OmniVista 4760 R5.2, then configure OmniVista 4760.

Procedure for versions starting from R5.0

Before the upgrade:

IMPORTANT

Get the directory manager and dba passwords. You should have a license compatible with the

Release R5.2 (version 12 or 13).

Perform a data base defragmentation and a Backup.

The customizing carried out on the various "themes" offered for Web Client will be saved during

the upgrade in the 4760\(web)client\themes directory.

The customizing carried out on the welcome page of Web Client is not saved. If necessary, you

should save the modified data of the 4760\webclient (R4.0) or 4760\client (other releases)

directory.

The customizing of the topology is saved during the upgrade. For security, it is possible to first

export the data from the system directory:

Nmc\nmcConfiguration\globalPreferences\topology

The Java RunTime Environment (JRE) will be installed if its version is not correct:




1 It is advisable to stop any On-access scan mechanism. Disabling the On-access scan

mechanism can provide a real installation time gain.

2 Check all OmniVista 4760 services have been started.

3 Launch the server update with the Serversetup.exe command.

4 Specify the location of license file when the system requests it.

5 Once the upgrade is completed, carry out all the checking jobs of the installation.

6 After any upgrade operation, it is recommended to save 4760 databases using 4760

Maintenance application.

7.4 Installing a corrective patch

The corrective patches are installed automatically at the end of 4760 server update if they are

available in the installation CD-ROM.

To manually install a patch copy the correspondent .ace file in the 4760\Install\Patches folder

and launch the 4760\install\Patchinstaller.exe command.

You can consult the patch installation log in \4760\install\patch_installer.log.

The installed patch list is in \4760\install\patch_history.ini.

7.5 Upgrading the OmniVista 4760 client to the version R5.2.03.00.c.

When a client PC running an earlier version connects to a server in 5.2.93.00.c, the system proposes

an update from this server. This update is running correctly only from a client version equal or greater

than R3.2.05.00.b. For client version less than R3.2.05.00.b, do not accept the update procedure

otherwise client could not open anymore. Under such circumstance, it is necessary to uninstall the

client and to reinstall it.

If the client is in version lower than R5.1, it is kept. An additional new client in R5.1 is installed in a

directory named Client4760 5.1.

This allows the cohabitation of several versions on a same PC.

A client can also be installed by launching the ClientSetup.exe file.

The rules of cohabitation above will also apply.

7.5.1 Installing the patch

There are no more patches specific "clients".

When connecting a client to server, the version of the nmc50.jar file is checked.

If the client version is below, an upgrade is available when connecting to the server. The upgrade is

carried out automatically.

7.5.2 Disabling the automatic upgrades of JRE

In order to retain the correct version of JRE, you should disable the automatic check of upgrades.





icons):

Double click on java,


8 OmniPCX OFFICE

Refer to the Technical Communication TCV049 Installation procedure for Release 2.1/3.x for

OmniPCX Office (IP, PPP, Accounting, Alarms, Troubleshooting).

8.1 Writing rights on dedicated OmniPCX Office directories

The management described below has to be applied, not only for the save/restore/download

operations, but also to enter into PCX configuration.

The OmniPCX Office data are saved by default on the 4760 server PC in the directory

4760_ARC/OXO/data. This directory is shared as 4760-databases during 4760 installation (or

4760-PM5 in case of upgrade operation), with read access to everyone.

CAUTION

If the 4760_ARC\OXO\data directory already exists before 4760 server installation (for instance after

uninstalling a previous 4760 server) and has a shared name, this name will not be modified by 4760

R4.1 installation. To use OmniPCX Configuration application from 4760 server, Windows® directory

shared name must be the same as the name defined in OmniVista 4760 System directory (this name

can be configured in /NmcConfiguration GlobalPreferences / Config / OXOAccess).

The PC administrator has to allow the writing right on the sharing to a local user. Remove "Everyone"

from the list of users. In the sharing management, for the user limit, "Maximum allowed" has to be

validated. A reboot of the PC can be needed to take into account the management.

This local user has to be declared in the 4760 server:

System Directory / NmcConfiguration / GlobalPreferences/Config/OXOAccess

The URGALARM user can be used if it’s already created or all other local user with permanent

password.

The software versions to be downloaded to the PCX have to be stored in the directory

4760_ARC/OXO/sw. For security reasons, it is no more required to share this directory.

8.2 OMC

From R4.0, OmniVista 4760 does not support PM5 software. To configure OmniPCX Office (whatever

is the version) through OmniVista 4760, OMC software has to be installed on the server and client

PCs.

OmniPCX Office can be configured from a 4760 client after following the procedure below:

Uninstall PM5 software install on the PC.




Reboot the PC.

Install OMC software 700/xx or OMC 800/xx or OMC810/xx or OMC900/xx or OMC910/xx.

Reboot the PC.

Run 4760 client, open Configuration application and launch the "Configure" menu after

selecting an OmniPCX Office: OMC client will be automatically open.

Notes

The same procedure has to be applied on PC hosting 4760 server to perform OmniPCX Office

maintenance operations.

Administrative parameters (mandatory customer information) must be configured on each

OmniPCX Office that we aim to manage from OmniVista 4760.

9 ALCATEL-LUCENT OFFICE (4200)

OmniVista 4760 R4.2 is the last release compatible with Alcatel-Lucent Office

(4200).

OmniVista 4760 R5.2 is no more compatible with Alcatel-Lucent Office (4200).




10 CORRECTIONS

10.1 Corrections in R5.2

10.1.1 Problems reports fixed in R5.2.03.00.c

CR id CR headline

crms00352935 Installation fails on Windows7 Russian

version

crms00367194 Cut and paste in Directory

crms00371525 Directory Server Control Center icon

crms00392568

crms00429622

Directory not available after migration

if Replication is activated.

Crms00419899 Graphic view locks the Client

crms00444949 Audit: all files always loaded

crms00454921 OXE J2 help files missing

crms00455063 Incomplete GUI for Inheritance

crms00455707 Importing ldif files failed

crms00457032 Web Directory is not correct after

upgrade.

10.1.2 Problems reports fixed in R5.2.02.00.b

CR id CR headline

crms00256881 Directory/link creation

crms00347803 Improvment for diagnostic tool

crms00347804 Improvment for diagnostic tool

crms00348669 Adminnmc locked

crms00348858 OXe Users Export failed

crms348925 Primary link with hunt group

crms00350346 Password with ToolsOmnivista

crms00351328 Audit process missing after upgrade

crms00364110 Web Directory:search not correct

crms00365836 Web Directory:search not correct

crms00368525 Pawword policy:bad translation

crms00368529 Password policy:unlock parameter

crms00368533 Password policy:number of login

attempts




10.1.3 Problems reports fixed in R5.2.01.04.c




10.1.4 Problems reports fixed in R5.2.01.03.d










11 RECOMMENDATIONS

11.1 INFRASTRUCTURE / INSTALLATION

11.1.1 TCP ports to be opened

Refer to Installation Manual.

11.1.2 Installation of MOXA driver

Driver version for Windows® 2000/XP, that is supplied with MOXA box, is not supported:

Plug and play problems.

Not stable.

Use only the 1.5.18 version supplied on folder TOOLS\MOXA of OmniVista 4760 CD-ROM.

11.1.3 Use of MOXA equipment

It’s necessary to disable DHCP:

Using Telnet:

Telnet on MOXA IP address.

Config server \ DHCP (disable).

Restart.

Using MOXA menu:

Main menu\network Setting\DHCP (disable).

It is recommended to manage the MOXA IP address in the same sub-network than the server one.

It is not recommended to use more than 3 MOXA boxes.

11.2 SECURITY

11.2.1 Password

A unique password is initialized on installation from scratch:

Directory Manager for the SunTM

DSEE manager.

Admin for the SunTM

DSEE administrator.

AdminNMC for the OmniVista 4760 administrator.

DBA for the accounting database access account.

Rules

ASCII characters

Length at least = 8

LDAP constraint: characters not in : ,+"\<>;#&%|^ and <space>

ASA constraint: characters not in !"%&'()*+,-./:;<=>?\^`{|}~ and <space>




Do not lose this password:

Admin and DBA are needed for the maintenance and the upgrade of server,

Admin and Directory Manager cannot connect to the OmniVista, they are used for advanced

management of the SunTM

DSEE.

Do not use AdminNMC, after installation for standard management of OmniVista 4760. Create

other administrator or manager accounts in order to retain the preferences of the various

administrators and managers and always keep a supervisor account even if the password is lost.

11.2.2 Rights

To allocate a right to an OmniVista login, select the predefined groups such as Directory Expert,

Network Expert and add members to these groups.

A login can belong to several predefined groups. In this case, these rights correspond to the sum of

rights of each group.

If there is no relevant profile:

allocate the rights individually:

select each application,

add a specific right (read, write, etc.) corresponding to the individual.

11.3 DIRECTORY

11.3.1 Implementing the photos

Be careful to disk space needed if you inserting photos in the directory: a 20 KB jpg format photo

takes 70 KB in LDAP (10 000 photos => 700 MB in LDAP base).

11.3.2 Creating the PCXs

When creating the PCX, you must specify the number of network node. On network 0 node 1, you

must not enter 001 but directly 1 otherwise the Past Time Performance files loading in database no

longer works.

Avoid the used of . (dot) in the name of the Network, Sub-Network and PCX (In some cases it could be a

problem during restoration of archives accounting tickets)

Example to avoid: Name of PCX : Brest.Alcatel

11.4 CONFIGURATION

11.4.1 Changing the PCX connection

Make sure to cut all connections in progress to this PCX via OmniVista 4760:

cut Telnet,

close Configuration,

but above all in the technical directory, deactivate the Alarm Processing.




As soon as the connection has been cut, carry out your modification in the "Connectivity" tab then if

necessary reactivate the alarm processing.

11.4.2 Free users name in the PCX

It’s extremely inadvisable to name a great amount of free users in the same way (example:

name=FREE). This rule as well concerns Dect Shells.

It’s recommended adding an information in the First name field (example: extension number).

To prevent from entry creation for these extensions in the Enterprise Directory, you have to not validate

the Call by name function.

These extensions ‘s successive allocations / unallocations lead to a lot of inactive sets creation into the

accounting organization.

The cleaning of a great amount of inactive free of ticket entries regularly fails; refer to XTSce15452.

11.5 ALARMS

11.5.1 Alarm supervision

If a PCX has to centralize all the network alarms and events, you must correctly manage the nodes

supervised by this PCX in the PCX incident management. Do not set the node to supervise itself.

If the management is incorrect, the alarm server will be saturated by the events sending which

damage the application operation (slow down, close of some services and disk saturation).

At 4760 server level, create this alarm centralizing PCX to do not restore alarms from a PCX still

unknown in 4760. Do not check the box Alarm Review on the PCX monitored otherwise the alarms

will be doubled.

Starting from R2.1, a character "_" is added to the server name, in the "Events Routing discriminator"

created in the OmniPCX 4400 and Enterprise (SERVER_ instead of SERVER). The number of names

being restricted to 16, it is recommended to suppress previous names in the PCX. If a PCX is not able

to create an "Events Routing discriminator" the alarms are not sent to the corresponding server.

11.6 TOPOLOGY

When the OmniVista 4760 manages a complex PCX network including a lot of inter-nodes links, the

topology display delay can be very long. According to the configuration type, following two solutions

decreases this display time:

a parameter in the Topology application, allows to enable/disable the display of the VPN links:

Preferences\Topology\Configuration\Display VPN links

a script allows to suppress the display ot the inter-node links to reduce the display delay of the

network. It is included in the TOOL directory of the installation CD.

To launch this script proceed as follows:

edit the delnodelink.bat file and enter your own Directory Manager password,

then launch the script on the Omnivista 4760 server PC.




This modification is lost after every network synchronization. So we have to program an automatic

re-launch job in the scheduler:

make a copy of the script under 4760\bin,

add a new job in the scheduler,

add a new task to launch the delnodelink.bat file.

Before any upgrade operation, caution has to be taken to be able to retrieve the work.

11.7 ACCOUNTING

11.7.1 Accounting: Local currency and referenced currency

11.7.1.1 Management overview

OmniVista 4760 allows the following management:

definition of a referenced currency (Euro for instance),

definition of local currencies (with a conversion rate),

input the carrier tariffs in the local currency or in the referenced currency,

cost calculation will be performed in the referenced currency (after applying a conversion rate, if

necessary),

Predefined reports are generated in the referenced currency only.

11.7.1.2 Installation of country = Default

At server installation, the selection of country = Default takes into account the country defined in

Regional Settings of Windows® and initializes referenced currency.

11.7.2 Cost centers different from those of the PCX

This option is only for OmniPCX 4400 and OmniPCX Enterprise Ux and Lx PCXs.

During the installation, you must define the management method of cost centers. If you choose to

dissociate the PCX cost centers from the OmniVista ones, you must manage them in the OmniVista

application. The Cost Center field, in OmniVista, will be completely independent from the cost

center managed on the PCX, there will be no synchronization in either direction.

To force a cost center in the accounting organization:

manage the cost center information in the company directory,

create a cost center directly in the accounting organization; then move the entries in this cost

center.

The Configuration module will continue to see the PCX cost centers.

11.7.3 Purging the accounting tickets

By default, the tickets and reports are purged after 3 months (94 days).

Before modifying these parameters, analyze the site to check that the limit of 20 GB of accounting

data (30 millions tickets) will not be exceeded. Then make the modifications:




in the Directory, Technical tab, move to

NMC/PC_Name/servers/PC_Name/NMCDatabase

select the Database tab,

change the CleanTicketAndAffiliatedOldThan attribute.

11.7.4 Carrier management

11.7.4.1 Tariff: Managing the period

During management of tariffs, period, only the start time is managed, the application

automatically manages the end time.

Do not forget to create the period which begins at 00H00 and loop back with the 1st

one

managed.

11.7.4.2 City / Country name: Loss of performance

During normal use, the number of Town / Country must be reduced. This information is in fact used

to identify in the reports the telephone directions frequently used; for example, to identify the

subsidiaries of a company.

It is not used to calculate the cost of telephone calls.

When the number of City / Country names becomes too high (>5000), the coherence check system

slows down the performance during accounting modifications.

Beyond 10000 Cities/Countries, the calculation of cost is impossible.

It is necessary to create areas and directions to optimize the treatment of the cities/countries.

Example

City country Name Region Paris Prefix 0170

Paris 0170 Prefix 0171

Paris 0171 Prefix 0172

Paris 0172

In this example, for the Cities/Countries, the Paris entry appears 3 times whereas by using the regions

and directions, the Paris entry appears only once.

11.8 REPORT GENERATOR

11.8.1 Weekly accounting report

CAUTION

The week defined in the report application does not begin on Monday but Sunday at 00h00 AM and

finishes on Saturday at 11h59 PM.




11.9 SCHEDULER

11.9.1 Tasks succession order

One‘s attention has to be given to the task’s succession.

The 4760 data backing up must never start when other tasks are running. Actually the saving

operation needs the all services stopping. This may have important bad consequences on

synchronization, tickets loading and cleaning operations.

11.10 MAINTENANCE

11.10.1 Rule of partitioning

It is recommended to have only one partition per physical disk and to separate the partition system

from the application. In effect, if a partition seems to be too small, it is impossible to extend it without

being obliged to format and re-install.

Example: put OS on C: on a disc of 80 GB, and the application on D: on a disc of 72 GB.

If the network allows it, it is recommended to use "network" disk as working space to carry out

upgrades, defragmentation data backups. In effect, each of these operations requires for their

working space near the twice Sybase size therefore depending on the cases up to 40 GB.

11.10.2 Backing up the databases

In case you need to re-install the application, it is possible to use some managed parameters of the

existing OmniVista 4760. To ensure you have as much information as possible on installation, you

must schedule:

the company directory LDIFF export,

the PCX network LDIFF export,

the carrier Code book export.

11.10.3 Backing up the OmniVista 4760 database

By default, no backup is scheduled. Only closing the server once a week on Sunday at 1 AM is

planned to impose a memory release under Windows®.

The backup stops the services (the server is not available) and compresses the databases in zip

format. To carry out the backup, you must have twice as much space free as the total size of all the

databases.

You must schedule a backup at least once a week of the OmniVista 4760 data and purge these

backups to avoid the disk saturation.

Refer also to the chapter “Tasks succession order” (Scheduler) to correctly schedule this task.

Note

A backup must be carried out before any important operation on the server (Upgrade, Retrospective

Cost Calculation on the complete database, etc.).




11.10.4 Defragmentation of the OmniVista 4760 database

It is recommended to schedule a monthly defragmentation of the databases. The defragmentation of

OmniVista 4760 databases allows to optimize the performances of jobs relative to Alarms,

Accounting, Past Time Performance or VoIP applications.

It is also recommended to run a defragmentation before upgrading a version.

CAUTION

This operation stops the services: the server is not available.

On a large database of about 1 GB, allow about 2H30min.

11.10.5 Backing up / Restoring OmniPCX 4400/Enterprise

11.10.5.1 Backup

You can schedule periodic backups of OmniPCX Enterprise PCXs.

From OmniVista 4760 R5.0, there is no need to use the swinst PCX tool to setup this operation.

If the download is scheduled at the PCX network level, only the PCXs which have ticked Automatic

database save on the tab Data Collection of the PCX declaration (Technical directory module)

will be backed up.

11.10.5.2 Restore

The data is restored in two steps:

1 OmniVista 4760 places the backup in a local directory of the PCX disk. The PCX can refuse the

copy if this local directory (\usr4\BACKUP\IMMED) already contains a backup.

2 Use swinst to restore this backup.




12 ADVANCED MANAGEMENT

12.1 INFRASTRUCTURE / INSTALLATION

12.1.1 Reinstalling the server

To reinstall the OmniVista 4760 server application with an empty database on a PC where OmniVista

has already been installed, you must first uninstall the application. The server module must be

uninstalled using a local administrator account.

To uninstall the OmniVista 4760 server:

Close all the OmniVista 4760 client applications. The SNMP and/or Compaq manufacturer

services must not be enabled during the uninstall phases.

Use the Add/Remove programs interface from the Control Panel.

Select the OmniVista 4760 Server program and click on Remove.

The uninstall procedure will take several minutes.

The SunOne Directory server and the SQL Anywhere 10 software will also be removed.

Note

The Java Runtime Environment is not uninstalled.

Restart the computer to complete the uninstallation procedure.

CAUTION

If you cannot access "OmniVista 4760 Server" from Add/Remove programs you should proceed

to a manual uninstallation of various items.

This procedure must be applied when Windows® Installer cannot restore the original state of the

PC after an incident when installing or upgrading.

It must also be applied if the automatic uninstallation fails.

CAUTION

As the registry is involved during this operation, it is recommended to perform before a system

backup for a possible restore later.

From Add/Remove programs, remove if necessary the visible programs (Directory Server

and SQL Anywhere 10 – Software).

Remove the Windows®\system32\productregistry file.

The presence of this file may prevent the re-installation of Sun One LDAP server on the same

path as the previous installation

Copy the PsExec directory from the uninstall tool.zip file available on the DVD of the

version (Tools) to c:\Program Files.

Launch reg_del.bat.

This commands opens the registry editor.

Import the del_regkeys_TS_50.reg file.

Reboot the PC.




Remove the directories where are installed various components of the system: 4760 server,

Sybase, SunOne, SQL database.

Refer to the technical communication TC1007 OmniVista 4760 Installation / Unsinstallation for

additional information about the manual uninstallation.

12.1.2 Change the IP address

12.1.2.1 Change procedure

1 Inform the users then stop the NMC Service Manager Service.

2 Change the IP address of the server.

3 In the \4760\data\Notify directory, delete all files EXCEPT Notify.cfg.

4 Reboot the server.

12.1.2.2 Add a new IP address

To prevent having to change the server IP address (example for OmniVista 4760 on an installer's

portable computer), leave the main IP address alone but add a secondary IP address on NT.

Then PCXs can be defined on the sub-network corresponding to this secondary address.

12.1.3 Change the PC name or the Windows® DNS suffix

This operation is not supported.

In such a case, the workaround consists in recovering the data of the old PC in the following way:

Export/import the PCX Technical data and Company directories,

Export/import the carriers configuration.

Recover the SQL database files in the 4760\data directory to copy them on the new PC after

installing the 4760 in the same version.

12.1.4 Change the passwords

The passwords of following accounts can be changed:

dba

Admin

Directory Manager

The change is made by using the toolsOmnivista tool available from 4760\bin directory.

Directory Manager password is needed to change account passwords.

For more information, please refer to the technical communication TCV045 How to change

OmniVista 4760 server passwords.




12.1.5 Re-assignation of accounting tickets to active entities

The ToolsOmnivista tool is used to update the organization of the accounting. It is used to assign

the tickets of inactive entities to the corresponding active entities. Then these inactive entities are

removed.

This feature allows a re-sequencing of the organization after a period of adaptation which generally

follows the startup of an OmniVista 4760 server.

12.2 DIRECTORY

12.2.1 Access the OmniVista 4760 directory through Alcatel 4059

In Alcatel 4059, enter:

the OmniVista 4760 server name,

the company directory root, example o=MyCompany, o=DirectoryRoot.

By default, Search base field length is limited to 27 characters in Alcatel 4059 LDAP directory

(SR 1-64755241).

the password defined on OmniVista 4760 (in case of confidentiality management).

For more information, refer to Alcatel 4059 installation procedure; the minimum release is

R4.014.10.

12.2.2 Customize the WEB consultation

12.2.2.1 Available options

The Administrator manual describes the client Web customization in Directory section.

You can:

Customize the attributes of a Company Directory level,

Customize the results display and print parameters (number of lines, grid sort, attributes to display

in grid, printed attributes)

Customize the detail and edit parameters (attributes to display and to edit in detail view)

Customize the search filters,

Customize partially the predefined themes (name, logo, logo position),

Customize fully the “Custom” theme (name, logo, logo position, colors, background, fonts).

12.2.3 Customizing the directory field names

An integrated tool allows to modify most of the field names displayed in Company Directory from a

Web or installed client.

To launch this tool proceed as follows:

Start/Programs/Omnivista 4760/Tools/Dictionary customization

For more information, refer to the Administrator Manual - Directory section.




12.3 ALARMS - TOPOLOGY

12.3.1 E-mail server

OmniVista 4760 can send alarms, reports or a accounting monitoring notification to an e-mail server

specifying a local or external e-mail address. Transmission is done via SMTP on the default port 25.

The sender's name of messages can be customized in the technical directory (nmc\server_name).

To check that the e-mail server can be reached by SMTP on port 25, try to connect via Telnet. On the

server PC, at the DOS command prompt, execute:

Telnet Server_Name_mail 25

If the SMTP port of your e-mail server is not the standard port 25, change it during the Telnet test. If

the test is successful on this port, copy the port number in the OmniVista 4760 application :

run the Directory application then click on the Technical tab,

click on the machine name in the tree structure. In the data area, modify the attribute E-mail

server and set :

E-mail_Server_Name:Port_Number (do not insert spaces around the ‘ : ’)

For more information, refer to the technical communication TCV020 Sending e-mails with

OmniVista 4760 – Release 2.0.

12.4 REPORT GENERATOR

For more information, refer to the troubleshooting guide TG0026 Reports and the Technical Communication

TCV059.

12.4.1 Schedule a report export

12.4.1.1 Restriction

To schedule a report with a file export to a network drive, OmniVista 4760 must be able to use a

Windows® account with certain rights.

If the password is wrong or obsolete, the report will no longer be exported.

12.4.1.2 Procedure

Use an account with local administrator rights on the OmniVista Server PC. We will suppose that this

account is named ADM4760 and that the Server PC is named PCSERVER.

If the Server PC is installed in a Windows® domain and that the users log in DOMUSER, therefore the

login of this account is DOMUSER\Adm4760.

If the Server PC is installed in a workgroup, the login of this account is PCSERVER \Adm4760.

1 Run a Windows® session as local administrator of the server PC.

2 Define a default printer for "User4760", if necessary.




3 Run Start/Administrative Tools (Common)/User manager.

Select the menu Policy/User rights.

Tick Show Advanced user rights.

For the following rights, add the user Adm4760 :

Act as a part of the operating system

Increase quotas/Adjust the memories quotas

Replace a process level token

Open a session locally

4 Grant the OmniVista 4760 the right to use this user. To do this :

run the Directory application, then click on the System tab,

in the tree structure move to

NMC / Server_Name / servers / Server_Name / ExecdExc

click on NT Account ,

manage the attributes :

User = DOMUSER\Adm4760, for a Server PC belonging to a domain of which the users

are managed under DOMUSER,

User = PCSERVER\ADM4760, for a Server PC belonging to a Workgroup and calling

PCSERVER,

Password: your password.

5 Run a scheduled report to check the correct setting.

12.4.2 Export to PDF format with specific characters to languages

The specific characters to languages (Polish, Czech, Chinese, Russian, etc.) are taken into account in

exported reports in pdf format.

To do that, you should specify the Windows® font which supports these specific characters: under

NMC\serverName : complete Name of font family for pdf export and Available

font styles (pdf export) (set the font name in an application such as Word).

12.4.3 Change of paper format for printing the reports

The paper format for printing reports is selected when installing the server. However, you can change

it after. In the technical directory,click on the name of server in the tree. In the right window, select the

appropriate Paper Format.




12.5 MAINTENANCE

12.5.1 Backup on a remote host

12.5.1.1 Restriction

The OmniVista 4760 Server PC and the remote host must be located on the same Windows® host

domain: in the same workgroup or in the same domain.

This backup mode requires using a Windows® account. Therefore this account must be enabled of

the OmniVista 4760 server and have the right to move files on the remote host.

12.5.1.2 Procedure in a domain

For the requirements of this procedure, we will suppose that the hosts are installed in the same

DOMMACHINE domain and that the users are identified in the DOMUSER domain.

Use a networked account with local administrator rights on the OmniVista Server PC. Let us name this

account ADM4760. The login of this account is DOMUSER\Adm4760.

1 Share a repertory on the remote host for the user DOMUSER\ ADM4760.

2 On the Server PC, run a Windows® session as DOMUSER\ ADM4760.

3 Grant the Execcdex and SaveRestore services, the right to use this user. To do this :



NMC / Server_Name / servers / Server_Name / ExecdEx



User = DOMUSER\Adm4760,

Password : your password,

carry out the same management for SaveRestore

4 When the Maintenance module is run, you can select a network disk for the backup.

12.5.1.3 Procedure in a Workgroup

For the requirements of this procedure, we will suppose that the hosts are installed in the same

WORKGROUP1 workgroup and that the Server PC is named PCSERVER.

Use a Server PC account with local administrator rights on the OmniVista Server PC. We will suppose

that this account is named ADM4760. On the remote host, create the same ADM4760 with the same

password.

1 Share a repertory on the remote host for the user ADM4760.

2 On the Server PC, run a Windows® session as DOMUSER\ ADM4760.

3 Grant the Execcdex and SaveRestore services, the right to use this user. To do this :






NMC / Server_Name / servers / Server_Name / ExecdEx



User = PCSERVER\Adm4760,

Password : your password,

carry out the same management for SaveRestore

4 When the Maintenance module is run, you can select a network disk for the backup.

12.6 CONFIGURATION

12.6.1 Simple Configuration Profile

The OmniPCX Enterprise security access profile 10 has been designed to allow some users such as

attendants to perform simple configuration operations.

By default, user with this profile will only have:

All rights on hunt group configuration.

All rights on user configuration.

All rights on Direct speed dialing number prefix configuration.

To active this profile for the OmniVista user ATTENDANT4760:

From Company directory, set the ATTENDANT4760 person into the member list of the

"Simplified Configuration" group (localized in Company name / Administration/ Groups).

From Security panel menu, open Access Control Editor for Configuration application: check

Profile 10 has been set to "Simplified Configuration" group.

If it is not the case, add or update rights of the "Simplified Configuration" group with:

Access Level= Normal

OmniPCX 4400 Access Level= Profile 10

Note

Profile (10) can be edited to add more available items (for instance program keys) or to remove

available items (for instance hunt groups).




13 NEW FEATURES (New R5.02.03.00.c features)

13.1 INFRASTRUCTURE

Support of OmniPCX Enterprise R11 and OmniPCX Office 9.1.

13.2 Server Update with Change of Operating System

Server update in R5.2.03.00.c with change of Operating System

Concerns the customers who want change the Operating System of their Server:

W2003 Server to W2008 Server or Win7

XP to W2008 server or Win7

OS Migration Steps.doc




14 RESTRICTIONS AND IDENTIFIED DEFAULTS

14.1 INFRASTRUCTURE

Installation

The identifiers of Experts groups must not have accents.

Using a Web administration client on XP SP2 with firewall activated

The default automatic firewall configuration is only performed on standard 4760

client. If you are using the Web applet, you need configure manually the XP

firewall and add the Corba port 30500 to 30509 on the XP client.

Path of installation for Sybase binaries

Do not install Sybase directly on the drive root (D:). In that case, if 4760 is

uninstalled, all data on D: will be removed.

Recommendation

Use C:\Program Files or C:\Program Files (x86) default folder to install

Sybase.

Refer to technical communication TCV056 Complete erasing of hard disk following

OmniVista 4760 uninstallation

Sybase software must not be installed in the same directory as OmniVista 4760; the

upgrade of server would fail.

Firefox limitation

If Firefox 1.0 is your default browser, you cannot launch the external application that

use Default Browser setting.

In technical (system) directory, in General tab, under NMC>Application>

External Applications, the default setting of the browser has to be

replaced by:

Type= Windows® application <Name of the binary> = C:\Program

Files\Mozilla Firefox\firefox.exe

SP1 installation on Windows® 2003 Server

Some PCs, especially the HP ML370G4, require a Bios and some drivers update

before Windows® 2003 Server SP1 patch installation. Otherwise the update

procedure would fail and the only solution would be to reinstall the operating

system. It's mandatory to have a 4760 data backup on a remote device. Refer

to the technical communication TCV066 Installation of Service Pack 1 for

Windows® 2003 over a HP/Compaq ML370 server will end in a definitive

crash of the PC and all data will be lost.




14.2 CONFIGURATION

USB modems are not supported on 4760 Server

Software download: 4 simultaneous downloads max

XTSce46865 The first key typed just open the edit mode. The first character is not written in the

field.

14.3 DIRECTORY

XTSce85390 Web directory: add edition ergonomics for Confidentiality field.

crms00192881 This is a system restriction

In the System Directory, the upper value for the Network number is 2140. Although

there is neither warning nor restriction when managing this field, a greater

value will lead to an error during Accounting Counter Calculation:

"Accounting: 233: 23502: com.sybase.jdbc2.jdbc.SybSQLException: Erreur SQL

Anywhere -195: the column 'PbxId' of the table 'EntityInfo' can not contain the value

NULL"

crms00280605 Impossible to change the language for the web directory.

Add the URL to the "Trusted Site" list in the browser.

crms00281819 Issue when consulting the web directory: when you select one element of the

organisation tree in the company directory you should when clicking on

research tab make the search from this element and this is not the case until

"Creation of entries authorized" is not validated

(System directory\NmcConfiguration\GlobalPreferences\DirectoryClient\GlobalParameters)

14.4 INSTALLATION

crms00101845 4760 Server uninstall: Displayed remaining time is totally erroneous / 1-83372904.




14.5 MAINTENANCE

PCX versions before E2.504 (UNIX versions) do not accept the backup commands sent by OmniVista

4760.

For these versions, OmniVista 4760 can only recover the mao-dat and cho-dat files daily created

by the PCX in the /usr4/BACKUP/DAY directory.

The files created by the PCX immediate backup command can no more be recovered by OmniVista

4760 Maintenance application.

A possible backup can be carried out by a "manual" FTP transfer.

Software Download

Starting from OmniPCX Enterprise R9.1, intermediate log files for a software update are managed

differently:

Before R9.1:

A unique SofwareUpdatestus_X file in the /var/ftp/pcx/logs folder.

(X=context Id)

Starting from R9.1:

Several files are created in the /tmpd/soft_install folder:

SofwareUpdatestus_X_1 (log for the remote load operation)

SofwareUpdatestus_X_Y (one file per installed client)

In both cases the final SofwareUpdatestus_X_end file is located in the /var/ftp/pcx/logs

folder.

Following this modification, OmniVista 4760 versions before R5.1.06.03.c are no more able to

retrieve intermediate logs during an update for PCX starting from R9.1. The solution is to use the

option “for one day” and then to select the files to restore in the list. All the files to restore can be

previously saved in a single folder.

14.6 SIP DM

SIP Device Management Server must have the version 1.2.000.010 or higher to be compatible with

OmniVista 4760 R5.2. The current version is 1.2.000.020.

SIP DM is not compatible with Windows® 2008 and Windows® 7.




14.7 OTHER

Concerning new feature: Arabic language

Each user can choose Arabic language in the list of OmniVista 4760 client languages. Other users can

choose other languages (like English) on the same server. Restrictions:

No ergonomics change: translation in Arabic, but no change in the screens display (from left to right)

Configuration: Content of the OXE object model is in the OXE installation language

Alarms: Diagnosis of the alarms in the OXE language

Audit: content of the logs (object, action) in the OXE language

Reports: export on pdf not supported

For Name/Surname displayed in Arabic on the 8000 & 9000 series phone sets

As of OXE 9.1 latest version, the language can be chosen for each phone set, from the phone set MMI or

from OmniVista 4760 Configuration

The Arabic names are managed in OmniVista 4760 Configuration. Arabic characters appear from right to

left, aligned on the left. Once a name is set up in Arabic, it is displayed in Arabic on all the OXE phone sets

Names/surnames in Arabic (UTF8) are not synchronized in the OmniVista 4760 web Directory.

Only the English (non UTF8) names/surnames are synchronized. It means that, for the web Directory or

the Call by name overflow, names should be created in Arabic and in English as well for the Directory.

Modification of English names is synchronized between OXE and the Directory, but modifications in Arabic names should be made on both sides.




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/ALUEnterpriseCare

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 -

http://twitter.com/ALUEnterpriseCa

http://www.facebook.com/ALECustomerCare

https://businessportal.alcatel-lucent.com/alugesdp/faces/gesdp/customerSupport/CustomerSupport.jspx

https://businessportal.alcatel-lucent.com/alugesdp/faces/gesdp/integration/KnowledgeDatabase.jspx

https://businessportal.alcatel-lucent.com/alugesdp/faces/gesdp/integration/KnowledgeDatabase.jspx

https://businessportal.alcatel-lucent.com/alugesdp/faces/gesdp/integration/KCSKnowledge.jspx

http://twitter.com/ALUEnterpriseCa

http://www.facebook.com/ALECustomerCare