tc1479en_installation procedure for version r5.2.01.03.d

8/19/2019 TC1479en_Installation Procedure for Version R5.2.01.03.d

1/72

1

TECHNICAL COMMUNICATION No. TC1479 Ed. 01

OmniVista 4760 Nb of pages : 72 Date : 19 May 2011

URGENT

NOT URGENT TEMPORARY PERMANENT

SUBJECT : INSTALLATION PROCEDURE FOR VERSION 5.2.01.03.d - RELEASE 5.2

This is a technical release of OmniVista 4760 with the version 5.2.01.03.d.

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

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

described in the installation procedure for version 5.2.01.03.d.

https://businessportal.alcatel-lucent.com/https://businessportal.alcatel-lucent.com/


2/72

2


3/72

OmniVista 4760

INSTALLATION PROCEDURE FOR VERSION5.2.01.03.d - RELEASE 5.2

Ed. 01 / 19 May 2011 3 TC1479

CONTENTS

1.

GENERAL.....................................................................................7

2.

NON STANDARD FEATURES ........................................................8

2.1. Non-operational configuration................................................................. 8

2.2. Features under PCS Premium Customer Support) Complex solutions) .... 8

2.3.

Specific process......................................................................................... 8

3.

CONTENT OF THE SOFTWARE PACKAGE.....................................8

3.1. References ................................................................................................ 8

3.2. Patches ..................................................................................................... 9

3.2.1.

Mandatory patches delivered with the DVD-ROM version.................................9

3.2.2. Optional patches ............................................................................................10

3.3. License file.............................................................................................. 10

4.

PREREQUISITES..........................................................................12

4.1. Server PC prerequisites........................................................................... 12

4.1.1. Hardware and software..................................................................................12

4.1.2. Software and hardware compatibility.............................................................12

4.1.3.

Configuring the Server PC ..............................................................................13

4.2. PCX prerequisites.................................................................................... 13

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

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

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

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

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

4.3. Prerequisites of administration Client PCs............................................... 17

4.4. Prerequisites of Client PCs for directory consultation via WEB................. 17

4.5.

Compatibility with SIP Device Management Server ................................. 17


4/72

OmniVista 4760


TC1479 4 Ed. 01 / 19 May 2011

5.

DATA COLLECTION OF THE SERVER ..........................................18

5.1. List of data to be collected ...................................................................... 18

5.2. Company directory ................................................................................. 18

5.3. Carrier configuration.............................................................................. 18

5.4.

Security................................................................................................... 19

5.5. Backup mode.......................................................................................... 19

6.

INSTALLATION ..........................................................................20

6.1. Additional installation of an integrated PC in factory.............................. 20

6.2. Standard server installation procedure ................................................... 20

6.2.1. Mandatory parameters installation.................................................................22

6.2.2. Restorecontext.ini file......................................................................................24

6.3. Patches delivered within a version.......................................................... 24

6.4.

Server post-installation........................................................................... 25

6.5. Client installation procedure................................................................... 25

6.6. Accessing OmniVista 4760 via a browser ............................................... 26

6.6.1. Installation......................................................................................................26

6.6.2. Checking the installation ................................................................................27

7. UPGRADES ................................................................................28

7.1. Prerequisites ........................................................................................... 28

7.2. License file update.................................................................................. 28

7.3. Upgrading the OmniVista 4760 server to version R5.2.01.03.d .............. 29

7.4. Installing a corrective patch .................................................................... 30

7.5.

Upgrading the OmniVista 4760 client to version 5.2.01.03.d ................. 30

7.5.1. Installing the patch .........................................................................................30

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

8. OMNIPCX OFFICE......................................................................31

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

8.2.

OMC....................................................................................................... 31

9.

ALCATEL-LUCENT OFFICE 4200) ..............................................32


5/72

OmniVista 4760


Ed. 01 / 19 May 2011 5 TC1479

APPENDIX

APPENDIX 1 – CORRECTIONS

APPENDIX 2 – RECOMMENDATIONS

APPENDIX 3 – ADVANCED MANAGEMENT

APPENDIX 4 – NEW FEATURES

APPENDIX 5 – IDENTIFIED DEFAULTS AND RESTRICTIONS


6/72

OmniVista 4760


TC1479 6 Ed. 01 / 19 May 2011


7/72

OmniVista 4760


Ed. 01 / 19 May 2011 7 TC1479

1. GENERAL

This document describes the installation procedure for OmniVista 4760 version 5.2.01.03.d.

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.businesspartner.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] or

33 (0)2 98 14 30 40).

http://www.businesspartner.alcatel-lucent.com/mailto:[email protected]:[email protected]://www.businesspartner.alcatel-lucent.com/


8/72

OmniVista 4760


TC1479 8 Ed. 01 / 19 May 2011

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

− LDAP replication.

2.3. Specific process

− Proxy SNMP / Spectrum, HPOV integration (Restrictions: not available on Windows 2008 and Windows 7).

− 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 AKAA which contains following items:

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

♦ Version Release R5.2.01.03.d

♦ 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 AKAA 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


9/72

OmniVista 4760


Ed. 01 / 19 May 2011 9 TC1479

3.2. Patches

3.2.1. Mandatory patches delivered with the DVD-ROM version

Under \Patches\Mandatory folder you will find:

Files Fixed Anomaly Reports4760-520103_PatchA_Dll.ace crms00242587

4760 R5.1/missing compression algorithms for VoIP/1-109455157 - Loader Changes

4760-520103_PatchC_Dll.ace crms002849164760 R5.2 compliancy with OXE R9.1: still NGPboard missing in VoIP ticket equipment

4760-520103_PatchD_Dll.ace crms00288431 Arbitrary code execution in admin software

4760-520103_PatchE_NotifyPlugin.ace crms00267068LDAP is not stopping properly sometimes

4760-520103_PatchF_jar.ace crms00291210Issue when importing ldif file. If an entry have apassword it’s impossible to import it in the companydirectory

4760-520103_PatchG_css.ace crms00291707 After internal upgrade (from R5.2.01.02.b toR5.2.01.03.d) style’s themes changes

4760-520103_PatchH_conf.ace crms00291138If entry have a . (ex: 01.PRESIDENT) it’s impossible toconsult in detail mode this entry with web directory

4760-520103_PatchI_jar.ace crms00309808 When importing department entries in companydirectory the department is not created.

4760-520103_PatchJ_AutoUpgrade.ace crms003115244760 5.2.01.01.b: 4760client 5.1upgrade issue

4760-520103_PatchK_Dll.ace crms00307073Issue when moving entries in company directory

4760-520103_PatchL_Dll.ace crms00311859Crash LDAP

4760-520103_PatchM_ldif.ace crms00296906Same uid issue

4760-520103_PatchN_directory.ace crms00312161 Web directory is not properly opened while apacheuses other than port 80

4760-520103_PatchO_Dll.ace crms00295525LDAP error when importing ldif files (Ldap Server

unavailable)

Reminder


10/72

OmniVista 4760


TC1479 10 Ed. 01 / 19 May 2011

On server side, all patches are automatically installed at the end of the installation.

3.2.2. Optional patches

Some patches, specific to rarely used applications can be available on the DVD-ROM,Tools\Optional Patches folder.

setup_patch.exe patch fixes inopportune stops of nmc50 database service.

Following information is generated in Windows events:

03/ 11/ 2009- - 1: 57: 27- - SQLANY - - ASANYs_nmc50: ** * ERROR ** * Asser t i onf ai l ed: 201501 ( 10. 0. 1. 3764) .

Page f or r equest ed r ecor d not a t abl e page or r ecor d not pr esent on page.

This problem exists in 5.0.07.02.b and 5.1.04.00.b versions (version Sybase 10.0.1 build 3764)when using the Past Time Performance feature.

The upgrade of these versions does not fix the issue.

The patch can be installed in version specified above and in 5.2.01.03.d if the Sybase version is10.0.1.3764 after an upgrade.

Refer to the section 7 Upgrades for the installation procedure.

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

End 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


11/72

OmniVista 4760


Ed. 01 / 19 May 2011 11 TC1479

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


12/72

OmniVista 4760


TC1479 12 Ed. 01 / 19 May 2011

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

PC Pack 4 Server Pack 3-2 Server Pack 3-3

HP COMPACT 6000 Pro HP DL 380 G6 HP DL 380 G5RAM 2Go

HD 250Go (1x250Go)

RAM 6GB - HD 438Go (3x146Go)

Mono Processor

RAM 2Go - HD 216Go (3x72Go)

Bi Processor

OmniV ista 4760 - Client XP Pro / Win 7-64 bits

Win 7-64 bits 2008 R2 Server

Win 7-32 bits

Win 7-64 bits

Win 7-64 bits

Win 7-64 bits

2008 R2 Server

Win 7-64 bits

2008 R2 Server

2008 R2 Server

2008 R2 Server

Win 7-64 bits

Genesys Compact Edition - Visual CC XP Pro / Win 7-64 bits TFT 19"

Genesys Compact Edition - Outbound 2003 Server TFT 19"

Genesys Compact Edition - Server 2003 Server / 2008 R1 Server TFT 19"

TFT 19"

OmniV ista 4760 - Server XP Pro / 2003 Server / TFT 19"

4059 IP XP Pro / TFT 19"

OmniTouch CC Standard - CCS Light XP Pro / TFT 19"

OmniTouch CC Standard - CCS Monosite XP Pro / TFT 19"

OmniTouch CC Standard - CCS Multisite XP Pro / TFT 19"

OmniTouch CC Standard - CCS Server 2003 Server / TFT 19"

OmniTouch CC Standard - ACR Server XP Pro / TFT 19"

OmniTouch CC Standard - CCA 2003 Server / TFT 19"

OmniTouch CC Standard - CCO 2003 Server TFT 19"

OmniTouch CC - CCivr Master Server 2003 Server / TFT 19"

OmniTouch CC - CCivr Easy Server 2003 Server / TFT 19"

OmniTouch CC - CCivr Client XP Pro / TFT 19"

OmniTouch CC Premium - Visual CC XP Pro TFT 19"

OmniTouch CC Premium - Outbound 2003 Server TFT 19"

OmniTouch CC Premium - Server 2003 Server TFT 19"

OmniTouch 8400 Instant Communications Suite Linux Linux TFT 19"

OmniTouch 8410 Instant Communications Web Services Linux TFT 19"

OmniTouch 8440 Messaging Sof tw are Linux TFT 19"

OmniTouch 8450 Fax Sof tw are Linux Linux TFT 19"

OmniTouch 8660 My Teamw ork Conf . and Collaboration Linux Linux TFT 19"

OmniTouch 8670 Automated Message Delivery System Linux Linux TFT 19"

OmniTouch 8464 Meet-me Audio Conferencing Bridge Linux TFT 19"

OmniTouch 8460 Advanced Communications Server BP provided server BP provided server

APPLICATIONS Scr een

NotesFrom 30000 subscribers, you need the agreement of Alcatel-Lucent (process PCS – PremiumCustomer Support).From 800 nodes or PCS, you need the agreement of Alcatel-Lucent (process PCS – Premium Customer Support).

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 must supportother applications, you should analyze the compatibility, estimate the performance requirements ofother applications and strictly follow the installation/uninstallation procedure. Moreover, theoperation 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.


13/72

OmniVista 4760


Ed. 01 / 19 May 2011 13 TC1479

4.1.3. Configuring the Server PC

The space disk requirements and the rules of disks partitioning are described in the Installationmanual.

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

− An other JAVA application can use the Classpath environment variable. In that case, the line ofparameters 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 willreceive 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). 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 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 notavailable in OmniPCX 4400 Release 3.0).


14/72

OmniVista 4760


TC1479 14 Ed. 01 / 19 May 2011

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 Yes

1.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 No

2.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 No

3.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 Yes

4.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.27.d 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 with tunnel address must be in version F4.401.7, F2.502.14, F3.301.36(or greater) so that LDAP/PCX synchronization runs properly (XTSce69071).

• OmniPCX Enterprise whose hostname length greater than 16 characters must be in versionF3.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.


15/72

OmniVista 4760


Ed. 01 / 19 May 2011 15 TC1479

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 Yes

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

(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 MultitechISDN 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 Yes

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


16/72

OmniVista 4760


TC1479 16 Ed. 01 / 19 May 2011

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 to have appropriate software locks in each PCX:

OmniVista 4760 modules Number of OmniPCX 4400/Enterprise software locks

Configuration 13 – ECS Engine50 - 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 a 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).


17/72

OmniVista 4760


Ed. 01 / 19 May 2011 17 TC1479

4.3. Prerequisites of administration Client PCs

HARDWARE AND SOFTWARE (Minimum)

PC Pack 4 Server Pack 3-2 Server Pack 3-3

HP COMPACT 6000 Pro HP DL 380 G6 HP DL 380 G5

RAM 2Go

HD 250Go (1x250Go)

RAM 6GB - HD 438Go (3x146Go)

Mono Processor

RAM 2Go - HD 216Go (3x72Go)

Bi Processor

OmniV ista 4760 - Client XP Pro /

APPLICATIONS Scr een

Win 7-64 bits

Win 7-64 bits 2008 R2 Server

TFT 19"

OmniV ista 4760 - Server XP Pro / 2003 Server / TFT 19"

i i

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 Vista

Internet browser Mozilla Firefox 2.0Internet Explorer version 6 or 7

4.5. Compatibility with SIP Device Management ServerSIP 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 DMS is not compatible with Windows 2008 and Windows 7.


18/72

OmniVista 4760


TC1479 18 Ed. 01 / 19 May 2011

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.


19/72

OmniVista 4760


Ed. 01 / 19 May 2011 19 TC1479

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


20/72

OmniVista 4760


TC1479 20 Ed. 01 / 19 May 2011

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 4

PREREQUISITES.

The installation fails if the operating system is not running in SP1 at least.Refre to technical communication TC1007-Ed02 OmniVista 4760 Installation /Uninstallation chapter 6.14.

− It is recommended to stop all Antivirus program. 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/

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:

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)


21/72

OmniVista 4760


Ed. 01 / 19 May 2011 21 TC1479

♦ 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.01.03.d\Setup\".

Then the version must be burnt under the 4760_R5.2.01.03.d 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 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)).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.


22/72


23/72

OmniVista 4760


Ed. 01 / 19 May 2011 23 TC1479

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 and HTTP ports are standardized. Do not change themunless 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 thecurrency (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.


24/72

OmniVista 4760


TC1479 24 Ed. 01 / 19 May 2011

♦ 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 performedinstallations 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 fileThis 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 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 .


25/72

OmniVista 4760


Ed. 01 / 19 May 2011 25 TC1479

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 complete

host 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


26/72

OmniVista 4760


TC1479 26 Ed. 01 / 19 May 2011

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

6

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

− 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,

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

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


27/72

OmniVista 4760


Ed. 01 / 19 May 2011 27 TC1479

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

gr ant codeBase "ht t p: / / Omni Vi st a. al cat el . f r / - " {

per mi ssi on j ava. secur i t y. Al l Per mi ssi on;

};

gr ant codeBase "ht t p: / / Omni Vi st a / - " {

per mi ssi on j ava. secur i t y. Al l Per mi ssi on;


28/72

OmniVista 4760


TC1479 28 Ed. 01 / 19 May 2011

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 Omni Vi st a Omni Vi st a. al cat el

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 stopNMC Services.

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

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 the pathgiven 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 typexxyyyzza.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.


29/72

OmniVista 4760


Ed. 01 / 19 May 2011 29 TC1479

7.3. Upgrading the OmniVista 4760 server to version R5.2.01.03.d

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

Releases VersionsR5.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.c

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 duringthe 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, you

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

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.


30/72

OmniVista 4760


TC1479 30 Ed. 01 / 19 May 2011

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.01.03.d

When a client PC running an earlier version connects to a server in 5.2.01.03.d, the systemproposes an update from this server. This update is running correctly only from a client version equalor greater than 3.2.05.00.b. For client version less than 3.2.05.00.b, do not accept the updateprocedure otherwise client could not open anymore. Under such circumstance, it is necessary touninstall 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 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.


• Double click on java,



31/72

OmniVista 4760


Ed. 01 / 19 May 2011 31 TC1479

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, Windowsdirectory 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

• Reboot the PC.

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


32/72

OmniVista 4760


TC1479 32 Ed. 01 / 19 May 2011

Notes

• The same procedure has to be applied on PC hosting 4760 server to perform OmniPCX Officemaintenance 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).


33/72

OmniVista 4760

INSTALLATION PROCEDURE FOR VERSION

5.2.01.03.d – RELEASE 5.2 APPENDIX 1

CORRECTIONS

Ed. 01 / 19 May 2011 1 TC1479

CORRECTIONS

CONTENTS

Corrections in R5.1

1. ACCOUNTING PTP VOIP .............................................................3

2.

MAINTENANCE ...........................................................................3

3. AUDIT..........................................................................................3

4. SCHEDULER.................................................................................3

5.

REPORTS......................................................................................3

6. CONNECTIVITY ...........................................................................3

Corrections in R5.1.1

1.

MAINTENANCE ...........................................................................3

2. AUDIT..........................................................................................4

3.

ANNUAIRE ..................................................................................4

Corrections in R5.2

1. DIRECTORY..................................................................................4


34/72

OmniVista 4760

APPENDIX 1

CORRECTIONS


5.2.01.03.d – RELEASE 5.2

TC1479 2 Ed. 01 / 19 May 2011


35/72

OmniVista 4760


5.2.01.03.d – RELEASE 5.2 APPENDIX 1

CORRECTIONS

Ed. 01 / 19 May 2011 3 TC1479

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.


36/72


37/72

OmniVista 4760


APPENDIX 2RECOMMENDATIONS

Ed. 01 / 19 May 2011 1 TC1479

RECOMMENDATIONS

CONTENTS

1 INFRASTRUCTURE / INSTALLATION 3

1 1 TCP ports to be opened 3

1 2 Installation of MOXA driver 3

1 3 Use of MOXA equipment 3

2 SECURITY 3

2 1 Password 3

2 2 Rights 4

3 DIRECTORY 4

3 1 Implementing the photos 4

3 2 Creating the PCXs 4

4 CONFIGURATION 4

4 1 Changing the PCX connection 4

4 2 Free users name in the PCX 5

5 ALARMS 5

5 1 Alarm supervision 5

6 TOPOLOGY 5

7 ACCOUNTING 6

7 1 Accounting: Local currency and referenced currency 6

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

7.1.2.

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

7 2 Cost centers different from those of the PCX 6


38/72

OmniVista 4760



TC1479 2 Ed. 01 / 19 May 2011

7 3 Purging the accounting tickets 7

7 4 Carrier management 7

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

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

8 REPORT GENERATOR 8

8 1 Weekly accounting report 8

9 SCHEDULER 8

9 1 Tasks succession order 8

10 MAINTENANCE 8

10 1 Rule of partitioning 8

10 2 Backing up the databases 8

10 3 Backing up the OmniVista 4760 database 8

10 4 Defragmentation of the OmniVista 4760 database 9

10 5 Backing up / Restoring OmniPCX 4400/Enterprise 9

10.5.1. Backup ..........................................................................................................9

10.5.2. Restore ..........................................................................................................9


39/72

OmniVista 4760



Ed. 01 / 19 May 2011 3 TC1479

1. INFRASTRUCTURE / INSTALLATION

1.1. TCP ports to be opened

Refer to Installation Manual.

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.

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.

2. SECURITY

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

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


40/72

OmniVista 4760



TC1479 4 Ed. 01 / 19 May 2011

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 advancedmanagement of the SunTM DSEE.

Do not use AdminNMC, after installation for standard management of OmniVista 4760. Createother administrator or manager accounts in order to retain the preferences of the variousadministrators and managers and always keep a supervisor account even if the password is lost.

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

3.

DIRECTORY

3.1. Implementing the photos

Be careful to disk space needed if you inserting photos in the directory: a 20 KB jpg format phototakes 70 KB in LDAP (10 000 photos => 700 MB in LDAP base).

3.2. Creating the PCXs

When creating the PCX, you must specify the number of network node. On network 0 node 1, youmust not enter 001 but directly 1 otherwise the Past Time Performance files loading in database nolonger works.

Avoid the used of . (dot) in the name of the Network, Sub-Network and PCX (In some cases it couldbe a problem during restoration of archives accounting tickets)

Example to avoid: Name of PCX : Brest.Alcatel

4. CONFIGURATION

4.1. Changing the PCX connection

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


41/72

OmniVista 4760



Ed. 01 / 19 May 2011 5 TC1479

− 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 ifnecessary reactivate the alarm processing.

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 notvalidate the Call by name function.

These extensions ‘s successive allocations / unallocations lead to a lot of inactive sets creation intothe accounting organization.

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

5. ALARMS

5.1. Alarm supervision

If a PCX has to centralize all the network alarms and events, you must correctly manage the nodessupervised 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 whichdamage 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 stillunknown in 4760. Do not check the box Alarm Review on the PCX monitored otherwise the alarmswill 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 namesbeing restricted to 16, it is recommended to suppress previous names in the PCX. If a PCX is not ableto create an "Events Routing discriminator" the alarms are not sent to the corresponding server.

6. TOPOLOGY

When the OmniVista 4760 manages a complex PCX network including a lot of inter-nodes links, thetopology display delay can be very long. According to the configuration type, following two solutionsdecreases 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


42/72

OmniVista 4760



TC1479 6 Ed. 01 / 19 May 2011

− a script allows to suppress the display ot the inter-node links to reduce the display delay of thenetwork. 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 anautomatic 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.

7. ACCOUNTING

7.1. Accounting: Local currency and referenced currency

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

− Predefined reports are generated in the referenced currency only.

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.

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 todissociate the PCX cost centers from the OmniVista ones, you must manage them in the OmniVistaapplication. 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.


43/72

OmniVista 4760



Ed. 01 / 19 May 2011 7 TC1479

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

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 accountingdata (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.

7.4. Carrier management

7.4.1.

Tariff: Managing the period

− During management of tariffs, period, only the start time is managed, the applicationautomatically manages the end time.

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

7.4.2.

City / Country name: Loss of performanceDuring normal use, the number of Town / Country must be reduced. This information is in fact usedto identify in the reports the telephone directions frequently used; for example, to identify thesubsidiaries 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 systemslows 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.

ExampleCity country Name Region Paris Prefix 0170

Paris 0170 Prefix 0171Paris 0171 Prefix 0172Paris 0172

In this example, for the Cities/Countries, the Paris entry appears 3 times whereas by using theregions and directions, the Paris entry appears only once.


44/72

OmniVista 4760



TC1479 8 Ed. 01 / 19 May 2011

8. REPORT GENERATOR

8.1. Weekly accounting report

CAUTIONThe week defined in the report application does not begin on Monday but Sunday at 00h00 AM andfinishes on Saturday at 11h59 PM.

9. SCHEDULER

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 savingoperation needs the all services stopping. This may have important bad consequences onsynchronization, tickets loading and cleaning operations.

10. MAINTENANCE

10.1.

Rule of partitioningIt is recommended to have only one partition per physical disk and to separate the partition systemfrom the application. In effect, if a partition seems to be too small, it is impossible to extend itwithout 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 outupgrades, defragmentation data backups. In effect, each of these operations requires for theirworking space near the twice Sybase size therefore depending on the cases up to 40 GB.

10.2. Backing up the databases

In case you need to re-install the application, it is possible to use some managed parameters of theexisting OmniVista 4760. To ensure you have as much information as possible on installation, youmust schedule:

− the company directory LDIFF export,

− the PCX network LDIFF export,

− the carrier Code book export.

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 isplanned to impose a memory release under Windows.

The backup stops the services (the server is not available) and compresses the databases in zipformat. To carry out the backup, you must have twice as much space free as the total size of all thedatabases.


45/72

OmniVista 4760



Ed. 01 / 19 May 2011 9 TC1479

You must schedule a backup at least once a week of the OmniVista 4760 data and purge thesebackups 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, RetrospectiveCost Calculation on the complete database, etc.).

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.

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

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

10.5. Backing up / Restoring OmniPCX 4400/Enterprise

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.

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 thecopy if this local directory (\usr4\BACKUP\IMMED ) already contains a backup.

2 Use swinst to restore this backup.


46/72

OmniVista 4760



TC1479 10 Ed. 01 / 19 May 2011


47/72

OmniVista 4760


APPENDIX 3 ADVANCED MANAGEMENT

Ed. 01 / 19 May 2011 1 TC1479

ADVANCED MANAGEMENT

CONTENTS

1.

INFRASTRUCTURE / INSTALLATION.............................................3

1.1. Reinstalling the server .............................................................................. 3

1.2. Change the IP address.............................................................................. 4

1.2.1. Change procedure............................................................................................4

1.2.2. Add a new IP address.......................................................................................4

1.3. Change the PC name or the Windows DNS suffix ..................................... 4

1.4. Change the passwords ............................................................................. 4

1.5. Re assignation of accounting tickets to active entities ............................... 4

2. DIRECTORY..................................................................................5

2.1. Access the OmniVista 4760 directory through Alcatel 4059...................... 5

2.2. Customize the WEB consultation............................................................... 5

2.2.1. Available options..............................................................................................5

2.3.

Customizing the directory field names...................................................... 5

3.

ALARMS TOPOLOGY .................................................................6

3.1.

E mail server ............................................................................................ 6

4. REPORT GENERATOR...................................................................6

4.1. Schedule a report export........................................................................... 6

4.1.1. Restriction.........................................................................................................6

4.1.2. Procedure .........................................................................................................6

4.2. Export to PDF format with specific characters to languages....................... 7

4.3. Change of paper format for printing the reports....................................... 7

5.

MAINTENANCE ...........................................................................8

5.1.

Backup on a remote host .......................................................................... 8


48/72

OmniVista 4760



TC1479 2 Ed. 01 / 19 May 2011

5.1.1. Restriction.........................................................................................................8

5.1.2. Procedure in a domain .....................................................................................8

5.1.3. Procedure in a Workgroup ...............................................................................8

6. CONFIGURATION .......................................................................9

6.1. Simple Configuration Profile..................................................................... 9


49/72

OmniVista 4760



Ed. 01 / 19 May 2011 3 TC1479

1. INFRASTRUCTURE / INSTALLATION

1.1. Reinstalling the server

To reinstall the OmniVista 4760 server application with an empty database on a PC whereOmniVista has already been installed, you must first uninstall the application. The server modulemust 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 manufacturerservices 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 Studio 9 software will also be removed.

Note

The Java Runtime Environment is not uninstalled.

− Restart the computer to complete the uninstallation procedure.

CAUTIONIf 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 thePC 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 systembackup for a possible restore later.

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

Server

and SQL Anywhere Studio 9 – Software).• Remove the Windows\system32\productregistry file.

The presence of this file may prevent the re-installation of Sun One LDAP server on the samepath 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, Netscape, SQL database.


50/72

OmniVista 4760



T