TC1660en

8/19/2019 TC1660en

1/74

1

TECHNICAL COMMUNICATION No. TC1660 Ed. 01

OmniVista 4760 Nb of pages : 76 Date : 06-04-2012

URGENT

NOT URGENT TEMPORARY PERMANENT

SUBJECT : INSTALLATION PROCEDURE FOR VERSION 5.2.02.00.b - RELEASE 5.2

This is a technical release of OmniVista 4760 with the version 5.2.02.00.b.

It is available on Alcatel-Lucent Business Portal (https://businessportal.alcatel-lucent.com) and onDVD-ROM with the reference 3BH 11632 AKAC.

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

described in the installation procedure for version 5.2.02.00.b.

8/19/2019 TC1660en

2/74

2

8/19/2019 TC1660en

3/74

OmniVista 4760

INSTALLATION PROCEDURE FOR VERSION5.2.02.00.b - RELEASE 5.2

Ed. 01/ 04-06-2012 3 TC1660

CONTENTS

1.1.1.1. GENERALGENERALGENERALGENERAL ............................................................................................................................................................................................................................................................................................................................................7777

2.2.2.2.

NON STANDARD FEATURENON STANDARD FEATURENON STANDARD FEATURENON STANDARD FEATURESSSS............................................................................................................................................................................................................................8888

2.1.2.1.2.1.2.1. NonNonNonNon----operational configurationoperational configurationoperational configurationoperational configuration............................................................................................................................................................................................................................................................8888

2.2.2.2.2.2.2.2. Features under PCSFeatures under PCSFeatures under PCSFeatures under PCS (Premium Customer Support) (Complex solutions)(Premium Customer Support) (Complex solutions)(Premium Customer Support) (Complex solutions)(Premium Customer Support) (Complex solutions) ............8888

2.3.2.3.2.3.2.3. Specific processSpecific processSpecific processSpecific process ........................................................................................................................................................................................................................................................................................................................................................8888

3.3.3.3. CONTENT OF THE SOFTWCONTENT OF THE SOFTWCONTENT OF THE SOFTWCONTENT OF THE SOFTWARE PACKAGE ARE PACKAGE ARE PACKAGE ARE PACKAGE ............................................................................................................................................8888

3.1.3.1.3.1.3.1. ReferencesReferencesReferencesReferences ....................................................................................................................................................................................................................................................................................................................................................................................8888

3.2.3.2.3.2.3.2. PatchesPatchesPatchesPatches ........................................................................................................................................................................................................................................................................................................................................................................................................ 9999

3.3.3.3.3.3.3.3.

License fileLicense fileLicense fileLicense file ....................................................................................................................................................................................................................................................................................................................................................................................9999

4.4.4.4. PREREQUISITESPREREQUISITESPREREQUISITESPREREQUISITES ................................................................................................................................................................................................................................................................................................10101010

4.1.4.1.4.1.4.1. Server PC prerequisitesServer PC prerequisitesServer PC prerequisitesServer PC prerequisites ................................................................................................................................................................................................................................................................................................ 10101010

4.1.1. Hardware and software..................................................................................10

4.1.2. Software and hardware compatibility.............................................................15

4.1.3. Configuring the Server PC ..............................................................................15

4.2.4.2.4.2.4.2. PCX prerequisitesPCX prerequisitesPCX prerequisitesPCX prerequisites ....................................................................................................................................................................................................................................................................................................................................16161616

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

4.2.2.

IP, PPP connections to OmniPCX Office ...........................................................18

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

4.2.4.

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

4.2.5. OmniPCX 4400/Enterprise software locks ......................................................19

4.3.4.3.4.3.4.3. Prerequisites of administration Client PCsPrerequisites of administration Client PCsPrerequisites of administration Client PCsPrerequisites of administration Client PCs....................................................................................................................................................................................20202020

4.4.4.4.4.4.4.4. Prerequisites of Client PCs for directory consultation via WEBPrerequisites of Client PCs for directory consultation via WEBPrerequisites of Client PCs for directory consultation via WEBPrerequisites of Client PCs for directory consultation via WEB ............................................................ 20202020

4.5.4.5.4.5.4.5.

Compatibility with SIP Device Management ServerCompatibility with SIP Device Management ServerCompatibility with SIP Device Management ServerCompatibility with SIP Device Management Server................................................................................................................................ 20202020

5.5.5.5. DATA COLLECTION OF TDATA COLLECTION OF TDATA COLLECTION OF TDATA COLLECTION OF THE SERVERHE SERVERHE SERVERHE SERVER ................................................................................................................................................................21212121

8/19/2019 TC1660en

4/74

OmniVista 4760


Ed. 01/ 04-06-2012 4 TC1660

5.1.5.1.5.1.5.1. List of data to be collectedList of data to be collectedList of data to be collectedList of data to be collected................................................................................................................................................................................................................................................................................21212121

5.2.5.2.5.2.5.2. Company directory Company directory Company directory Company directory............................................................................................................................................................................................................................................................................................................................ 21212121

5.3.5.3.5.3.5.3. Carrier configurationCarrier configurationCarrier configurationCarrier configuration ............................................................................................................................................................................................................................................................................................................21212121

5.4.5.4.5.4.5.4. Security Security Security Security ................................................................................................................................................................................................................................................................................................................................................................................................ 22222222

5.5.5.5.5.5.5.5. Backup modeBackup modeBackup modeBackup mode ............................................................................................................................................................................................................................................................................................................................................................22222222

6.6.6.6. INSTALLATIONINSTALLATIONINSTALLATIONINSTALLATION....................................................................................................................................................................................................................................................................................................23232323

6.1.6.1.6.1.6.1.

Additional installation of an integrated PC in factory Additional installation of an integrated PC in factory Additional installation of an integrated PC in factory Additional installation of an integrated PC in factory ................................................................................................................ 23232323

6.2.6.2.6.2.6.2. Standard server installation procedureStandard server installation procedureStandard server installation procedureStandard server installation procedure ....................................................................................................................................................................................................23232323

6.2.1. Mandatory parameters installation.................................................................25

6.2.2.

Restorecontext.ini file......................................................................................27

6.3.6.3.6.3.6.3. Patches delivered within a versionPatches delivered within a versionPatches delivered within a versionPatches delivered within a version................................................................................................................................................................................................................................27272727

6.4.6.4.6.4.6.4. Server postServer postServer postServer post----installationinstallationinstallationinstallation ................................................................................................................................................................................................................................................................................................ 28282828

6.5.6.5.6.5.6.5. Client installation procedureClient installation procedureClient installation procedureClient installation procedure ................................................................................................................................................................................................................................................................ 28282828

6.6.6.6.6.6.6.6. Accessing OmniVista 4760 via a browser Accessing OmniVista 4760 via a browser Accessing OmniVista 4760 via a browser Accessing OmniVista 4760 via a browser ....................................................................................................................................................................................29292929

6.6.1.

Installation......................................................................................................29

6.6.2. Checking the installation ................................................................................30

7.7.7.7. UPGRADESUPGRADESUPGRADESUPGRADES............................................................................................................................................................................................................................................................................................................................ 31313131

7.1.7.1.7.1.7.1. PrerequisitesPrerequisitesPrerequisitesPrerequisites ................................................................................................................................................................................................................................................................................................................................................................31313131

7.2.7.2.7.2.7.2. License file updateLicense file updateLicense file updateLicense file update ............................................................................................................................................................................................................................................................................................................................ 31313131

7.3.7.3.7.3.7.3. Upgrading the OmniVista 4760 server to version R5.Upgrading the OmniVista 4760 server to version R5.Upgrading the OmniVista 4760 server to version R5.Upgrading the OmniVista 4760 server to version R5.2.01.04.c2.01.04.c2.01.04.c2.01.04.c ....................................................32323232

7.4.7.4.7.4.7.4. Installing a corrective patchInstalling a corrective patchInstalling a corrective patchInstalling a corrective patch........................................................................................................................................................................................................................................................................33333333

7.5.7.5.7.5.7.5. Upgrading the OmniVista 4760 client to version 5.2.02.00.bUpgrading the OmniVista 4760 client to version 5.2.02.00.bUpgrading the OmniVista 4760 client to version 5.2.02.00.bUpgrading the OmniVista 4760 client to version 5.2.02.00.b ................................................................ 33333333

7.5.1.

Installing the patch .........................................................................................33

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

8.8.8.8. OMNIPCX OFFICEOMNIPCX OFFICEOMNIPCX OFFICEOMNIPCX OFFICE ................................................................................................................................................................................................................................................................................35353535

8.1.8.1.8.1.8.1. Writing rights on dedicated OmniPCX Office directoriesWriting rights on dedicated OmniPCX Office directoriesWriting rights on dedicated OmniPCX Office directoriesWriting rights on dedicated OmniPCX Office directories................................................................................................35353535

8.2.8.2.8.2.8.2. OMCOMCOMCOMC................................................................................................................................................................................................................................................................................................................................................................................................................35353535

9.9.9.9.

ALCATEL ALCATEL ALCATEL ALCATEL----LUCENT OFFICE (4200)LUCENT OFFICE (4200)LUCENT OFFICE (4200)LUCENT OFFICE (4200) ....................................................................................................................................................................................36363636

8/19/2019 TC1660en

5/74

OmniVista 4760


Ed. 01/ 04-06-2012 5 TC1660

APPENDIX

APPENDIX 1 – CORRECTIONS

APPENDIX 2 – RECOMMENDATIONS

APPENDIX 3 – ADVANCED MANAGEMENT

APPENDIX 4 – NEW FEATURES

APPENDIX 5 – IDENTIFIED DEFAULTS AND RESTRICTIONS

8/19/2019 TC1660en

6/74

OmniVista 4760


Ed. 01/ 04-06-2012 6 TC1660

8/19/2019 TC1660en

7/74

OmniVista 4760


Ed. 01/ 04-06-2012 7 TC1660

1. GENERAL

This document describes the installation procedure for OmniVista 4760 version 5.2.02.00.b.

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

SIP Device Management Server must have the version 1.2.000.010 or higher to becompatible 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 technicalcommunications 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 deprecatedmode

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

These operations must be performed by an expert (ACSE) trained on the product. In the oppositeside, you can contact the "Professional Services" (mailto:[email protected] ).

8/19/2019 TC1660en

8/74

OmniVista 4760


Ed. 01/ 04-06-2012 8 TC1660

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. CONTENT OF THE SOFTWARE PACKAGE

3.1. References

− OmniVista 4760 Release 5.2 package: 3BH 11632 AKAC which contains following items:

• OmniVista 4760 software DVD: 3BH 11628 AMAC which contains:

♦ Version Release R5.2.02.00.b

♦ OmniVista 4760 Installation manual : 3BH 19261 ed. 16

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

♦ Security Guide : 8AL 90700 ed. 01

• Documentation CD: 3BH 11630 AKAB which contains :

♦

Administrator manual : 3BH 19260 ed. 15♦ 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

8/19/2019 TC1660en

9/74

OmniVista 4760


Ed. 01/ 04-06-2012 9 TC1660

3.2. Patches

No additional patches in this package.

3.3. 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 filefor 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 declarationnode for OmniVista 4760 server.

CAUTION

• If the declaration node is OmniPCX 4400 ≤ R5.0 Ux, you can no more get the OmniVista4760 license file.

• If the declaration node is OmniPCX Office, OmniPCX Enterprise ≥ R5.0 Lx, the license file isproduced 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.2End of corrections 10/05 04/06 10/06 04/07 01/08 05/09 01/10 06/11

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

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

Versions of embedded software:

InstallShield® JRE SunTM DirectoryService Enterprise

Edition

Sybase Apache PHP

2008 1.6.0.21 DSEE 7.0 SQL Anywhere 1010.0.1.4157

2.2.16.0 5.2.14.14

8/19/2019 TC1660en

10/74

OmniVista 4760


Ed. 01/ 04-06-2012 10 TC1660

4.

PREREQUISITES

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

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 beminimum, 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 systemconfiguration and to help you to generate the license file.

8/19/2019 TC1660en

11/74

OmniVista 4760


Ed. 01/ 04-06-2012 11 TC1660

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

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

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, maximum30000 users, directory replication not supported.

Data Centre and other specific Windows® editions (Entreprise Edition) are not validated. Regarding Small business edition this Windows® edition is packaged as a Windows® Domain Controller: itincludes 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

8/19/2019 TC1660en

12/74

OmniVista 4760


Ed. 01/ 04-06-2012 12 TC1660

8/19/2019 TC1660en

13/74

OmniVista 4760


Ed. 01/ 04-06-2012 13 TC1660

8/19/2019 TC1660en

14/74

OmniVista 4760


Ed. 01/ 04-06-2012 14 TC1660

Test environment:

8/19/2019 TC1660en

15/74

OmniVista 4760


Ed. 01/ 04-06-2012 15 TC1660

4.1.2.

Software and hardware compatibility

The installation on a dedicated Server PC in accordance with the prerequisite allows a correctoperation of the software. If the number of users is lower than 250 and if the Server PC mustsupport other applications, you should analyze the compatibility, estimate the performancerequirements 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 compatibilitybetween 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 isbetter 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 betwice 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.

− An other 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.

8/19/2019 TC1660en

16/74

OmniVista 4760


Ed. 01/ 04-06-2012 16 TC1660

• 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). Youmake sure that the "NetBios name of the computer" is the same as the "name of the computer".To read the "NetBios name of the computer", click on the button Other from modificationwindow of the name of the computer.

− For the first OmniVista 4760 server installation on a new PC, this one has to be connected to theIP network. Otherwise the installation would fail during the Sun TM DSEE server installation. Themessage 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 notavailable in OmniPCX 4400 Release 3.0).

8/19/2019 TC1660en

17/74

OmniVista 4760


Ed. 01/ 04-06-2012 17 TC1660

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

Release4760

ReleasePCX

Software version equal toor higher than

IP or IP/X25connection

PPP connection

1.5 3.0 C1.532.5.w (except STAP) Yes No1.5 3.2M C1.712.5.c, C1.714.3.a Yes Yes1.5 3.2 C2 C1.762.21 Yes Yes1.5 4.1 D1.305.4.f Yes Yes1.5 4.1.1 D1.311.7.d Yes Yes

1.5 4.2.1 D2.304.4.s Yes Yes2.0 5.0 Ux D2.313.7.f Yes Yes2.0 5.0.1 Ux D2.314.7.p Yes Yes2.0 5.0 Lx E1.604.9.t Yes No2.1 5.1 E2.404.u Yes No2.1 5.1.1 E2.502.2.p Yes No2.1 5.1.2 E2.504.1.ai Yes Yes3.0 6.0 F1.602.3.i Yes No3.0 6.0.1 F1.603.1.l Yes Yes3.1 6.1 F2.500.6.g Yes No3.1 6.1.1 F2.502.12 Yes Yes

3.2 6.2 F3.301.36 Yes Yes4.0 7.0 F4.401.13 Yes Yes4.1 7.1 F5.401.25.b Yes Yes4.2 8.0 G1.302.5 Yes Yes4.2 8.0.1 G1.503.23.b Yes Yes5.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 YesR5.2 R9.1 I1.605.22 Yes Yes (2)R5.2 R10.0 J1.410.39.a Yes Yes (2)

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

R5.2.2 R10.1 J2.501.9.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 OmniVistareleases.

8/19/2019 TC1660en

18/74

OmniVista 4760


Ed. 01/ 04-06-2012 18 TC1660

4.2.2. IP, PPP connections to OmniPCX Office

ReleasesSoftware version equal to or higher

thanIP connection

PPP connection(1)

1.0 Not supported No No1.1 1.0.19.06 (2) Yes Yes2.0 2.0.32.013 Yes Yes2.1 210.083.001 Yes Yes3.0 300/19.1 Yes Yes3.1 310/038.001 Yes Yes4.0 400/022.001 (1) Yes Yes4.1 410/015.005 (1) Yes Yes5.0 500/030.004 (1) Yes Yes5.1 510/017 (1) Yes Yes6.0 600/014.001 Yes Yes7.0 700/012.001 Yes Yes7.1 710/022.001 Yes Yes8.0 800/24.1.a Yes Yes (3)8.1 810/045.003 Yes Yes (3)8.2 820/026.005 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. Formore information, refer to the technical communication TCV039 OmniVista4760 licenses.

(3)

Only with Windows® 2003

4.2.3.

OMC Release Compatibility with Operating Systems

OMC Releasesmin

Windows® XPSP2

Windows® 2003SP1/2

Windows® 7 Windows® 2008

600 / 14.1.d Yes Yes No No700 / 8.1.c Yes Yes Yes No800/24.1.a Yes Yes Yes Yes810/31.1.a Yes Yes Yes Yes820/15.1.a Yes Yes Yes Yes

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

Releases

≥ R4

8/19/2019 TC1660en

19/74

OmniVista 4760


Ed. 01/ 04-06-2012 19 TC1660

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.5. OmniPCX 4400/Enterprise software locks

The modules of the OmniVista application are validated by the server license file. On the other handthe access to data of the various PCXs requires having appropriate software locks in each PCX:

OmniVista 4760 modules Number of OmniPCX 4400/Enterprise software locksConfiguration 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 - DirectoryTraffic observation 42 - Accounting users (do not forget)

39 - Performance VoIP 42 - Accounting users

Alarms 47 - Alarms

Secured SSH connection toOmniPCX Enterprise

No specific lock for OmniPCX Enterprise. Security license forOmniVista 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 partof the configuration application window.

•

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

8/19/2019 TC1660en

20/74

OmniVista 4760


Ed. 01/ 04-06-2012 20 TC1660

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 2) Windows® 2003 SP1 or 2

Windows® VistaInternet browser Mozilla Firefox 2.0

Internet Explorer version 6 or 7

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 withOmniVista 4760 R5.2. The current version is 1.2.000.020.

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

8/19/2019 TC1660en

21/74

OmniVista 4760


Ed. 01/ 04-06-2012 21 TC1660

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

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 inrequired formats.

An A4715/A4740 -> A4760 carrier migration tool can be used to retrieve the carrier data of thesame tariff area. This tool operates only from version 4_4.14x of Alcatel 4715/A4740. Itsfunctioning is described in the technical communication TCV002 Alcatel 4715/4740 carrier datamigration to OmniVista 4760.

An A4755 -> A4760 carrier migration tool can be used to retrieve the carrier data of the same tariffarea. Its functioning is described in the technical communication TCV017 Carrier data migrationfrom Alcatel 4755 to OmniVista 4760.

8/19/2019 TC1660en

22/74

OmniVista 4760


Ed. 01/ 04-06-2012 22 TC1660

CAUTION

− Each Code book import must be followed by a cost recalculation. It can be scheduled or runmanually. 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 carriername:

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

NoteThe 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 inthe 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 securedcompany 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.

8/19/2019 TC1660en

23/74

OmniVista 4760


Ed. 01/ 04-06-2012 23 TC1660

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 theOn-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 4PREREQUISITES.

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 ,hotfix KB956572 mustOn W2003 ,hotfix KB956572 mustOn W2003 ,hotfix KB956572 mustOn W2003 ,hotfix KB956572 must be removed (freeze TOMCAT installation)be removed (freeze TOMCAT installation)be removed (freeze TOMCAT installation)be removed (freeze TOMCAT installation)and replaced by the KB971812.and replaced by the KB971812.and replaced by the KB971812.and 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 beforeconfirming 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 andfolder

Unset hide protected operating system files.

♦ To set trace mode installation, after copying 4760 software on hard disk, modifyServerSetup.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:

8/19/2019 TC1660en

24/74

OmniVista 4760


Ed. 01/ 04-06-2012 24 TC1660

Document Settings\Administrator\Local Settings\Temp\Omnivista4760_install.log for Server (if XP or Win2003)

Document Settings\Administrator\Local Settings\Temp\Omnivista4760Client_install.log for Client (if 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 underthe 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.02.00.b\Setup\”.

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

Any error management at this level generates the “Insert Disk 1” message wheninstalling or updating.

• Installation

To install or upgrade a remote server using a Terminal Server or RemoteDesktop connection, it is mandatory to start the session as “console “(command mstsc.exe /console (Windows® 2003, Windows® XP SP2) ormstsc.exe /admin (Windows® XP SP3, Windows® Vista)).

Otherwise the operation would fail.

• In the installation fails, contact the Technical Support by providing the OmniVista4760_install.log log.

If an installation fails, refer to the technical communication TC1007 OmniVista 4760Installation / Uninstallation for a possible “manual” uninstallation.

8/19/2019 TC1660en

25/74

OmniVista 4760


Ed. 01/ 04-06-2012 25 TC1660

6.2.1. Mandatory parameters installation

Parameter Type Name values valid if

Company name String Always valid. Special characters areescaped

Destination directory Directory Directory exists, is empty and is not a rootdirectory such as C:\

SunTM DSEE destinationdirectory

Directory Directory exists, is empty and is not a rootdirectory such as C:\

Sybase ASA serverdestination directory Directory Directory exists, is empty and is not a rootdirectory such as C:\Database data destinationdirectory


Server archives destinationdirectory


Hostname and domain (ordns suffix)

FQDN DNS domain existsHostname less or equal to 15 characters

Mail server name or IPaddress

Name or IP address Name can be resolved

Localization country Country name See Table: OmniVista 4760 supported

countriesLocalization language Language name See Table: OmniVista 4760 supported

countries Application administratorlogon

Default: AdminNmc • ASCII characters• Characters not in: ,+”\;#&%|^

Database administratorlogon

Fixed: DBA Characters in ASCII letters and digits and_$#

Password • ASCII characters• Length is at least 8• LDAP constraint: characters not in:

,+”\;#&%|^ and

•

ASA constraint: characters not in!”%&’()*+,-./:;?\^`{|}~ and

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 .

After starting ServerSetup.exe, the system checks if software is already installed bysearching this registry entry:

♦ HKEY_CLASSES_ROOT\Installer\Products\9850FC3C721B51C43A740ECDBC7CE478

8/19/2019 TC1660en

26/74

OmniVista 4760


Ed. 01/ 04-06-2012 26 TC1660

If the hostname has more than 15 characters, the LDAP installation will fail. The limitation to15 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 thespace 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 hasbeen done during installation. The setup will not continue to install if the temp size is lessthan 100 MB. The threshold value is maintained at 100 MB to make sure that it has enoughspace to keep the extracted files from the setup during installation. The estimation iscalculated from the space occupied by the installation files in the %Temp% folder. This spacechecking is only applicable for Server.

3 If the correct Java Runtime Environment (JRE) (1.6.0_11) is not detected, its installation willstart automatically.

4 Indicate the location of the xxyyyzza.sw4760 license file, supplied on diskette or in adirectory 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 OmniVista4760; the upgrade towards a higher version would 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 notchange 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.

8/19/2019 TC1660en

27/74

OmniVista 4760


Ed. 01/ 04-06-2012 27 TC1660

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 filedisplays 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 logwindow displays information about patch installation (log localization: installationrepertory\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 DescriptionDATE 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 portsvPortTomcat TOMCAT portsvServerPort 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 installationprocedure 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.

8/19/2019 TC1660en

28/74

OmniVista 4760


Ed. 01/ 04-06-2012 28 TC1660

• 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 describedbelow.

− When the installation and the configuration are finished, we recommend performing a serverdata 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 ofupgrades.

In the Control Panel, use the standard display (the default display of Windows® XP masks someicons):

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

The complete procedure is described in the Installation Manual.

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

• Client PC end, run:

ping .

ping .

• Server PC end, run:

ping

ping .

If it is not the case, ask the network manager to correct the DNS management or to completehost file (under winnt or Windows®\system32\drivers\etc\) of Client PC and Server PCwith:

IP_Address Host_Name Host_Name.DNS_Suffix_Name

Example: 155.166.123.156 OmniVista OmniVista.alcatel.fr

8/19/2019 TC1660en

29/74

OmniVista 4760


Ed. 01/ 04-06-2012 29 TC1660

Method 1

1 Launch ClientSetup.exe.

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

3 Accept “Alcatel License agreement”.

4 Enter the installation path.

5 Click on Install to start the installation

6666

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


• Click on java,


With a 4760 client installed under Vista, a warning message is displayed. Select the Dont showthis 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 4760server 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 nameand its IP address in intranet sites.

− If a request of proxy authorization occurs during this procedure, you will probably not be able toaccess the application since the network manager does not allow this type of connection.

− The complete procedure is described in the Installation Manual.

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:

♦ Menu Tool/Internet Options/Privacy tab,

8/19/2019 TC1660en

30/74

OmniVista 4760


Ed. 01/ 04-06-2012 30 TC1660

♦ 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 buttonthe authorization for the 4760 server.

• Under Mozilla Firefox 2.0:

♦ Menu Edit/Preferences/Advanced ,

♦ Under Cookies, tick Accept all cookies,

3 Following management will prevent from a language switch after search in the directory. In thiscase the No such object error message is also displayed.

The management described concerns Internet Explorer 6.0. An equivalent management has tobe done for other browsers.

• menu Tool/Internet Options/Privacy tab

• click on Advanced button

• select Override automatic cookie handling, accept option for First-PartyCookies and Third-party Cookies and validate Always allow sessioncookies

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 OmniVista4760 NMS for the first time or from a new server, please install

JRE.

• Click on Open 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.

• Click on Open.

6.6.2.

Checking the installation

If the Java plug-in installation and the initialization with an OmniVista 4760 server occurredcorrectly, 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 /-« {

8/19/2019 TC1660en

31/74

OmniVista 4760


Ed. 01/ 04-06-2012 31 TC1660

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

Example155.166.123.156 OmniVista OmniVista.alcatel

7.

UPGRADESPerform 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 stopNMC 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 thedata and then uninstalls and reinstalls and finally makes an import of the data backup. So duringthe 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 thepath 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 pathE:\Temp\Temp4760\.

During the LDAP database backup the Save_Ldapbasesfiles.ace file will be stored in the pathE:\Temp\Temp4760\. If the Sybase is installed in path drive D: then theSave_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.

8/19/2019 TC1660en

32/74

OmniVista 4760


Ed. 01/ 04-06-2012 32 TC1660

3 Restart NMCService Manager.

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

7.3. Upgrading the OmniVista 4760 server to version R5.2.01.04.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.bR5.1 5.1.04.00.b

R5.1.1 5.1.06.03.cR5.2 5.2.01.03.d

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 thenmc.license file but this does not allow an upgrade of the server. You need to reinstall a newapplication R5.2 or perform an upgrade with an intermediate allowed version.

Procedure for versions before R5.0

• Backup parameters (PCX in System Directory, Logins, 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 theRelease R5.2 (version 12 or 13).

− Perform a database de-fragmentation.

−

Save the application data.− The customizing carried out on the various "themes" offered for Web Client will be saved during

the upgrade in the 4760\(web)client\thèmes directory.

The customizing carried out on the welcome page of Web Client is not saved. If necessary, youshould save the modified data of the 4760\webclient (R4.0) or 4760\client (otherreleases) directory.

− The customizing of the topology is saved during the upgrade. For security, it is possible to firstexport 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 scanmechanism can provide a real installation time gain.

8/19/2019 TC1660en

33/74

OmniVista 4760


Ed. 01/ 04-06-2012 33 TC1660

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 4760Maintenance application.

7.4. Installing a corrective patch

The corrective patches are installed automatically at the end of 4760 server update if they areavailable in the installation CD-ROM.

To manually install a patch copy the correspondent .ace file in the 4760\Install\Patches folderand 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 version 5.2.02.00.b

When a client PC running an earlier version connects to a server in 5.2.02.00.b, the system

proposes an update from this server. This update is running correctly only from a client versionequal or greater than 3.2.05.00.b. For client version less than 3.2.05.00.b, do not accept theupdate procedure otherwise client could not open anymore. Under such circumstance, it is necessaryto 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 adirectory 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 iscarried 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.


• Double click on java,

8/19/2019 TC1660en

34/74

OmniVista 4760


Ed. 01/ 04-06-2012 34 TC1660


8/19/2019 TC1660en

35/74

OmniVista 4760


Ed. 01/ 04-06-2012 35 TC1660

8. OmniPCX OFFICE

Refer to the Technical Communication TCV049 Installation procedure for Release 2.1/3.x forOmniPCX 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/downloadoperations, but also to enter into PCX configuration.

The OmniPCX Office data are saved by default on the 4760 server PC in the directory4760_ARC/OXO/data. This directory is shared as 4760-databases during 4760 installation (or4760-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 instanceafter uninstalling a previous 4760 server) and has a shared name, this name will not be modified by4760 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 bevalidated. 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 permanentpassword.

The software versions to be downloaded to the PCX have to be stored in the directory4760_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 serverand 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.

•

Reboot the PC.

8/19/2019 TC1660en

36/74

OmniVista 4760


Ed. 01/ 04-06-2012 36 TC1660

• Run 4760 client, open Configuration application and launch the "Configure" menu afterselecting an OmniPCX Office: OMC client will be automatically open.

Notes

• The same procedure has to be applied on PC hosting 4760 server to perform OmniPCXOffice maintenance operations.

• Administrative parameters (mandatory customer information) must be configured on eachOmniPCX 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).

8/19/2019 TC1660en

37/74

OmniVista 4760

INSTALLATION PROCEDURE FOR VERSION5.2.02.00.b – RELEASE 5.2

APPENDIX 1CORRECTIONS

Ed. 01 / 06-04-2012 1 TC1660

CORRECTIONS

CONTENTS

Corrections in R5.1

1.1.1.1. ACCOUNTING ACCOUNTING ACCOUNTING ACCOUNTING----PTPPTPPTPPTP----VOIP VOIP VOIP VOIP ............................................................................................................................................................................................................................................3333

2.2.2.2. MAINTENANCEMAINTENANCEMAINTENANCEMAINTENANCE........................................................................................................................................................................................................................................................................................................3333

3.3.3.3. AUDIT AUDIT AUDIT AUDIT ................................................................................................................................................................................................................................................................................................................................................................3333

4.4.4.4. SCHEDULERSCHEDULERSCHEDULERSCHEDULER ............................................................................................................................................................................................................................................................................................................................3333

5.5.5.5. REPORTSREPORTSREPORTSREPORTS ................................................................................................................................................................................................................................................................................................................................................3333

6.6.6.6. CONNECCONNECCONNECCONNECTIVITY TIVITY TIVITY TIVITY........................................................................................................................................................................................................................................................................................................3333

Corrections in R5.1.1


2.2.2.2. AUDIT AUDIT AUDIT AUDIT ................................................................................................................................................................................................................................................................................................................................................................4444

3.3.3.3. A AA ANNUAIRENNUAIRENNUAIRENNUAIRE....................................................................................................................................................................................................................................................................................................................................4444

Corrections in R5.2

1.1.1.1. PROBLEM REPORTS CORRPROBLEM REPORTS CORRPROBLEM REPORTS CORRPROBLEM REPORTS CORRECTEDECTEDECTEDECTED IN R5.2.02.00.BIN R5.2.02.00.BIN R5.2.02.00.BIN R5.2.02.00.B........................................................................................4444

2.2.2.2. PROBLEMPROBLEMPROBLEMPROBLEM REPORTS CORRECTED IREPORTS CORRECTED IREPORTS CORRECTED IREPORTS CORRECTED IN R5.2.01.04.CN R5.2.01.04.CN R5.2.01.04.CN R5.2.01.04.C ........................................................................................5555

3.3.3.3. PROBLEM REPORTS CORRPROBLEM REPORTS CORRPROBLEM REPORTS CORRPROBLEM REPORTS CORRECTEDECTEDECTEDECTED IN R5.2.01.03.DIN R5.2.01.03.DIN R5.2.01.03.DIN R5.2.01.03.D ........................................................................................6666

8/19/2019 TC1660en

38/74

OmniVista 4760



Ed. 01 / 06-04-2012 2 TC1660

8/19/2019 TC1660en

39/74

OmniVista 4760



Ed. 01 / 06-04-2012 3 TC1660

Corrections in R5.1

1.

ACCOUNTING-PTP-VoIP

crms00149205 Not possible to purge 140.000 inactive entries / 1-91409651.

2.

MAINTENANCE

crms00153645 4760 R5.0/ Software download/noautostart not sent for H1 PCX release / 1-92752061.

3. AUDIT

crms00182438 Audit purge not based on actions date / 1-98201027.

4. SCHEDULER

crms00167838 Incorrect PCX config export status in the scheduler (mao off) / 1-95128131.

5. REPORTS

crms00154349 Report: Project code filter not ok-out of range of destination.

6. CONNECTIVITY

crms00169291 PPP Connection fails with OXE in H1. Fixed in H1.301.31.b.

Corrections in R5.1.1

1.

MAINTENANCE

crms00186287 4760 R5.1/software download/context id updated too quickly/1-99095569.

8/19/2019 TC1660en

40/74

OmniVista 4760



Ed. 01 / 06-04-2012 4 TC1660

2. AUDIT

crms00182971 4760 R5.1 Audit/the year is sometimes not correct / 1-9830087.

3. ANNUAIRE

crms00191660 Web client not accessible in German Language.

Corrections in R5.2

1.

Problem reports verified 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 loginattempts

8/19/2019 TC1660en

41/74

OmniVista 4760



Ed. 01 / 06-04-2012 5 TC1660

2. Problems reports corrected in R5.2.01.04.c

8/19/2019 TC1660en

42/74

OmniVista 4760



Ed. 01 / 06-04-2012 6 TC1660

3.

Problem reports verified in R5.2.01.03.d

8/19/2019 TC1660en

43/74

OmniVista 4760



Ed. 01 / 06-04-2012 7 TC1660

8/19/2019 TC1660en

44/74

OmniVista 4760



Ed. 01 / 06-04-2012 8 TC1660

8/19/2019 TC1660en

45/74

OmniVista 4760


APPENDIX 2RECOMMENDATIONS

Ed. 01 / 06-04-2012 1 TC1660

RECOMMENDATIONS

CONTENTS

1.1.1.1. INFRASTRUCTURE / INSINFRASTRUCTURE / INSINFRASTRUCTURE / INSINFRASTRUCTURE / INSTALLATIONTALLATIONTALLATIONTALLATION ............................................................................................................................................................................3333

1.1.1.1.1.1.1.1. TCP ports to be openedTCP ports to be openedTCP ports to be openedTCP ports to be opened ........................................................................................................................................................................................................................................................................................................3333

1.2.1.2.1.2.1.2. Installation of MOXA driver Installation of MOXA driver Installation of MOXA driver Installation of MOXA driver ................................................................................................................................................................................................................................................................................3333

1.3.1.3.1.3.1.3. Use of MOXA equipmentUse of MOXA equipmentUse of MOXA equipmentUse of MOXA equipment ................................................................................................................................................................................................................................................................................................3333

2.2.2.2. SECURITY SECURITY SECURITY SECURITY............................................................................................................................................................................................................................................................................................................................................3333

2.1.2.1.2.1.2.1. PasswordPasswordPasswordPassword ............................................................................................................................................................................................................................................................................................................................................................................................ 3333

2.2.2.2.2.2.2.2. RightsRightsRightsRights....................................................................................................................................................................................................................................................................................................................................................................................................................4444

3.3.3.3.

DIRECTORY DIRECTORY DIRECTORY DIRECTORY ................................................................................................................................................................................................................................................................................................................................4444

3.1.3.1.3.1.3.1. Implementing the photosImplementing the photosImplementing the photosImplementing the photos................................................................................................................................................................................................................................................................................................4444

3.2.3.2.3.2.3.2. Creating the PCXsCreating the PCXsCreating the PCXsCreating the PCXs ........................................................................................................................................................................................................................................................................................................................................4444

4.4.4.4. CONFIGURATIONCONFIGURATIONCONFIGURATIONCONFIGURATION........................................................................................................................................................................................................................................................................................5555

4.1.4.1.4.1.4.1. Changing the PCX connectionChanging the PCX connectionChanging the PCX connectionChanging the PCX connection.................................................................................................................................................................................................................................................................... 5555

4.2.4.2.4.2.4.2. Free users name in the PCXFree users name in the PCXFree users name in the PCXFree users name in the PCX................................................................................................................................................................................................................................................................................5555

5.5.5.5.

ALARMS ALARMS ALARMS ALARMS ....................................................................................................................................................................................................................................................................................................................................................5555

5.1.5.1.5.1.5.1. Alarm supervision Alarm supervision Alarm supervision Alarm supervision ........................................................................................................................................................................................................................................................................................................................................5555

6.6.6.6. TOPOLOGY TOPOLOGY TOPOLOGY TOPOLOGY................................................................................................................................................................................................................................................................................................................................6666

7.7.7.7. ACCOUNTING ACCOUNTING ACCOUNTING ACCOUNTING ............................................................................................................................................................................................................................................................................................................6666

7.1.7.1.7.1.7.1. Accounting: Local currency and referenced currency Accounting: Local currency and referenced currency Accounting: Local currency and referenced currency Accounting: Local currency and referenced currency............................................................................................................................ 6666

7.1.1. Management overview .....................................................................................6

7.1.2.

Installation of country = Default.......................................................................6

7.2.7.2.7.2.7.2. Cost centers different from those of the PCXCost centers different from those of the PCXCost centers different from those of the PCXCost centers different from those of the PCX ............................................................................................................................................................................6666

8/19/2019 TC1660en

46/74

OmniVista 4760


APPENDIX 2RECOMMENDATIONS

Ed. 01 / 06-04-2012 2 TC1660

7.3.7.3.7.3.7.3. Purging the accounting ticketsPurging the accounting ticketsPurging the accounting ticketsPurging the accounting tickets ................................................................................................................................................................................................................................................................ 7777

7.4.7.4.7.4.7.4. Carrier managementCarrier managementCarrier managementCarrier management........................................................................................................................................................................................................................................................................................................................7777

7.4.1. Tariff: Managing the period..............................................................................7

7.4.2. City / Country name: Loss of performance .......................................................7

8.8.8.8. REPORT GENERATORREPORT GENERATORREPORT GENERATORREPORT GENERATOR ....................................................................................................................................................................................................................................................................8888

8.1.8.1.8.1.8.1. Weekly accounting reportWeekly accounting reportWeekly accounting reportWeekly accounting report............................................................................................................................................................................................................................................................................................8888

9.9.9.9.

SCHEDULERSCHEDULERSCHEDULERSCHEDULER ............................................................................................................................................................................................................................................................................................................................8888

9.1.9.1.9.1.9.1. Tasks succession order Tasks succession order Tasks succession order Tasks succession order ............................................................................................................................................................................................................................................................................................................8888


10.1.10.1.10.1.10.1. Rule of partitioningRule of partitioningRule of partitioningRule of partitioning ................................................................................................................................................................................................................................................................................................................................8888

10.2.10.2.10.2.10.2. Backing up the databasesBacking up the databasesBacking up the databasesBacking up the databases......................................................................................................................................................................................................................................................

Date post:	07-Jul-2018
Category:	Documents
Upload:	dhexter-villa
View:	213 times
Download:	0 times