TC1479en - Installation Procedure For Version R5.2.01.03.d

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 DVDROM 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.
OmniVista 4760
INSTALLATION PROCEDURE FOR VERSION
5.2.01.03.d - RELEASE 5.2
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.
4.
License file.............................................................................................. 10
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
Ed. 01 / 19 May 2011
TC1479
OmniVista 4760
5.2.01.03.d - RELEASE 5.2
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.
TC1479
ALCATEL-LUCENT OFFICE (4200) ..............................................32

4
Ed. 01 / 19 May 2011
OmniVista 4760
5.2.01.03.d - RELEASE 5.2
APPENDIX
APPENDIX 1 CORRECTIONS
APPENDIX 2 RECOMMENDATIONS
APPENDIX 3 ADVANCED MANAGEMENT
APPENDIX 4 NEW FEATURES
APPENDIX 5 IDENTIFIED DEFAULTS AND RESTRICTIONS
Ed. 01 / 19 May 2011
TC1479
OmniVista 4760
5.2.01.03.d - RELEASE 5.2
TC1479
Ed. 01 / 19 May 2011
OmniVista 4760
5.2.01.03.d - RELEASE 5.2
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 this
product.
SIP Device Management Server must have the version 1.2.000.010 or higher to be
compatible with OmniVista 4760 R5.2. The current version is 1.2.000.020.
SIP DMS is not compatible with Windows 2008 and Windows 7
It is also highly recommended to consult on "Alcatel-Lucent Business Portal"
(http://www.businesspartner.alcatel-lucent.com/) ; software downloading and technical
communications can contain new information regarding OmniVista 4760 Release 5.2.
Refer to appendixes to respect the recommendations of installation and management.
The following Technical Communications are essential for the OmniVista 4760 maintenance:
TG0029 Trouble shooting Guide
TG0033 OmniPCX Enterprise Interworking
TCV020 Emails sending by OmniVista 4760
TCV039 License management
TCV060 Directory Management
TCV061 Alarms filtering from OmniPCX Enterprise to OmniVista 4760
TC0835 Disks and memory management
TC0846 Accounting: Investigation elements
TC0858 Traffic observation: Investigation elements
TC0953 OmniVista 4760 license on OmniPCX Office: Max users reached, client in deprecated
mode
TC1007-Ed02 OmniVista 4760 Installation / Uninstallation
CAUTION
Each time you are requested to erase or edit a file, it is absolutely necessary to make a copy of the
original.
These operations must be performed by an expert (ACSE) trained on the product. In the opposite
side, you can contact the "Professional Services" (mailto:professional.services@alcatel-lucent.com or
33 (0)2 98 14 30 40).
Ed. 01 / 19 May 2011
TC1479
OmniVista 4760
5.2.01.03.d - RELEASE 5.2
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
TC1479
Ed. 01 / 19 May 2011
OmniVista 4760
5.2.01.03.d - RELEASE 5.2
3.2.
Patches
3.2.1. Mandatory patches delivered with the DVD-ROM version

Under \Patches\Mandatory folder you will find:
Files
4760-520103_PatchA_Dll.ace
4760-520103_PatchC_Dll.ace
4760-520103_PatchD_Dll.ace
4760-520103_PatchE_NotifyPlugin.ace
4760-520103_PatchF_jar.ace
4760-520103_PatchG_css.ace
4760-520103_PatchH_conf.ace
4760-520103_PatchI_jar.ace
4760-520103_PatchJ_AutoUpgrade.ace
4760-520103_PatchK_Dll.ace
4760-520103_PatchL_Dll.ace
4760-520103_PatchM_ldif.ace
4760-520103_PatchN_directory.ace
4760-520103_PatchO_Dll.ace
Fixed Anomaly Reports

crms00242587
4760 R5.1/missing compression algorithms for
VoIP/1-109455157 - Loader Changes
crms00284916
4760 R5.2 compliancy with OXE R9.1: still NGP
board missing in VoIP ticket equipment
crms00288431
Arbitrary code execution in admin software
crms00267068
LDAP is not stopping properly sometimes
crms00291210
Issue when importing ldif file. If an entry have a
password its impossible to import it in the company
directory
crms00291707
After internal upgrade (from R5.2.01.02.b to
R5.2.01.03.d) styles themes changes
crms00291138
If entry have a . (ex: 01.PRESIDENT) its impossible to
consult in detail mode this entry with web directory
crms00309808
When importing department entries in company
directory the department is not created.
crms00311524
4760 5.2.01.01.b: 4760client 5.1upgrade issue
crms00307073
Issue when moving entries in company directory
crms00311859
Crash LDAP
crms00296906
Same uid issue
crms00312161
Web directory is not properly opened while apache
uses other than port 80
crms00295525
LDAP error when importing ldif files (Ldap Server
unavailable)
Reminder
Ed. 01 / 19 May 2011
TC1479
OmniVista 4760
5.2.01.03.d - RELEASE 5.2
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 *** Assertion
failed: 201501 (10.0.1.3764).
Page for requested record not a table page or record not present 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 is
10.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 file
for your PCX network and which describes the available modules.
In Actis, choose one PCX in the network and specify in its configuration that it is the declaration
node for OmniVista 4760 server.
CAUTION
If the declaration node is OmniPCX 4400 R5.0 Ux, you can no more get the OmniVista
4760 license file.
If the declaration node is OmniPCX Office, OmniPCX Enterprise R5.0 Lx, the license file is
produced on BPWS/ELP.
Correspondence between license version and OmniVista release:

License
10
11
12
13
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
4760
TC1479
10
Ed. 01 / 19 May 2011
OmniVista 4760
5.2.01.03.d - RELEASE 5.2
OmniVista 4760 R5.2 accepts licenses versions 12 and 13.

Versions of embedded software:
InstallShield
JRE
2008
1.6.0.21
Ed. 01 / 19 May 2011
SunTM Directory
Service Enterprise
Edition
DSEE 7.0
11
Sybase
Apache
PHP
SQL Anywhere 10
10.0.1.4157
2.2.16.0
5.2.14.14
TC1479
OmniVista 4760
5.2.01.03.d - RELEASE 5.2
4.
PREREQUISITES
This section describes the prerequisites required to install OmniVista 4760 server and client
applications.
4.1.
Server PC prerequisites
4.1.1. Hardware and software
A PPLICA TIONS
OmniV ista 4760 - Client

OmniV ista 4760 - Server
PC Pa ck 4
Se rve r Pa ck 3-2
Se rve r Pa ck 3-3
HP COMPA CT 6000 Pro

RA M 2Go
HD 250Go (1x250Go)
XP Pro / Win 7-64 bits
HP DL 380 G6
RA M 6GB - HD 438Go (3x146Go)
Mono Processor
HP DL 380 G5
RA M 2Go - HD 216Go (3x72Go)
Bi Processor
2003 Server / 2008 R2 Server
Screen
TFT 19"
TFT 19"
4059 IP
TFT 19"
OmniTouch CC Standard - CCS Light
TFT 19"
OmniTouch CC Standard - CCS Monosite
TFT 19"
OmniTouch CC Standard - CCS Multisite
TFT 19"
OmniTouch CC Standard - CCS Server

OmniTouch CC Standard - A CR Server
TFT 19"
TFT 19"
TFT 19"
OmniTouch CC Standard - CCA

OmniTouch CC Standard - CCO
2003 Server
TFT 19"
OmniTouch CC - CCivr Master Server
TFT 19"
OmniTouch CC - CCivr Easy Server
OmniTouch CC - CCivr Client

OmniTouch CC Premium - V isual CC
TFT 19"
XP Pro
TFT 19"
OmniTouch CC Premium - Outbound

OmniTouch CC Premium - Server
Genesys Compact Edition - V isual CC
TFT 19"

2003 Server
TFT 19"
2003 Server
TFT 19"
2003 Server
TFT 19"
TFT 19"
Genesys Compact Edition - Outbound

Genesys Compact Edition - Server
TFT 19"
OmniTouch 8400 Instant Communications Suite
Linux
OmniTouch 8410 Instant Communications Web Services
Linux
OmniTouch 8440 Messaging Sof tw are
Linux
OmniTouch 8450 Fax Sof tw are
Linux
Linux
TFT 19"
OmniTouch 8660 My Teamw ork Conf . and Collaboration
Linux
Linux
TFT 19"
OmniTouch 8670 A utomated Message Delivery System
Linux
Linux
OmniTouch 8464 Meet-me A udio Conf erencing Bridge
Linux
OmniTouch 8460 A dvanced Communications Server
BP provided server
Linux
TFT 19"
TFT 19"
TFT 19"
TFT 19"
TFT 19"
BP provided server
Notes
From 30000 subscribers, you need the agreement of Alcatel-Lucent (process PCS Premium
Customer 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 correct
operation of the software. If the number of users is lower than 250 and if the Server PC must support
other applications, you should analyze the compatibility, estimate the performance requirements of
other applications and strictly follow the installation/uninstallation procedure. Moreover, the
operation of these other external applications is not supported.
The Security Guide provides a description of parameters to take into account to study compatibility
between an external application and OmniVista 4760 server.
TC1479
12
Ed. 01 / 19 May 2011
OmniVista 4760
5.2.01.03.d - RELEASE 5.2
4.1.3. Configuring the Server PC

The space disk requirements and the rules of disks partitioning are described in the Installation
manual.
Here are the essential points.
Hard disk.
A NTFS partition must be set for installing the SunTM DSEE Server. When installing the server, it is
better to keep the defaults directories and to change only the physical drives.
RAM.
Check that the virtual memory is correctly set, the size of the maximum virtual memory must be
twice the physical RAM. Moreover the disk using the exchange file must have enough free space.
Refer to the technical communication TC0835 Managing the disk and RAM in Release 4.1.
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.
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:\windows
C:\winnt\system32 or
;
C:\windows\system32
The name of the computer must not have the following characters ., -, + (dot, dash, plus). You
make sure that the "NetBios name of the computer" is the same as the "name of the computer".
To read the "NetBios name of the computer", click on the button Other from modification
window of the name of the computer.
For the first OmniVista 4760 server installation on a new PC, this one has to be connected to the
IP network. Otherwise the installation would fail during the SunTM DSEE server installation. The
message in the log file is:
com.iplanet.install.svrutil.wbSvrutil::getHostName:
can't
determine
host name: java.net.UnknownHostException:
4.2.
PCX prerequisites
The compatible OmniPCX 4400 releases depend on the type of PCX Server connection.
The problems related to phase out PCX releases are not fixed (example: the hang-up via STAP is not
available in OmniPCX 4400 Release 3.0).
Ed. 01 / 19 May 2011
13
TC1479
OmniVista 4760
5.2.01.03.d - RELEASE 5.2
4.2.1. IP, IP/X25, PPP connections to OmniPCX 4400/Enterprise

Release
4760
1.5
1.5
1.5
1.5
1.5
1.5
2.0
2.0
2.0
2.1
2.1
2.1
3.0
3.0
3.1
3.1
3.2
4.0
4.1
4.2
4.2
5.0
5.1
5.1.1
Release
PCX
3.0
3.2M
3.2 C2
4.1
4.1.1
4.2.1
5.0 Ux
5.0.1 Ux
5.0 Lx
5.1
5.1.1
5.1.2
6.0
6.0.1
6.1
6.1.1
6.2
7.0
7.1
8.0
8.0.1
9.0
9.0
9.1
Software version equal to

or higher than
C1.532.5.w (except STAP)
C1.712.5.c, C1.714.3.a
C1.762.21
D1.305.4.f
D1.311.7.d
D2.304.4.s
D2.313.7.f
D2.314.7.p
E1.604.9.t
E2.404.u
E2.502.2.p
E2.504.1.ai
F1.602.3.i
F1.603.1.l
F2.500.6.g
F2.502.12
F3.301.36
F4.401.13
F5.401.25.b
G1.302.5
G1.503.23.b
H1.301.31.b
H1.301.31.b
I1.605.6.a
IP or IP/X25
connection
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
R5.2
R5.2
R9.1
R10.0
I1.605.22
J1.410.27.d
Yes
Yes
PPP connection
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
No
No
Yes
No
Yes
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes (1)
Yes (1)
Yes
Yes (2)
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 version
F3.301.36, F2.502.9 (or greater) so that LDAP/PCX synchronization runs properly
(XTSce69070).
PCX Releases are regularly updated. The new values also concerns previous OmniVista
releases.
TC1479
14
Ed. 01 / 19 May 2011
OmniVista 4760
5.2.01.03.d - RELEASE 5.2
4.2.2. IP, PPP connections to OmniPCX Office

Releases
1.0
1.1
2.0
2.1
3.0
3.1
4.0
4.1
5.0
5.1
6.0
7.0
7.1
8.0
Software version equal to or higher

than
Not supported
1.0.19.06 (2)
2.0.32.013
210.083.001
300/19.1
310/038.001
400/022.001 (1)
410/015.005 (1)
500/030.004 (1)
510/017 (1)
600/014.001
700/012.001
710/022.001
800/24.1.a
IP connection
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
PPP connection
(1)
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes (3)
(1)
Windows 2003 server is mandatory to receive urgent alarms on the fly.
No S0 modems with OminPCX Office 1.x.
1 B channel-ISDN connectivity with OmniPCX Office 400/15.3 and Multitech
ISDN modem.
(2) The check of attached node requires an OmniPCX Office versions 2.0. For
more information, refer to the technical communication TCV039 OmniVista
4760 licenses.
(3) Only with Windows 2003
4.2.3. OMC Release Compatibility with Operating Systems
OMC Releases
min
600 / 14.1.d
700 / 8.1.c
800/24.1.a
Windows XP
SP2
Yes
Yes
Yes
Windows 2003
SP1/2
Yes
Yes
Yes
Windows 7
Windows 2008
No
Yes
Yes
No
No
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).
Ed. 01 / 19 May 2011
15
TC1479
OmniVista 4760
5.2.01.03.d - RELEASE 5.2
4.2.5. OmniPCX 4400/Enterprise software locks

The modules of the OmniVista application are validated by the server license file. On the other hand
the access to data of the various PCXs requires to have appropriate software locks in each PCX:
OmniVista 4760 modules
Configuration
Accounting
Directory
Traffic observation
VoIP
Alarms
Secured SSH connection to
OmniPCX Enterprise
Number of OmniPCX 4400/Enterprise software locks

13 ECS Engine
50 - Configuration
42 - Accounting users
98 Accounting for local calls (for local accounting use)
99 Accounting for ABC calls(for network accounting use)
49 - Directory
42 - Accounting users (do not forget)
39 - Performance
42 - Accounting users
47 - Alarms
No specific lock for OmniPCX Enterprise. Security license for
OmniVista 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 part
of the configuration application window.
Accounting: Consult the NMCSyncLdap_x.log file at level of accounting ticket retrieval

(polling_accounting).
TC1479
16
Ed. 01 / 19 May 2011
OmniVista 4760
5.2.01.03.d - RELEASE 5.2
4.3.
Prerequisites of administration Client PCs
HARDWARE AND SOFTWARE (Minimum)

PC Pa ck 4
Se rve r Pa ck 3-2
Se rve r Pa ck 3-3
HP COMPA CT 6000 Pro

RA M 2Go
HD 250Go (1x250Go)
HP DL 380 G6
RA M 6GB - HD 438Go (3x146Go)
Mono Processor
HP DL 380 G5
RA M 2Go - HD 216Go (3x72Go)
Bi Processor
OmniV ista 4760 - Server
4059 IP
XP P
A PPLICA TIONS
OmniV ista 4760 - Client
4.4.
Screen
TFT 19"
/ Wi 7 32 bit
TFT 19"
TFT 19"
Prerequisites of Client PCs for directory consultation via WEB
HARDWARE AND SOFTWARE (Minimum)

Operating System
Internet browser
4.5.
Windows XP (Service Pack 2)

Windows 2003 SP1 or 2
Windows Vista
Mozilla Firefox 2.0
Internet Explorer version 6 or 7
Compatibility with SIP Device Management Server
SIP Device Management Server must have the version 1.2.000.010 or higher to be compatible with
OmniVista 4760 R5.2. The current version is 1.2.000.020.
SIP DMS is not compatible with Windows 2008 and Windows 7.
Ed. 01 / 19 May 2011
17
TC1479
OmniVista 4760
5.2.01.03.d - RELEASE 5.2
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
License file
Directory
Host name
Passwords
Carrier configuration
DNS domain name
Directory root
Connection to PCXs
Type of accounting (global /

detailed)
Access security
Backup mode
Windows data.
They are used to integrate the server PC in client computer network.
Installation data.
They are essential to undertake the server installation.
Management data.
They are used to define with the client the information to be completed after installation.
5.2.
Company directory
The company directory management is described in the technical communication TCV060 Directory
Management.
5.3.
Carrier configuration
The Code book import function is used to automatically import all accounting carrier parameters in
a database from previously created text files.
Refer to Administrator Manual Section 4 Accounting/Traffic/VoIP, to create these text files in
required formats.
An A4715/A4740 -> A4760 carrier migration tool can be used to retrieve the carrier data of the
same tariff area. This tool operates only from version 4_4.14x of Alcatel 4715/A4740. Its
functioning is described in the technical communication TCV002 Alcatel 4715/4740 carrier data
migration to OmniVista 4760.
An A4755 -> A4760 carrier migration tool can be used to retrieve the carrier data of the same tariff
area. Its functioning is described in the technical communication TCV017 Carrier data migration
from Alcatel 4755 to OmniVista 4760.
TC1479
18
Ed. 01 / 19 May 2011
OmniVista 4760
5.2.01.03.d - RELEASE 5.2
CAUTION
Each Code book import must be followed by a cost recalculation. It can be scheduled or run
manually. The recalculation process can take several hours depending on the number of tickets.
There are ten Code book files. Generally, they are located in a directory which has the carrier
name:
Information file
: .inf,
Area file
: .rgn,
City / Country file
: .ccn,
Direction file
: .dir,
Tariff file
: .trf,
Calendar file
: .cal,
Installation file
: .itl,
Adjustment file
: .adj.
ISDN services file
: .fct
Trunk groups file
: .trg (starting from R4.2)
The .inf ; .itl ; .dir ; .ccn files must be changed depending on the site.
The .cal file must be completed with local holiday days.
In the .itl file, the node names must be exactly the same as declared in the system directory;
ensure the correct case.
Note
The import never deletes an object. It can only create or update the objects information in the files.
The needed deletion are carried out manually or with the Clean Carrier Configuration application in
the scheduler. These cleans are needed to keep the OmniVista 4760 performances.
5.4.
Security
The Security Guide provides all useful information to integrate OmniVista 4760 into a secured
company network.
Establish with the client, the access security to manage inside the application:
access security to OmniVista 4760 modules,
access security when configuring the various PCXs.
5.5.
Backup mode
Establish with the client:
the backup period,
the backup location on the disk or on the network.
Ed. 01 / 19 May 2011
19
TC1479
OmniVista 4760
5.2.01.03.d - RELEASE 5.2
6.
INSTALLATION
6.1.
Additional installation of an integrated PC in factory
Only Operating System and JRE are factory installed on the PC delivered by Alcatel. Disabling the
On-access scan mechanism can provide a real installation time gain.
6.2.
Standard server installation procedure
The complete procedure is described in the Installation Manual.
Before beginning the installation, prepare the Server PC accordingly to section 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:
folder
Show
hidden
files
and
unset hide protected operating system files.
To set trace mode installation, after copying 4760 software on hard disk, modify
ServerSetup.ini:
replace 1=/v REINSTALL=ALL REINSTALLMODE=vamus ALLUSERS=2 /Lie
by
1=/vREINSTALL=ALL REINSTALLMODE=vamus ALLUSERS=2 /L*v
On 4760 Server:
Installation log file on server is in:
Document Settings\Administrator\Local Settings\Temp\
Omnivista4760_install.log for Server (if XP or Win2003)
Document Settings\Administrator\Local Settings\Temp\
Omnivista4760Client_install.log for Client (if XP or Win2003)
TC1479
20
Ed. 01 / 19 May 2011
OmniVista 4760
5.2.01.03.d - RELEASE 5.2
Client log connections are:

4760\Client\bin\4760Client.log on server
Client4760\bin\4760Client.log on client
To get an extended uninstallation log, launch:

msiexec /uninstall {C3CF0589-B127-4C15-A347-E0DCCBC74E87} /L*v
"%TEMP%\OmniVista4760_uninstall.log".
By default, on a DVD, data (directories and files) of the version must be located under
the root.
For copying more versions on a same DVD, you should modify the
\Setup\fix_media_source.vbs file to ispecify the actual path:
Example:
"MediaPackage", "\4760_R5.2.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 when
installing or updating.
Installation
To install or upgrade a remote server using a Terminal Server or Remote
Desktop connection, it is mandatory to start the session as "console "
(command mstsc.exe /console (Windows 2003, Windows XP SP2) or mstsc.exe
/admin (Windows XP SP3, Windows Vista)).
Otherwise the operation would fail.
In the installation fails, contact the Technical Support by providing the OmniVista
4760_install.log log.
If an installation fails, refer to the technical communication TC1007 OmniVista 4760
Installation / Uninstallation for a possible "manual" uninstallation.
Ed. 01 / 19 May 2011
21
TC1479
OmniVista 4760
5.2.01.03.d - RELEASE 5.2
6.2.1. Mandatory parameters installation

Parameter
Company name
Type
String
Destination directory
Directory
SunTM DSEE destination

directory
Sybase ASA server
destination directory
Database data destination
directory
Server archives destination
directory
Hostname and domain (or
dns suffix)
Mail server name or IP
address
Localization country
Directory
Localization language
Application administrator
logon
Database administrator
logon
Password
LDAP port
HTTP port
Directory
Directory
Directory
FQDN
Name or IP address
Country name
Language name
Default: AdminNmc
Fixed: DBA
Default: 389
Default: 80
Name values valid if

Always valid. Special characters are
escaped
Directory exists, is empty and is not a root
directory such as C:\
DNS domain exists
Hostname less or equal to 15 characters
Name can be resolved
See Table: OmniVista 4760 supported
countries
See Table: OmniVista 4760 supported
countries
ASCII characters
Characters not in: ,+"\<>;#&%|^
Characters in ASCII letters and digits and
_$#
ASCII characters
Length is at least 8
LDAP constraint: characters not in:
,+"\<>;#&%|^ and <space>
ASA constraint: characters not in
!"%&'()*+,-./:;<=>?\^`{|}~
and
<space>
In [1-1024] and [5000-65535]
In [1-1024] and [5000-65535]
Start the PC and connect as local administrator of PC.
Launch ServerSetup.exe .
After starting ServerSetup.exe, the system checks if software is already installed by
searching this registry entry:
HKEY_CLASSES_ROOT\Installer\Products\9850FC3C721B51C43A740ECDBC7CE478
If the hostname has more than 15 characters, the LDAP installation will fail. The limitation to
15 characters is written in the registry.
TC1479
22
Ed. 01 / 19 May 2011
OmniVista 4760
5.2.01.03.d - RELEASE 5.2
The registry key is found in the place:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog.
During installation, the setup files are extracted and copied in the %Temp% folder. If the
space in the %Temp% folder is less than required, then it will not copy all the files in the
%Temp% folder. So to make sure that there is enough space in %Temp% folder a check has
been done during installation. The setup will not continue to install if the temp size is less
than 100 MB. The threshold value is maintained at 100 MB to make sure that it has enough
space to keep the extracted files from the setup during installation. The estimation is
calculated from the space occupied by the installation files in the %Temp% folder. This space
checking is only applicable for Server.
3
If the correct Java Runtime Environment (JRE) (1.6.0_11) is not detected, its installation will
start automatically.
Indicate the location of the xxyyyzza.sw4760 license file, supplied on diskette or in a

directory in the PC. The setup will check coherency of the supplied file.
Specify:
the Company Name which will be used as directory root,
the installation directory of OmniVista 4760 (this access path must not have space as
"Program Files"), of Sun ONE Directory server, of Sybase software and database SQL.
Sybase software should never be installed in the same directory as OmniVista
4760; the upgrade towards a higher version would fail.
Specify the backup directory then click on Next.
Specify:
the numbers of the LDAP, LDAPS and HTTP ports are standardized. Do not change them
unless you need to,
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.
Enter:
the "IP name / address of the e-mail server" if used,
choose the Country that gives the Language, the paper size and the
currency (parameters used for the accounting),
The Cost Centers management method.
10 For a standard installation, do not pre-configure the system.

Click on Install to launch the installation.
Ed. 01 / 19 May 2011
23
TC1479
OmniVista 4760
5.2.01.03.d - RELEASE 5.2
Click View log file to displays the log file of installation (Omnivista4760_report.log).
The log file is useful in case of installation error. This file displays the performed
installations steps (log localization: %Temp% for Vista).
11 The patches available under 4760/Install/Patches are installed.
The View log for Patches button opens the patch log window. The patch log
window displays information about patch installation (log localization: installation
repertory\4760\install\patch installer.log).
12 At the end of installation, confirm to reboot the PC.
6.2.2. Restorecontext.ini file
This file is created/updated with software operations (installation/upgrade).
Option name
DATE
NmcVersion
SvDomain
svNMCDirInst
SvNMCName
svPortApache
svServerPort
svSuffix
szAsaDir
szDataBase
szNetscape
TIME
nmcInitialVersion
nmcPreviousVersion
6.3.
Description
Installation date, format MM-DD-YY
Version that has been installed
DNS domain
Install directory
Host name (without domain)
Httpd server port
LDAP server port
Company name
Sybase ASA installation directory
Database files directory (*.db)
SunTM DSEE installation directory
Installation time, format HH:MM:SS
Current version at install time (never changed) (created with installation)
Version that has been upgraded (created when upgrading)
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.
TC1479
24
Ed. 01 / 19 May 2011
OmniVista 4760
5.2.01.03.d - RELEASE 5.2
6.4.
Server post-installation
Post-installation is described in the Installation manual. Carry out in more the operations described
below.
When the installation and the configuration are finished, we recommend performing a server
data backup on a networked disk or on a CDROM.
Manage the sharing of archive directory of tickets to allow the restoration of these tickets.
Example: Name of sharing: 4760_ARC, Reading right for "Everyone".
In order to retain the correct version of JRE, you should disable the automatic check of
upgrades.
In the Control Panel, use the standard display (the default display of Windows XP masks some
icons):
Click on java,
In the Update tab, disable Check for update automatically.
6.5.
Client installation procedure

Install the client in a new c:\4760client or c:\Program Files\4760client
directory. Do not use an existing directory (c:\Program Files).

Check that the Client PC and the Server PC can reach together on the network.
Client PC end, run:

ping <Server_Name>.
ping <Server_Name>.<Server_DNS_Suffix_Name>
Server PC end, run:
ping <Client_Name>
ping <Client_Name>.<Client_DNS_Suffix_Name>
If it is not the case, ask the network manager to correct the DNS management or to complete
host file (under winnt or windows\system32\drivers\etc\) of Client PC and Server PC
with:
IP_Address Host_Name Host_Name.DNS_Suffix_Name
Example: 155.166.123.156 OmniVista OmniVista.alcatel.fr
Ed. 01 / 19 May 2011
25
TC1479
OmniVista 4760
5.2.01.03.d - RELEASE 5.2
Method 1
1
Launch ClientSetup.exe.
If the correct Java Runtime Environment (JRE) (1.6.0.21) is not detected, its installation will start
automatically.
Accept "Alcatel License agreement".
Enter the installation path.
Click on Install to start the installation
In order to retain the correct version of JRE, you should disable the automatic check of
upgrades.
icons):
Click on java,
With a 4760 client installed under Vista, a warning message is displayed. Select the Dont show
this message again option.
Method 2
When the server is already installed you can download the client installation file using this url:
http:/server_name/cgi-bin/OmniVista4760Client.exe (replace server_name by your OmniVista 4760
server name).
For more information, refer to the Installation Manual.
6.6.
Accessing OmniVista 4760 via a browser
6.6.1. Installation
Contact the client network manager to authenticate the OmniVista 4760 server with its name
and its IP address in intranet sites.
If a request of proxy authorization occurs during this procedure, you will probably not be able to
access the application since the network manager does not allow this type of connection.
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
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.
TC1479
26
Ed. 01 / 19 May 2011
OmniVista 4760
5.2.01.03.d - RELEASE 5.2
Under Internet Explorer 6.0:

Menu Tool/Internet Options/Privacy tab,
Select a different level of Block All Cookies or manage with the Modifier button
the authorization for the 4760 server.
Under Mozilla Firefox 2.0:

Menu Edit/Preferences/Advanced ,
Under Cookies, tick Accept all cookies,
Following management will prevent from a language switch after search in the directory. In this
case the No such object error message is also displayed.
The management described concerns Internet Explorer 6.0. An equivalent management has to
be done for other browsers.
menu Tool/Internet Options/Privacy tab
click on Advanced button
select Override automatic cookie handling, accept option for First-Party

Cookies and Third-party Cookies and validate Always allow session
cookies
Before accessing the JAVA page of the network management, install the JAVA Plug-in:
If the correct JRE version (1.6.0.21) is already installed on the station, go to the point 5.
On the home page, click on the Before using the Alcatel-Lucent OmniVista
4760 NMS for the first time or from a new server, please install
JRE.
Click on Open to start the installation procedure of JRE.
Select the standard installation procedure.
Reboot the PC after installation.
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 occurred
correctly, check in the Documents and Settings/Your connection login directory, that the .java.policy
file contains the address returned by the server in text mode.
Example: Server named OmniVista installed in the alcatel.fr domain.
grant codeBase "http:// OmniVista.alcatel.fr /-" {
permission java.security.AllPermission;
};
grant codeBase "http:// OmniVista /-"
{
permission java.security.AllPermission;
Ed. 01 / 19 May 2011
27
TC1479
OmniVista 4760
5.2.01.03.d - RELEASE 5.2
If from the PC, you cannot ping to OmniVista.alcatel.fr, there is a name or domain problem.
Check the hosts file or the addresses of the DNS server.
If the hosts file is used (without DNS), it must contains a line like below:
ip_address server_name server_name.domain
Example
155.166.123.156 OmniVista OmniVista.alcatel
7.
UPGRADES
Perform OmniVista 4760 server data backup then a defragmentation before starting upgrade.
7.1.
Prerequisites
Close all windows opened before starting server upgrade but do not stop
NMC Services.
The installation fails if the operating system is not running in SP1 at least
Stop if necessary the SIP DM Server services.
Temp4760 folder
This folder will be created under the %Temp% folder. During the upgrade it makes a backup of the
data and then uninstalls and reinstalls and finally makes an import of the data backup. So during
the backup operation the Temp4760 folder is used to keep the backup files. It stores the files in ace
format. Currently ten ACE files are stored. The Temp4760 folder is created depending upon the path
given during installation of LDAP, Sybase or 4760.
If the path drive letter for the LDAP is E: then Temp4760 will be created in the path
E:\Temp\Temp4760\.
During the LDAP database backup the Save_Ldapbasesfiles.ace file will be stored in the path
E:\Temp\Temp4760\. If the Sybase is installed in path drive D: then the
Save_ASAdatabasefiles.ace file will be available in the path D:\Temp\Temp4760.
7.2.
License file update
Close the NMC service manager with the OmniVista 4760 service manager.
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.
Restart NMCService Manager.
Check that the licenses have been updated: Help\About menu.
TC1479
28
Ed. 01 / 19 May 2011
OmniVista 4760
5.2.01.03.d - RELEASE 5.2
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
R5.0
R5.1
R5.1.1
Versions
5.0.07.02.b/5.0.07.03.c/5.0.07.05.b
5.1.04.00.b
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 the
nmc.license file but this does not allow an upgrade of the server. You need to reinstall a new
application R5.2 or perform an upgrade with an intermediate allowed version.
Procedure for versions before R5.0
Backup parameters (PCX in System Directory, Logins, Directory, Carriers definitions,

accounting tickets).
Reinstall if necessary a new operating system compatible with OmniVista 4760 R5.2.
Install OmniVista 4760 R5.2, then configure OmniVista 4760.
Procedure for versions starting from R5.0

Before the upgrade:
IMPORTANT
Get the directory manager and dba passwords. You should have a license compatible with the
Release R5.2 (version 12 or 13).
Perform a 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\thmes directory.
The customizing carried out on the welcome page of Web Client is not saved. If necessary, you
should save the modified data of the 4760\webclient (R4.0) or 4760\client (other
releases) directory.
The customizing of the topology is saved during the upgrade. For security, it is possible to first
export the data from the system directory:
Nmc\nmcConfiguration\globalPreferences\topology
The Java RunTime Environment (JRE) will be installed if its version is not correct:
1 It is advisable to stop any On-access scan mechanism. Disabling the On-access scan
mechanism can provide a real installation time gain.
2 Check all OmniVista 4760 services have been started.
3 Launch the server update with the Serversetup.exe command.
4 Specify the location of license file when the system requests it.
5 Once the upgrade is completed, carry out all the checking jobs of the installation.
Ed. 01 / 19 May 2011
29
TC1479
OmniVista 4760
5.2.01.03.d - RELEASE 5.2
6 After any upgrade operation, it is recommended to save 4760 databases using 4760
Maintenance application.
7.4.
Installing a corrective patch
The corrective patches are installed automatically at the end of 4760 server update if they are
available in the installation CD-ROM.
To manually install a patch copy the correspondent .ace file in the 4760\Install\Patches folder
and launch the 4760\install\Patchinstaller.exe command.
You can consult the patch installation log in \4760\install\patch_installer.log.
The installed patch list is in \4760\install\patch_history.ini.
7.5.
Upgrading the OmniVista 4760 client to 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 system
proposes an update from this server. This update is running correctly only from a client version equal
or greater than 3.2.05.00.b. For client version less than 3.2.05.00.b, do not accept the update
procedure otherwise client could not open anymore. Under such circumstance, it is necessary to
uninstall the client and to reinstall it.
If the client is in version lower than R5.1, it is kept. An additional new client in R5.1 is installed in a
directory named Client4760 5.1.
This allows the cohabitation of several versions on a same PC.
A client can also be installed by launching the ClientSetup.exe file.
The rules of cohabitation above will also apply.
7.5.1. Installing the patch
There are no more patches specific "clients".
When connecting a client to server, the version of the nmc50.jar file is checked.
If the client version is below, an upgrade is available when connecting to the server. The upgrade is
carried out automatically.
7.5.2. Disabling the automatic upgrades of JRE
In order to retain the correct version of JRE, you should disable the automatic check of upgrades.
icons):
Double click on java,
TC1479
30
Ed. 01 / 19 May 2011
OmniVista 4760
5.2.01.03.d - RELEASE 5.2
8.
OmniPCX OFFICE
Refer to the Technical Communication TCV049 Installation procedure for Release 2.1/3.x for
OmniPCX Office (IP, ppp, Accounting, Alarms, Troubleshooting).
8.1.
Writing rights on dedicated OmniPCX Office directories
The management described below has to be applied, not only for the save/restore/download
operations, but also to enter into PCX configuration.
The OmniPCX Office data are saved by default on the 4760 server PC in the directory
4760_ARC/OXO/data. This directory is shared as 4760-databases during 4760 installation (or
4760-PM5 in case of upgrade operation), with read access to everyone.
CAUTION
If the 4760_ARC\OXO\data directory already exists before 4760 server installation (for instance
after uninstalling a previous 4760 server) and has a shared name, this name will not be modified by
4760 R4.1 installation. To use OmniPCX Configuration application from 4760 server, Windows
directory shared name must be the same as the name defined in OmniVista 4760 System directory
(this name can be configured in /NmcConfiguration GlobalPreferences / Config /
OXOAccess).
The PC administrator has to allow the writing right on the sharing to a local user. Remove "Everyone"
from the list of users. In the sharing management, for the user limit, "Maximum allowed" has to be
validated. A reboot of the PC can be needed to take into account the management.
This local user has to be declared in the 4760 server:
System directory / NmcConfiguration / GlobalPreferences/Config/OXOAccess
The URGALARM user can be used if its already created or all other local user with permanent
password.
The software versions to be downloaded to the PCX have to be stored in the directory
4760_ARC/OXO/sw. For security reasons, it is no more required to share this directory.
8.2.
OMC
From R4.0, OmniVista 4760 does not support PM5 software. To configure OmniPCX Office
(whatever is the version) through OmniVista 4760, OMC software has to be installed on the server
and client PCs.
OmniPCX Office can be configured from a 4760 client after following the procedure below:
Uninstall PM5 software install on the PC.
Reboot the PC.
Install OMC software 700/xx or OMC 800/xx
Reboot the PC.
Run 4760 client, open Configuration application and launch the "Configure" menu after
selecting an OmniPCX Office: OMC client will be automatically open.
Ed. 01 / 19 May 2011
31
TC1479
OmniVista 4760
5.2.01.03.d - RELEASE 5.2
Notes
The same procedure has to be applied on PC hosting 4760 server to perform OmniPCX Office
maintenance operations.
Administrative parameters (mandatory customer information) must be configured on each

OmniPCX Office that we aim to manage from OmniVista 4760.
9.
ALCATEL-LUCENT OFFICE (4200)

OmniVista 4760 R4.2 is the last release compatible with Alcatel-Lucent Office
(4200).
OmniVista 4760 R5.2 is no more compatible with Alcatel-Lucent Office (4200).
TC1479
32
Ed. 01 / 19 May 2011
OmniVista 4760
APPENDIX 1
CORRECTIONS

5.2.01.03.d RELEASE 5.2
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
Ed. 01 / 19 May 2011
TC1479
OmniVista 4760
5.2.01.03.d RELEASE 5.2
APPENDIX 1
CORRECTIONS
TC1479
Ed. 01 / 19 May 2011
OmniVista 4760
APPENDIX 1
CORRECTIONS

5.2.01.03.d RELEASE 5.2
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 / 192752061.
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.
Ed. 01 / 19 May 2011
TC1479
OmniVista 4760
5.2.01.03.d RELEASE 5.2
APPENDIX 1
CORRECTIONS
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.
DIRECTORY
crms00252049 Graphical view of sets available / 1-110475829.
TC1479
Ed. 01 / 19 May 2011
OmniVista 4760
APPENDIX 2
RECOMMENDATIONS

5.2.01.03.d - RELEASE 5.2
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
Ed. 01 / 19 May 2011
TC1479
OmniVista 4760
5.2.01.03.d - RELEASE 5.2
APPENDIX 2
RECOMMENDATIONS
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.
9.
Weekly accounting report ......................................................................... 8
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
TC1479
Ed. 01 / 19 May 2011
OmniVista 4760
APPENDIX 2
RECOMMENDATIONS

5.2.01.03.d - RELEASE 5.2
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
Its 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 <space>
ASA constraint: characters not in
Ed. 01 / 19 May 2011
!"%&'()*+,-./:;<=>?\^`{|}~ and <space>
TC1479
OmniVista 4760
5.2.01.03.d - RELEASE 5.2
APPENDIX 2
RECOMMENDATIONS
Do not lose this password:
Admin and DBA are needed for the maintenance and the upgrade of server,
Admin and Directory Manager cannot connect to the OmniVista, they are used for advanced
management of the SunTM DSEE.
Do not use AdminNMC, after installation for standard management of OmniVista 4760. Create
other administrator or manager accounts in order to retain the preferences of the various
administrators and managers and always keep a supervisor account even if the password is lost.
2.2.
Rights
To allocate a right to an OmniVista login, select the predefined groups such as Directory Expert,
Network Expert and add members to these groups.
A login can belong to several predefined groups. In this case, these rights correspond to the sum of
rights of each group.
If there is no relevant profile:
allocate the rights individually:
select each application,
add a specific right (read, write, etc.) corresponding to the individual.
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 photo
takes 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, you
must not enter 001 but directly 1 otherwise the Past Time Performance files loading in database no
longer works.
Avoid the used of . (dot) in the name of the Network, Sub-Network and PCX (In some cases it could
be a problem during restoration of archives accounting tickets)
Example to avoid: Name of PCX : Brest.Alcatel
4.
CONFIGURATION
4.1.
Changing the PCX connection
Make sure to cut all connections in progress to this PCX via OmniVista 4760:
TC1479
Ed. 01 / 19 May 2011
OmniVista 4760
APPENDIX 2
RECOMMENDATIONS

5.2.01.03.d - RELEASE 5.2
cut Telnet,
close Configuration,
but above all in the technical directory, deactivate the Alarm Processing.
As soon as the connection has been cut, carry out your modification in the "Connectivity" tab then if
necessary reactivate the alarm processing.
4.2.
Free users name in the PCX
Its extremely inadvisable to name a great amount of free users in the same way (example:
name=FREE). This rule as well concerns Dect Shells.
Its recommended adding an information in the First name field (example: extension number).
To prevent from entry creation for these extensions in the Enterprise Directory, you have to not
validate the Call by name function.
These extensions s successive allocations / unallocations lead to a lot of inactive sets creation into
the accounting organization.
The cleaning of a great amount of inactive free of ticket entries regularly fails; refer to XTSce15452.
5.
ALARMS
5.1.
Alarm supervision
If a PCX has to centralize all the network alarms and events, you must correctly manage the nodes
supervised by this PCX in the PCX incident management. Do not set the node to supervise itself.
If the management is incorrect, the alarm server will be saturated by the events sending which
damage the application operation (slow down, close of some services and disk saturation).
At 4760 server level, create this alarm centralizing PCX to do not restore alarms from a PCX still
unknown in 4760. Do not check the box Alarm Review on the PCX monitored otherwise the alarms
will be doubled.
Starting from R2.1, a character "_" is added to the server name, in the "Events Routing discriminator"
created in the OmniPCX 4400 and Enterprise (SERVER_ instead of SERVER). The number of names
being restricted to 16, it is recommended to suppress previous names in the PCX. If a PCX is not able
to create an "Events Routing discriminator" the alarms are not sent to the corresponding server.
6.
TOPOLOGY
When the OmniVista 4760 manages a complex PCX network including a lot of inter-nodes links, the
topology display delay can be very long. According to the configuration type, following two solutions
decreases this display time:
a parameter in the Topology application, allows to enable/disable the display of the VPN links:
Preferences\Topology\Configuration\Display VPN links
Ed. 01 / 19 May 2011
TC1479
OmniVista 4760
5.2.01.03.d - RELEASE 5.2
APPENDIX 2
RECOMMENDATIONS
a script allows to suppress the display ot the inter-node links to reduce the display delay of the
network. It is included in the TOOL directory of the installation CD.
To launch this script proceed as follows:
edit the delnodelink.bat file and enter your own Directory Manager password,
then launch the script on the Omnivista 4760 server PC.

This modification is lost after every network synchronization. So we have to program an
automatic re-launch job in the scheduler:
make a copy of the script under 4760\bin,
add a new job in the scheduler,
add a new task to launch the delnodelink.bat file.
Before any upgrade operation, caution has to be taken to be able to retrieve the work.
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, if
necessary),
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 to
dissociate the PCX cost centers from the OmniVista ones, you must manage them in the OmniVista
application. The Cost Center field, in OmniVista, will be completely independent from the cost
center managed on the PCX, there will be no synchronization in either direction.
To force a cost center in the accounting organization:
manage the cost center information in the company directory,
create a cost center directly in the accounting organization; then move the entries in this cost
center.
TC1479
Ed. 01 / 19 May 2011
OmniVista 4760
APPENDIX 2
RECOMMENDATIONS

5.2.01.03.d - RELEASE 5.2
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 accounting
data (30 millions tickets) will not be exceeded. Then make the modifications:
in the Directory, Technical tab, move to

NMC/PC_Name/servers/PC_Name/NMCDatabase
select the Database tab,
change the CleanTicketAndAffiliatedOldThan attribute.
7.4.
7.4.1.
Carrier management
Tariff: Managing the period
During management of tariffs, period, only the start time is managed, the application
automatically manages the end time.
Do not forget to create the period which begins at 00H00 and loop back with the 1st one
managed.
7.4.2.
City / Country name: Loss of performance
During normal use, the number of Town / Country must be reduced. This information is in fact used
to identify in the reports the telephone directions frequently used; for example, to identify the
subsidiaries of a company.
It is not used to calculate the cost of telephone calls.
When the number of City / Country names becomes too high (>5000), the coherence check system
slows down the performance during accounting modifications.
Beyond 10000 Cities/Countries, the calculation of cost is impossible.
It is necessary to create areas and directions to optimize the treatment of the cities/countries.
Example
City country Name
Paris 0170
Paris 0171
Paris 0172
Region
Paris
Prefix 0170
Prefix 0171
Prefix 0172
In this example, for the Cities/Countries, the Paris entry appears 3 times whereas by using the
regions and directions, the Paris entry appears only once.
Ed. 01 / 19 May 2011
TC1479
OmniVista 4760
5.2.01.03.d - RELEASE 5.2
APPENDIX 2
RECOMMENDATIONS
8.
REPORT GENERATOR
8.1.
Weekly accounting report
CAUTION
The week defined in the report application does not begin on Monday but Sunday at 00h00 AM and
finishes on Saturday at 11h59 PM.
9.
SCHEDULER
9.1.
Tasks succession order
Ones attention has to be given to the tasks succession.

The 4760 data backing up must never start when other tasks are running. Actually the saving
operation needs the all services stopping. This may have important bad consequences on
synchronization, tickets loading and cleaning operations.
10. MAINTENANCE
10.1. Rule of partitioning
It is recommended to have only one partition per physical disk and to separate the partition system
from the application. In effect, if a partition seems to be too small, it is impossible to extend it
without being obliged to format and re-install.
Example: put OS on C: on a disc of 80 GB, and the application on D: on a disc of 72 GB.
If the network allows it, it is recommended to use "network" disk as working space to carry out
upgrades, defragmentation data backups. In effect, each of these operations requires for their
working space near the twice Sybase size therefore depending on the cases up to 40 GB.
10.2. Backing up the databases

In case you need to re-install the application, it is possible to use some managed parameters of the
existing OmniVista 4760. To ensure you have as much information as possible on installation, you
must schedule:
the company directory LDIFF export,
the PCX network LDIFF export,
the carrier Code book export.
10.3. Backing up the OmniVista 4760 database

By default, no backup is scheduled. Only closing the server once a week on Sunday at 1 AM is
planned to impose a memory release under Windows.
The backup stops the services (the server is not available) and compresses the databases in zip
format. To carry out the backup, you must have twice as much space free as the total size of all the
databases.
TC1479
Ed. 01 / 19 May 2011
OmniVista 4760
APPENDIX 2
RECOMMENDATIONS

5.2.01.03.d - RELEASE 5.2
You must schedule a backup at least once a week of the OmniVista 4760 data and purge these
backups to avoid the disk saturation.
Refer also to the chapter Tasks succession order (Scheduler) to correctly schedule this task.
Note
A backup must be carried out before any important operation on the server (Upgrade, Retrospective
Cost Calculation on the complete database, etc.).
10.4. Defragmentation of the OmniVista 4760 database

It is recommended to schedule a monthly defragmentation of the databases. The defragmentation of
OmniVista 4760 databases allows to optimize the performances of jobs relative to Alarms,
Accounting, Past Time Performance or VoIP applications.
It is also recommended to run a defragmentation before upgrading a version.
CAUTION
This operation stops the services: the server is not available.
On a large database of about 1 GB, allow about 2H30min.
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 the
copy if this local directory (\usr4\BACKUP\IMMED) already contains a backup.
Use swinst to restore this backup.
Ed. 01 / 19 May 2011
TC1479
OmniVista 4760
5.2.01.03.d - RELEASE 5.2
APPENDIX 2
RECOMMENDATIONS
TC1479
10
Ed. 01 / 19 May 2011
OmniVista 4760
APPENDIX 3
ADVANCED MANAGEMENT

5.2.01.03.d - RELEASE 5.2
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.
2.3.
3.
Customizing the directory field names ...................................................... 5
ALARMS - TOPOLOGY .................................................................6
3.1.
4.
Available options ..............................................................................................5
E-mail server ............................................................................................ 6
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
Ed. 01 / 19 May 2011
TC1479
OmniVista 4760
5.2.01.03.d - RELEASE 5.2
APPENDIX 3
ADVANCED MANAGEMENT
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.
TC1479
Simple Configuration Profile ..................................................................... 9
Ed. 01 / 19 May 2011
OmniVista 4760
APPENDIX 3
ADVANCED MANAGEMENT

5.2.01.03.d - RELEASE 5.2
1.
INFRASTRUCTURE / INSTALLATION
1.1.
Reinstalling the server
To reinstall the OmniVista 4760 server application with an empty database on a PC where
OmniVista has already been installed, you must first uninstall the application. The server module
must be uninstalled using a local administrator account.
To uninstall the OmniVista 4760 server:
Close all the OmniVista 4760 client applications. The SNMP and/or Compaq manufacturer
services must not be enabled during the uninstall phases.
Use the Add/Remove programs interface from the Control Panel.

Select the OmniVista 4760 Server program and click on Remove.
The uninstall procedure will take several minutes.
The SunOne Directory server and the SQL Anywhere Studio 9 software will also be removed.
Note
The Java Runtime Environment is not uninstalled.
Restart the computer to complete the uninstallation procedure.

CAUTION
If you cannot access "OmniVista 4760 Server" from Add/Remove programs you should
proceed to a manual uninstallation of various items.
This procedure must be applied when Windows Installer cannot restore the original state of the
PC after an incident when installing or upgrading.
It must also be applied if the automatic uninstallation fails.
CAUTION
As the registry is involved during this operation, it is recommended to perform before a system
backup for a possible restore later.
From Add/Remove programs, remove if necessary the visible programs (Directory
Server and SQL Anywhere 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 same
path as the previous installation
Copy the PsExec directory from the uninstall tool.zip file available on the DVD of
the version (Tools) to c:\Program Files.
Launch reg_del.bat.
This commands opens the registry editor.
Import the del_regkeys_TS_50.reg file.
Reboot the PC.
Remove the directories where are installed various components of the system: 4760 server,
Sybase, Netscape, SQL database.
Ed. 01 / 19 May 2011
TC1479
OmniVista 4760
5.2.01.03.d - RELEASE 5.2
APPENDIX 3
ADVANCED MANAGEMENT
Refer to the technical communication TC1007 OmniVista 4760 Installation / Unsinstallation for
additional information about the manual uninstallation.
1.2.
Change the IP address
1.2.1. Change procedure

1 Inform the users then stop the NMC Service Manager service.
2 Change the IP address of the server.
3 In the \4760\data\Notify directory, delete all files EXCEPT Notify.cfg.
4 Reboot the server.
1.2.2. Add a new IP address
To prevent having to change the server IP address (example for OmniVista 4760 on an installer's
portable computer), leave the main IP address alone but add a secondary IP address on NT.
Then PCXs can be defined on the sub-network corresponding to this secondary address.
1.3.
Change the PC name or the Windows DNS suffix
This operation is not supported.

In such a case, the workaround consists in recovering the data of the old PC in the following way:
Export/import the PCX Technical data and Company directories,
Export/import the carriers configuration.
Recover the SQL database files in the 4760\data directory to copy them on the new PC after
installing the 4760 in the same version.
1.4.
Change the passwords
The passwords of following accounts can be changed:
dba
Admin
Directory Manager
The change is made by using the toolsOmnivista tool available from 4760\bin directory.
Directory Manager password is needed to change account passwords.
For more information, please refer to the technical communication TCV045 How to change
OmniVista 4760 server passwords?.
1.5.
Re-assignation of accounting tickets to active entities
The toolsOmnivista tool is used to update the organization of the accounting. It is used to assign
the tickets of inactive entities to the corresponding active entities. Then these inactive entities are
removed.
TC1479
Ed. 01 / 19 May 2011
OmniVista 4760
APPENDIX 3
ADVANCED MANAGEMENT

5.2.01.03.d - RELEASE 5.2
This feature allows a re-sequencing of the organization after a period of adaptation which generally
follows the startup of a OmniVista 4760 server.
2.
DIRECTORY
2.1.
Access the OmniVista 4760 directory through Alcatel 4059
In Alcatel 4059, enter:
the OmniVista 4760 server name,
the company directory root, example o=MyCompany, o=DirectoryRoot.

By default, Search base field length is limited to 27 characters in Alcatel 4059 LDAP directory
(SR 1-64755241).
the password defined on OmniVista 4760 (in case of confidentiality management).
For more information, refer to Alcatel 4059 installation procedure; the minimum release is
4.014.10.
2.2.
Customize the WEB consultation
2.2.1. Available options

The Administrator manual describes the client Web customization in Directory section.
You can:
Customize the attributes of a Company Directory level,
Customize the results display and print parameters (number of lines, grid sort, attributes to
display in grid, printed attributes)
Customize the detail and edit parameters (attributes to display and to edit in detail view)
Customize the search filters,
Customize partially the predefined themes (name, logo, logo position),
Customize fully the Custom theme (name, logo, logo position, colors, background, fonts).
2.3.
Customizing the directory field names
An integrated tool allows to modify most of the field names displayed in Company Directory from a
Web or installed client.
To launch this tool proceed as follows:
Start/Programs/OmniVista 4760/Tools/Customize dictionary
For more information, refer to the Administrator Manual - Directory section.
Ed. 01 / 19 May 2011
TC1479
OmniVista 4760
5.2.01.03.d - RELEASE 5.2
APPENDIX 3
ADVANCED MANAGEMENT
3.
ALARMS - TOPOLOGY
3.1.
E-mail server
OmniVista 4760 can send alarms, reports or a accounting monitoring notification to an e-mail
server specifying a local or external e-mail address. Transmission is done via SMTP on the default
port 25.
The sender's name of messages can be customized in the technical directory (nmc\server_name).
To check that the e-mail server can be reached by SMTP on port 25, try to connect via Telnet. On the
server PC, at the DOS command prompt, execute :
Telnet Server_Name_mail 25
If the SMTP port of your e-mail server is not the standard port 25, change it during the Telnet test. If
the test is successful on this port, copy the port number in the OmniVista 4760 application :
run the Directory application then click on the Technical tab,
click on the machine name in the tree structure. In the data area, modify the attribute E-mail
server and set :
(do not put spaces around the : )
E-mail_Server_Name:Port_Number
For more information, refer to the technical communication TCV020 Sending e-mails with
OmniVista 4760 Release 2.0.
4.
REPORT GENERATOR
For more information, refer to the troubleshooting guide TG0026 Reports.
4.1.
Schedule a report export
4.1.1. Restriction
To schedule a report with a file export to a network drive, OmniVista 4760 must be able to use a
Windows account with certain rights.
If the password is wrong or obsolete, the report will no longer be exported.
4.1.2. Procedure
Use an account with local administrator rights on the OmniVista Server PC. We will suppose that this
account is named ADM4760 and that the Server PC is named PCSERVER.
If the Server PC is installed in a Windows domain and that the users log in DOMUSER, therefore the
login of this account is DOMUSER\Adm4760.
If the Server PC is installed in a workgroup, the login of this account is PCSERVER \Adm4760.
1
Run a Windows session as local administrator of the server PC.
Define a default printer for "User4760", if necessary.
TC1479
Ed. 01 / 19 May 2011
OmniVista 4760
APPENDIX 3
ADVANCED MANAGEMENT

5.2.01.03.d - RELEASE 5.2
Run Start/Administrative Tools (Common)/User manager.
Select the menu Policy/User rights.
Tick Show Advanced user rights.
For the following rights, add the user Adm4760 :

Act as a part of the operating system
Increase quotas/Adjust the memories quotas
Replace a process level token
Open a session locally
4 Grant the OmniVista 4760 the right to use this user. To do this :
run the Directory application, then click on the System tab,
in the tree structure move to

NMC / Server_Name / servers / Server_Name / ExecdExc
click on NT Account ,
manage the attributes :

User = DOMUSER\Adm4760, for a Server PC belonging to a domain of which the users
are managed under DOMUSER,
User = PCSERVER\ADM4760, for a Server PC belonging to a Workgroup and calling
PCSERVER,
Password: your password.
5 Run a scheduled report to check the correct setting.
4.2.
Export to PDF format with specific characters to languages
The specific characters to languages (Polish, Czech, Chinese, Russian, etc.) are taken into account in
exported reports in pdf format.
To do that, you should specify the Windows font which supports these specific characters: under
NMC\serverName : complete Name of font family for pdf export and Available
font styles (pdf export) (set the font name in an application such as Word).
4.3.
Change of paper format for printing the reports
The paper format for printing reports is selected when installing the server. However, you can
change it after. In the technical directory, click on the name of server in the tree. In the right window,
select the appropriate Paper Format.
Ed. 01 / 19 May 2011
TC1479
OmniVista 4760
5.2.01.03.d - RELEASE 5.2
APPENDIX 3
ADVANCED MANAGEMENT
5.
MAINTENANCE
5.1.
Backup on a remote host
5.1.1. Restriction
The OmniVista 4760 Server PC and the remote host must be located on the same Windows host
domain : in the same workgroup or in the same domain.
This backup mode requires using a Windows account. Therefore this account must be enabled of the
OmniVista 4760 server and have the right to move files on the remote host.
5.1.2. Procedure in a domain
For the requirements of this procedure, we will suppose that the hosts are installed in the same
DOMMACHINE domain and that the users are identified in the DOMUSER domain.
Use an networked account with local administrator rights on the OmniVista Server PC. Let us name
this account ADM4760. The login of this account is DOMUSER\Adm4760.
1
Share a repertory on the remote host for the user DOMUSER\ ADM4760.
On the Server PC, run a Windows session as DOMUSER\ ADM4760.
Grant the Execcdex and SaveRestore services, the right to use this user. To do this :

NMC / Server_Name / servers / Server_Name / ExecdEx

User = DOMUSER\Adm4760,
Password : your password,
carry out the same management for SaveRestore
When the Maintenance module is run, you can select a network disk for the backup.
5.1.3. Procedure in a Workgroup

For the requirements of this procedure, we will suppose that the hosts are installed in the same
WORKGROUP1 workgroup and that the Server PC is named PCSERVER.
Use a Server PC account with local administrator rights on the OmniVista Server PC. We will
suppose that this account is named ADM4760. On the remote host, create the same ADM4760 with
the same password.
1
Share a repertory on the remote host for the user ADM4760.
On the Server PC, run a Windows session as DOMUSER\ ADM4760.
TC1479
Ed. 01 / 19 May 2011
OmniVista 4760
APPENDIX 3
ADVANCED MANAGEMENT

5.2.01.03.d - RELEASE 5.2
Grant the Execcdex and SaveRestore services, the right to use this user. To do this :

NMC / Server_Name / servers / Server_Name / ExecdEx

User = PCSERVER\Adm4760,
Password : your password,
carry out the same management for SaveRestore
4 When the Maintenance module is run, you can select a network disk for the backup.
6.
CONFIGURATION
6.1.
Simple Configuration Profile
The OmniPCX Enterprise security access profile 10 has been designed to allow some users such as
attendants to perform simple configuration operations.
By default, user with this profile will only have:
All rights on hunt group configuration.
All rights on user configuration.
All rights on Direct speed dialing number prefix configuration.
To active this profile for the OmniVista user ATTENDANT4760:
From Company directory, set the ATTENDANT4760 person into the member list of the
"Simplified Configuration" group (localized in Company name / Administration/ Groups).
From Security panel menu, open Access Control Editor for Configuration application: check
Profile 10 has been set to "Simplified Configuration" group.
If it is not the case, add or update rights of the "Simplified Configuration" group with:
Access Level= Normal
OmniPCX 4400 Access Level= Profile 10
Note
Profile (10) can be edited to add more available items (for instance program keys) or to remove
available items (for instance hunt groups).
Ed. 01 / 19 May 2011
TC1479
OmniVista 4760
5.2.01.03.d - RELEASE 5.2
APPENDIX 3
ADVANCED MANAGEMENT
TC1479
10
Ed. 01 / 19 May 2011
OmniVista 4760
APPENDIX 4
NEW FEATURES

5.2.01.03.d - RELEASE 5.2
NEW FEATURES
CONTENTS
New R5.1 Features
1.
INFRASTRUCTURE........................................................................3
2.
AUDIT..........................................................................................3
3.
ALARMS.......................................................................................3
4.
DIRECTORY..................................................................................3
5.
SECURITY ....................................................................................4
5.1. Last login date ............................................................................................ 4

5.2. LDAPS Protocol ........................................................................................... 4
New R5.1.1 Features
1.
INFRASTRUCTURE........................................................................5
2.
DIRECTORY..................................................................................5
3.
AUDIT..........................................................................................5
4.
REPORTS......................................................................................5
5.
MAINTENANCE ...........................................................................6
6.
SIP MANAGER .............................................................................6
New R5.2 Features
1.
INFRASTRUCTURE........................................................................7
Ed. 01 / 19 May 2011
TC1479
OmniVista 4760
5.2.01.03.d - RELEASE 5.2
APPENDIX 4
NEW FEATURES
2.
TC1479
MAINTENANCE ...........................................................................7
Ed. 01 / 19 May 2011
OmniVista 4760
APPENDIX 4
NEW FEATURES

5.2.01.03.d - RELEASE 5.2
New R5.1 features

1.
INFRASTRUCTURE
OmniVista 4760 server has been tested and validated for 30.000 users on a VMWare ESX Virtual
Machine.
2.
AUDIT
The application handles now "system" actions (linux commands) from OmniPCX Enterprise.
Data is coming from the following files:
\var\log\auth.log
\var\log\shell.log
Note
The Reports application can only generate reports for PCX configuration data (MAO).
3.
ALARMS
Some old OmniPCX Enterprise versions keep for a long time some no more valid alarms that were
downloaded at every synchronization.
It is now possible to manage the 4760 server so that it will not save alarms older than x days.
This parameter is common to all the OmniPCX Enterprise.
System
Directory\Server_Name\Servers\Server_Name\AlarmServer\specific\
Process Limit for OXE/4400 incidents (days).
The default value -1 means that no filter is applied.
4.
DIRECTORY
It is now possible to replicate one or several branches (country, city, company, department) from a
master server to a client one.
The client update needs to be scheduled. It is not done on the fly.
The replication management is accessible from the Company directory (Preferences menu).
Ed. 01 / 19 May 2011
TC1479
OmniVista 4760
5.2.01.03.d - RELEASE 5.2
APPENDIX 4
NEW FEATURES
5.
SECURITY
5.1.
Last login date
The date of the last login is saved for every manager on the following path:
Company Directory\Manager Name\Individual\Last Login Date.
One can use the search filters to find all the last login dates.
5.2.
LDAPS Protocol
The dialog between one R5.1 client and the server uses the LDAPS secured protocol on the default
port 636.
External applications can use either LDAP or LDAPS.
TC1479
Ed. 01 / 19 May 2011
OmniVista 4760
APPENDIX 4
NEW FEATURES

5.2.01.03.d - RELEASE 5.2
New R5.1.1 features
1.
INFRASTRUCTURE
Support of OmniPCX Enterprise R9.1;
2.
DIRECTORY
When creating an OmniPCX Enterprise in System directory, the FTP

Password fields are automatically completed (adfexc/adfexc).
Username and FTP
This account will be used to create the /usr4/tmp/ov4760 folder which contains information used
for check of license. This account is only allowed to write in this directory.
If the FTP account is modified, the check of license process fails and generates alarms. If the
problem is not resolved in time, the system can switch to restricted operating. Being informed that
data automatically when creating the PCX, limit the risk of error at this level.
3.
AUDIT
The application displays connection information of clients to the server and the access to
Accounting and Reports applications which contain confidential information.
The synchronization of PCXs can be launched from Audit application.
Time/Date stamp of exported files on the server.
The grid of System tab displays by default only the activities containing commands performed
by the PCXs.
The purge of data is based on the date of actions and not depending on the date of entry into
the base.
New columns in System grid: "Process Id" and "Details".
4.
REPORTS
Two new predefined Audit reports are available:
Connection of clients to server.
Access of clients to Accounting and Reports applications.
Ed. 01 / 19 May 2011
TC1479
OmniVista 4760
5.2.01.03.d - RELEASE 5.2
APPENDIX 4
NEW FEATURES
5.
MAINTENANCE
Downloading application of PCX versions:
It is possible to define the starting date and duration of period when the transfers of version are
allowed between OmniVista 4760 to OmniPCX Enterprise. This allows for transfers outside of
working hours.
It is possible to define the maximum number of simultaneous downloads. This is the number of
simultaneous FTP transfers of the version from 4760 to the Masters
Administrator can configure this attribute to make software download job to run in batches for large
PCX networks.
For example, if number of parallel software download attribute value is 10 and there are 200
master PCXs in the network and duration configured is 5 hours, then job will start with 10 master
PCX. Once finished with first 10 PCXs, we will check if it is in the timeframe allowed for the transfer.
If so, it starts the transfer to the 10 following PCX masters. Transfers will continue if necessary until
the end of the period allowed. After this period, if there are transfers to perform the task will be
paused and will be automatically scheduled the next day at the same time.
The "Software Update Status" has been improved.
All the information is now available from a unique window.
6.
SIP MANAGER
Management of Alcatel-Lucent 4008 and4018 sets.
TC1479
Ed. 01 / 19 May 2011
OmniVista 4760
APPENDIX 4
NEW FEATURES

5.2.01.03.d - RELEASE 5.2
New R5.2 features
1.
INFRASTRUCTURE
Support of OmniPCX Enterprise R10.0 and OmniPCX Office 8.0
Support of Windows 2008 and Windows 7 64 bits
New language: Arabic
2.
MAINTENANCE
OmniVista 4760 R5.2 software downloading.
OmniVista 4760 R5.2 supports the parallel download from Master PCX to Client PCX. This
feature is available from OXE R9.1 release onwards.
This feature will work only for the master PCXs which are either Appliance Server or Blade
Server having R9.1 release and above. There is no change in the status files.
Ed. 01 / 19 May 2011
TC1479
OmniVista 4760
5.2.01.03.d - RELEASE 5.2
APPENDIX 4
NEW FEATURES
TC1479
Ed. 01 / 19 May 2011
OmniVista 4760
APPENDIX 5
RESTRICTIONS AND IDENTIFIED DEFAULTS

5.2.01.03.d - RELEASE 5.2
CONTENTS
1.
INFRASTRUCTURE........................................................................3
2.
CONFIGURATION .......................................................................4
3.
DIRECTORY..................................................................................4
4.
INSTALLATION ............................................................................5
5.
MAINTENANCE ...........................................................................5
6.
SCHEDULER.................................................................................6
7.
ACCOUNTING.............................................................................6
8.
REPORT .......................................................................................6
9.
REPLICATION ..............................................................................6
10. SIP DMS.......................................................................................6

11. PROXY SNMP ...............................................................................7
12. OTHER.........................................................................................7
Ed. 01 / 19 May 2011
TC1479
OmniVista 4760
5.2.01.03.d - RELEASE 5.2
APPENDIX 5
TC1479
Ed. 01 / 19 May 2011
OmniVista 4760
APPENDIX 5

5.2.01.03.d - RELEASE 5.2
1.
INFRASTRUCTURE
Installation
The identifiers of Experts groups must not have accents.
Using a Web administration client on XP SP2 with firewall activated
The default automatic firewall configuration is only performed on standard 4760
client. If you are using the Web applet, you need configure manually the XP firewall
and add the Corba port 30500 to 30509 on the XP client.
Path of installation for Sybase binaries
Do not install Sybase directly on the drive root (D:). In that case, if 4760 is
uninstalled, all data on D: will be removed.
Recommendation
Use C:\Program Files or C:\Program Files (x86) default folder to install
Sybase.
Refer to technical communication TCV056 Complete erasing of hard disk following
OmniVista 4760 uninstallation
Sybase software must not be installed in the same directory as OmniVista 4760; the
upgrade of server would fail.
Firefox limitation
If Firefox 1.0 is your default browser, you cannot launch the external application
that use Default Browser setting.
In technical (system) directory, in General tab, under NMC>Application>
External Applications, the default setting of the browser has to be replaced
by:
Type= Windows application <Name of the binary> = C:\Program
Files\Mozilla Firefox\firefox.exe
SP1 installation on Windows 2003 Server
Some PCs, especially the HP ML370G4, require a Bios and some drivers update
before Windows 2003 Server SP1 patch installation. Otherwise the update
procedure would fail and the only solution would be to reinstall the operating
system. It's mandatory to have a 4760 data backup on a remote device. Refer to the
technical communication TCV066 Installation of Service Pack 1 for Windows 2003
over a HP/Compaq ML370 server will end in a definitive crash of the PC and all
data will be lost.
Step mandatory before to install OmniVista 4760 R5.2 under Windows 2008 and Windows
7 (at minimum, verify if the field has the correct value)
If Sybase related libraries (like dbsrv10.exe) are not getting installed in Windows 7 &
Windows 2008 physical servers and VMware sessions so we must to do the
Ed. 01 / 19 May 2011
TC1479
OmniVista 4760
5.2.01.03.d - RELEASE 5.2
APPENDIX 5
following workaround to make it available for installation; changing the value to

zero and click OK. Steps are given below.
- On a Windows 7 box (and possibly on a Windows 2008 R2 box), the following
registry key needs to be changed prior to installing 8770:
Start the registry editor
Go to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem
folder.
Double-click on the NtfsDisable8dot3NameCreation value, type the
number 0 in the Data box, and then click OK.
Reboot the server.
Server Migration
The migration of server is not possible.
For example: impossible to migrate a 4760 on Windows 2003 to Windows 2008 or
Windows 7.
2.
CONFIGURATION
USB modems are not supported on 4760 Server

Software download: 4 simultaneous downloads max
XTSce46865
The first key typed just open the edit mode. The first character is not written in the
field.
crms00154884 Scheduler status for PCX users export is "failed" although the export is correct / 192953253.
3.
DIRECTORY
XTSce85390
Web directory: add edition ergonomics for Confidentiality field.
crms00192881 This is a system restriction
In the System Directory, the upper value for the Network number is 2140. Although
there is neither warning nor restriction when managing this field, a greater value
will lead to an error during Accounting Counter Calculation:
"Accounting: 233: 23502: com.sybase.jdbc2.jdbc.SybSQLException: Erreur SQL
Anywhere -195: the column 'PbxId' of the table 'EntityInfo' can not contain the value
NULL"
crms00280605 Impossible to change the language for the web directory.
TC1479
Ed. 01 / 19 May 2011
OmniVista 4760
APPENDIX 5

5.2.01.03.d - RELEASE 5.2
Add the URL to the "Trusted Site" list in the browser.

crms00281819 Issue when consulting the web directory: when you select one element of the
organisation tree in the company directory you should when clicking on research
tab make the search from this element and this is not the case until "Creation of
entries authorized" is not validated
(System directory\NmcConfiguration\GlobalPreferences\DirectoryClient\GlobalParameters)
4.
INSTALLATION
XTSce96481
Bad Server uninstallation / Some remaining registry keys / 1-93130151 (dup

XTSce88029/87330/crms00184577).
Svc_mgr is not removed from the registry.
crms00101845 4760 R4.2/Server uninstall: Displayed remaining time is totally erroneous / 183372904.
crms00183159 4760 R5.0/ Installation/Button activation failure. See patch log.
5.
MAINTENANCE
PCX versions before E2.504 (UNIX versions) do not accept the backup commands sent by OmniVista
4760.
For these versions, OmniVista 4760 can only recover the mao-dat and cho-dat files daily created
by the PCX in the /usr4/BACKUP/DAY directory.
The files created by the PCX immediate backup command can no more be recovered by OmniVista
4760 Maintenance application.
A possible backup can be carried out by a "manual" FTP transfer.
Software Download
Starting from OmniPCX Enterprise R9.1, intermediate log files for a software update are managed
differently:
Before R9.1:
A unique SofwareUpdatestus_X file in the /var/ftp/pcx/logs folder.
(X=context Id)
Starting from R9.1:

Several files are created in the /tmpd/soft_install folder:
SofwareUpdatestus_X_1 (log for the remote load operation)
SofwareUpdatestus_X_Y (one file per installed client)
Ed. 01 / 19 May 2011
TC1479
OmniVista 4760
5.2.01.03.d - RELEASE 5.2
APPENDIX 5
In both cases the final SofwareUpdatestus_X_end file is located in the /var/ftp/pcx/logs

folder.
Following this modification, OmniVista 4760 versions before R5.1.06.03.c are no more able to
retrieve intermediate logs during an update for PCX starting from R9.1.
6.
SCHEDULER
crms00199798 Scheduler status for PCX users export is "failed" although the export is correct / 1102115641.
7.
ACCOUNTING
crms00192703 Accounting tickets restore function not working fine/1-00688885

When restoring tickets for a period, the available PCX list is sometimes incorrect
or unavailable.
The solution is to use the option for one day and then to select the files to restore
in the list. All the files to restore can be previously saved in a single folder.
8.
REPORT
crms00285308 The export in pdf format using Arabic language is not supported.
9.
REPLICATION
crms00287377 GUI tab issue on replication application: "ST_REPLICA-ALL" instead of "Replicate

ALL".
10. SIP DMS

SIP Device Management Server must have the version 1.2.000.010 or higher to be compatible with
OmniVista 4760 R5.2. The current version is 1.2.000.020.
SIP DMS is not compatible with Windows 2008 and Windows 7.
TC1479
Ed. 01 / 19 May 2011
OmniVista 4760
APPENDIX 5

5.2.01.03.d - RELEASE 5.2
11. PROXY SNMP

Not available with Windows 2008 and Windows 7.
12. OTHER
Concerning new feature: Arabic language:
Each user can choose Arabic language in the list of OmniVista 4760 client
languages. Other users can choose other languages (like English) on the same
server.
Restrictions:
No ergonomics change: translation in Arabic, but no change in the screens
display (from left to right)
Configuration: Content of the OXE object model is in the OXE installation
language
Alarms: Diagnosis of the alarms in the OXE language
Audit: content of the logs (object, action) in the OXE language
Reports: export on pdf not supported
For Name/Surname displayed in Arabic on the 8000 & 9000 series phone sets
As of OXE 9.1 latest version, the language can be chosen for each phone set,
from the phone set MMI or from OmniVista 4760 Configuration
The Arabic names are managed in OmniVista 4760 Configuration. Arabic
characters appear from right to left, aligned on the left.
Once a name is set up in Arabic, it is displayed in Arabic on all the OXE
phone sets
Names/surnames in Arabic (UTF8) are not synchronized in the OmniVista
4760 web Directory.
Only the English (non UTF8) names/surnames are synchronized. It
means that, for the web Directory or the Call by name overflow,
names should be created in Arabic and in English as well for the
Directory.
Modification of English names is synchronized between OXE and the
Directory, but modifications in Arabic names should be made on both
sides.
Ed. 01 / 19 May 2011
TC1479
OmniVista 4760
5.2.01.03.d - RELEASE 5.2
APPENDIX 5
TC1479
Ed. 01 / 19 May 2011

TC1479en - Installation Procedure For Version R5.2.01.03.d

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

TC1479en - Installation Procedure For Version R5.2.01.03.d

Uploaded by

Copyright:

Available Formats

TECHNICAL COMMUNICATION

Date : 19 May 2011

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Ed. 01 / 19 May 2011

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Ed. 01 / 19 May 2011

Ed. 01 / 19 May 2011

Ed. 01 / 19 May 2011

Ed. 01 / 19 May 2011

NON STANDARD FEATURES

4760 client with Citrix for OmniPCX Office management.

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

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

CONTENT OF THE SOFTWARE PACKAGE

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

OmniVista 4760 Installation manual

: 3BH 19261 ed. 16

SIP Device Management Installation manual

: 8AL 90701 ed. 01

: 8AL 90700 ed. 01

Documentation CD: 3BH 11630 AKAA which contains :

: 3BH 19260 ed. 15

OmniVista 4760 Installation manual

: 3BH 19261 ed. 15

SIP Device Management Installation manual

: 8AL 90701 ed. 01