Sie sind auf Seite 1von 30

TECHNICAL COMMUNICATION No. TCV039 Ed.

07

OmniVista 4760 Nb of pages : 30 Date : 25 October 2007

URGENT

NOT URGENT TEMPORARY PERMANENT

SUBJECT : OmniVista 4760 LICENSES

CONTENTS

1. GENERAL.....................................................................................3
1.1 Principle.................................................................................................... 3
1.2 Generating the license file ........................................................................ 3
1.3 Name of the file........................................................................................ 4
1.4 History ...................................................................................................... 4

2. CONTENT OF THE FILE ................................................................5


2.1 OmniVista version .................................................................................... 5
2.2 4760 identifier .......................................................................................... 6
2.2.1 OmniPCX Office................................................................................................6
2.2.2 OmniPCX 4400 R3.0 to R5.0 .............................................................................6
2.2.3 OmniPCX Enterprise R5.0 Lx ..........................................................................7
2.3 Type of managed PCX............................................................................... 7
2.4 Modules.................................................................................................... 7
2.5 Number of users....................................................................................... 8
2.5.1 OmniPCX 4400/Enterprise ................................................................................8
2.5.2 OmniPCX Office................................................................................................9
2.6 Number of Client PCs ............................................................................. 10
2.7 Example of OmniVista 4760 R4.2 license file .......................................... 10

3. CHECKING THE LICENSE ...........................................................11


3.1 Restricted mode ...................................................................................... 11
3.2 Presence of the file ................................................................................. 11
3.3 Presence of attachment PCX.................................................................... 11
3.4 Global synchronization ........................................................................... 12
3.4.1 Principle..........................................................................................................12
1
3.4.2 Launching the synchronization in restricted mode ..........................................14
3.5 Number of users..................................................................................... 15
3.6 Number of client PCs .............................................................................. 16
3.7 Use of the same license on two OmniVista 4760 servers ........................ 17

4. MODIFYING THE LICENSES........................................................20


4.1 Changing manually the licenses ............................................................. 20
4.2 Modifying the capacity / Adding the module .......................................... 20
4.3 Changing the CPU .................................................................................. 20
4.4 Migrating OmniPCX 4400 to OmniPCX Enterprise................................... 20
4.5 Migrating the OmniVista 4760 version ................................................... 20

5. SOFTWARE LOCKS ON OMNIPCX 4400/ENTERPRISE .................22

6. PROBLEMS AND SOLUTIONS .....................................................23


6.1 Alarms of licenses................................................................................... 23
6.2 Client PC connection ............................................................................... 25
6.3 Alarms .................................................................................................... 28
6.4 Configuration ......................................................................................... 28
6.5 Tickets..................................................................................................... 29
6.6 New license ............................................................................................ 30
OmniVista 4760
OmniVista 4760 LICENSES

1. GENERAL

1.1 Principle
OmniVista 4760 is a client server application. Client PCs get a license token from the server. Only
the server requires a license file during installation.
A 4760 license:
is specific for your PBX network,
is sized according to the user capacity of that network, number of client PCs,
describes the available OmniVista 4760 modules,
is permanent or temporary with an exact date of end of validity (example : 31/12/2004).
This license is based on the Actis/eLP configuration of one Alcatel PCX. When running, OmniVista
4760 server will connect to this PCX to launch an hardware check, this enable license validation.
Such PCX is called attachment PCX.
To use OmniVista 4760 module, it is necessary to open, on all the managed PCX the relevant
licenses.
To install a second OmniVista 4760 server (backup server, modules split on different servers), a new
license should be generated on another attachment PCX.

The permanent control of licenses by the server can generate information messages
as well as alarms during the launching of a client customer.
It is very important to take into account this information and if necessary to bring
the corrective measures.
If these recommendations are not respected, the system will operate in restricted
mode.
The fitter of the system must sensitize the final administrator on this crucial point for
the continuity of OmniVista 4760 service.

1.2 Generating the license file


This file is generated by eLP, server of licenses available on Business Partner Web Site (BPWS). eLP
takes into account:
the historic of the site: new installation or addition,
the license requirements.
The information of the functional OmniVista 4760 requirements is subjected either directly in eLP or
via an Actis configuration.
Using Actis, and only for OmniPCX 4400 or Enterprise :
1 Select one of PCXs of the network.
2 Specify in its configuration that it is a declaration node of 4760 server.

Ed. 07 / 25 October 2007 3 TCV039


OmniVista 4760
OmniVista 4760 LICENSES

3 Order the software and licenses.


The licenses are generated by eLP.
4 Generate the MAO files to provide the 4760 license file.
5 Launch an MAO export.
Using eLP (via BPWS) :
1 Order the software and licenses.
2 Download the 4760 license file.
Note
Since July 2006, there is no more any 4760 license diskette supplied by Alcatel. You need to provide
the license file by yourself either by accessing to eLP site and retrieving your license or by Actis tool,
by exporting the MAO file and 4760 license.

1.3 Name of the file


This file is named XXYYYAAe.sw4760, when it is provided by eLP/Actis.
When installing the OmniVista 4760 server:
the installation program requires a file with *.sw4760 extension,
then this file is copied in the \4760\etc sub-directory and renamed nmc.license.
The upgrades of licenses are carried out on the 4760 server by replacing this file.
Note
XXYYYAAe is the reference of Actis configuration of the PCX.

1.4 History

Releases Evolution
R1.0 Actis sets a capacity = 110% requested capacity
R1.5 Handle4760 check is operational on OmniPCX Enterprise R5.0
R2.0 OmniPCX Office CPU-Id check is operational on OmniPCX Office R2.0
Actis sets a capacity = requested capacity
Server can operate up to 110% of the license capacity
R3.0 Failure delay for license is extended from 21 days to 32 days
R3.1
R3.2 OmniPCX Office: Improved check of user capacity
OmniPCX 4400: If attachment node is still OmniPCX 4400 R5.0 Ux, Actis tool will
limit all OmniVista 4760 orders to OmniVista 4760 R3.2
R4.0 and The same OmniVista 4760 license cannot be used on 2 different servers, a
above separate order for the second one must be placed
Client switch to restricted mode when license limit is reached
Actis tool cannot generate a license based on OmniPCX 4400 hard key. However
for maintenance reason, you can update to OmniVista 4760 R4.0 using a license
that include hard key value

TCV039 4 Ed. 07 / 25 October 2007


OmniVista 4760
OmniVista 4760 LICENSES

2. CONTENT OF THE FILE

2.1 OmniVista version


The major commercial OmniVista versions are named RX.Y. In-house, these versions match an id of
version 1, 2, 3, etc. The technical versions, named RX.Y.Z.T.u, use the same id of license like version
RX.Y. If you have 4760 license file with an id "N", you can install a server requiring normally the
license version of id "N+1".
Examples

Existing Release Change to Change to


R3.2 (License version = 7) R4.0 (License version = 8) R4.2 (License version = 10)
No change of license Change of license
R4.0 (License version = 8) R4.1 (License version = 9) R4.2 (License version = 10)
No change of license Change of license
R4.1 (License version = 9) R4.2 (License version = 10)
No change of license

CAUTION
This operation is reserved for maintenance needs (to solve a known issue). You still need to update
the license to take into account a new PCX version or a new 4760 feature.

Commercial Release Released Version Id of version Compatible Id


R1.0 R1.0.28.05a 1 1
R1.0.28.07b
R1.5 R1.5.08.00c 2 2
R1.5.08.00d
R1.5.09.00a
R2.0 R2.0.12.01d 3 3
R2.0.12.01d-5
R2.0.12.01e
R2.0.13.00c
R2.1 R2.1.13.01b 4 3 and 4
R2.1.14.00b
R2.1.15.01a
R2.1.16.00b
R2.1.17.00b
R3.0 R3.0.15.00c 5 4 and 5
R3.0.16.00b
R3.1 R3.1.07.00c 6 5 and 6
R3.2 R3.2.04.00a 7 5, 6 and 7
R3.2.05.00b
R4.0 R4.0.11.01a 8 7 and 8
R4.0.12.01.c
R4.0.12.01.d
R4.1 R4.1.08.00.c 9 8 et 9
R4.1.12.00.b
R4.1.13.00.a

Ed. 07 / 25 October 2007 5 TCV039


OmniVista 4760
OmniVista 4760 LICENSES

Commercial Release Released Version Id of version Compatible Id


R4.2 R4.2.06.02.a 10 9 and 10

2.2 4760 identifier

2.2.1 OmniPCX Office

The OmniVista 4760 license is based on the number of OmniPCX Office CPU-Id. To find it, consult:
the Business Partner Web Site,
the board of labels which was delivered with the cabinet,
the original packaging,
your invoice.
The technician can also find the number of CPU-Id via:
the options of attendant set,
its PM5 configuration tool, installed to configure the system,
the CPU board; for that, the system must be turn-off.
Note
The OmniPCX Office CPU-Id is changed thereafter, regenerate a new OmniVista 4760 license.
IMPORTANT
The check of attached node requires an OmniPCX Office versions 2.0. As CPU-Id is not available
for OmniPCX Office versions < 2.0, OmniVista 4760 cannot check the attached node declared in its
license.

2.2.2 OmniPCX 4400 R3.0 to R5.0

The OmniVista 4760 license is based on the number of hard keys. To find it, consult:
the Business Partner Web Site,
the Actis installation folder.
The technician can also find the number of hard key(s) via:
the CPU board; for that, the system must be turn-off,
its spadmin tool,
under telnet, launch spadmin
select the option 2 Display active File
note the values of HardKey1 and HardKey2
Example
Hard Key1=DDF7, Hard Key1=BAC5
Note
The hard keys cannot be changed.

TCV039 6 Ed. 07 / 25 October 2007


OmniVista 4760
OmniVista 4760 LICENSES

2.2.3 OmniPCX Enterprise R5.0 Lx


The OmniVista 4760 license is based on the value of the Handle4760 field. To find it, consult:
the Actis installation folder.
The technician can find the value of Handle4760 via:
its spadmin tool,
under telnet, launch spadmin
select the option 2 Display active File
note the value of Handle4760
Example
0000875c
Note
To retrieve easily a OmniVista 4760 license, the Handle4760 is initiated with the value of the very
first CPU-Id then, when the OmniPCX Enterprise CPU is changed (so new CPU-Id), the value of
Handle4760 is retained in PCX license and OmniVista 4760 license. There is no need to replace the
OmniVista 4760 license.

2.3 Type of managed PCX


The OmniVista 4760 server uses this information to authorize or not the management of PCX of the
Alcatel Office, OmniPCX Office, OmniPCX 4400, OmniPCX Enterprise type.
In the case of heterogeneous network, here the rules to be followed to authorize the management of
all PCXs:

Heterogeneous Network Attachment of the license to


4400 & Enterprise 4400 or Enterprise
4400/Enterprise & OmniPCX Office 4400 or Enterprise
4400/Enterprise & 4200 4400 or Enterprise
OmniPCX Office & 4200 OmniPCX Office

CAUTION
As of release OmniVista 4760 R4.0, you cannot generate license with hard key. Hence, the
attachment PCX cannot be in OmniPCX 4400 release R5.0 Ux

2.4 Modules
The following modules are not subject to a specific license:

Directory System part and management of administrator accounts


Alarms Internal alarms of server
Scheduler Lists of scheduled jobs
Maintenance Save and restore
Report Report on alarms, accounting, traffic observation, VoIP

Ed. 07 / 25 October 2007 7 TCV039


OmniVista 4760
OmniVista 4760 LICENSES

On OmniPCX 4400 and Enterprise, the following licenses can be ordered:

Configuration Graphic Interface of configuration


Alarms Alarms of PCX
Topology Topology of PCX network and associated alarms
Accounting Accounting
AccountingMonitoring Monitoring of accounting, traffic and VoIP
PastTimePerformance Traffic observation
Directory Management of company directory
VoIP IP tickets
Ticket Collector Make available the accouting tickets and IP for third application
Security Secured SSH connectivity between 4760 server and OmniPCX Enterprise
RSC Give access to multicompanies features

On OmniPCX Office, the following licenses can be ordered:

Configuration Proxy of connection, requires PM5 locally


Alarms Alarms of PCX
Topology View of PCX on a map and associated alarms
Accounting Accounting
AccountingMonitoring Accounting monitoring

2.5 Number of users


The following capacities are sold:
0 or 250 : basic capacity,
10 or 100 : additional capacities.
The 100-additional is only available from a 250-basic capacity.
The 10 and 100 capacities can be mixed.
The global capacity is based on the quantity of user sets. All users of the PCX network have to be
taken into account in the capacity calculation. For sites with more than 30000 users, make a PCS
request (Premium Customer Support). The licenses will be delivered by this specific procedure.

2.5.1 OmniPCX 4400/Enterprise

Users capacity is calculated by Omnivista 4760 by searching the number of users synchronised in
the system directory. You need to:
Take into account the virtual users.
In case of Hotel/Hospital installations, virtual user (room) is replicated in the network. It must be
taken into account on each network node.
One exception on OmniPCX 4400/Enterprise: do not count having simultaneously the three
following characteristics:
analog set,

TCV039 8 Ed. 07 / 25 October 2007


OmniVista 4760
OmniVista 4760 LICENSES

accounting category: not justified,


equipment addresses set to 255.

2.5.2 OmniPCX Office

The users capacity comes from a request to OmniPCX Office which send the number managed
users. When the max capacity is reached, it becomes impossible to use any client. The OmniVista
license needs then to be updated. In case, you disagree with this quantity, analysis must be
performed on PCX side.
List of interfaces/terminals which will be counted
Reflexes terminals.
All UA accesses dedicated to a specific terminal (UA 2G, UA3G, IP Touch terminals, terminal
adaptor, TA, etc.).
Mobile terminals.
All DECT accesses dedicated to a specific terminal including GAP terminals (Mobile 100 Reflexes,
Mobile 200 Reflexes, etc.).
IP terminals including IP PIMPhony users (PC Multimedia).
IP terminal (First/IP, Easy/IP, Premium/IP, Advanced/IP, IP Touch 4018/IP, 4028/IP, IP Touch
4038/IP, IP Touch 4068/IP, etc.).
Analog accesses.
ISDN terminals.
S0 subdevice (4094).
List of interfaces/terminals which will be not counted
UA accesses not dedicated to a specific terminal.
IP accesses not dedicated to a specific terminal.
DECT accesses.
All the virtual sets (included Nomadic).
Integrated modem V34.
Integrated modem V24.
Voice Mail Unit.
Internet Access.
Remote Access ISDN.
The administrator has always the possibility to delete or erase any account associated with a terminal
when no effective terminal is connected. The counting is decreased respectively and taken into
account in OmniVista 4760 by next synchronization.
CAUTION
There is an issue OmniPCX Office R410 side that causes the counting of the ACD groups as users
by OmniVista 4760 R4.0 and R4.1.
To fix this issue, apply the patch "4760 R4.1.13 + patch XTScf00842".

Ed. 07 / 25 October 2007 9 TCV039


OmniVista 4760
OmniVista 4760 LICENSES

2.6 Number of Client PCs


Only the administrator clients of 4760 server are counted.
Especially, do not forget to count:
the client launched on the server PC,
the administrator clients accessing the server via the Intranet.
The number of simultaneous client PCs is 15.

2.7 Example of OmniVista 4760 R4.2 license file


;
; Omnivista 4760 License File
;
[4760]
Version = 10
4760OfferNumber = 20060905090556123
Signature = gwa3B2gr/Iel/2pjjOKHrg==0Gu0zizoa1r8s9tfKq43pg==
RSC = 1

[ALIZE]
Management = 1

[A4400]
Management = 1
4760Handle = 0000875c

; list of applications and capacities


[Modules]
Configuration = 15000
Alarms = 15000
Topology = 1
Accounting = 15000
AccountingMonitoring = 1
PastTimePerformance = 15000
VoipPerformance = 15000
Directory = 15000
NmcClients = 10
Security = 1
TicketCollector = 15000

TCV039 10 Ed. 07 / 25 October 2007


OmniVista 4760
OmniVista 4760 LICENSES

3. CHECKING THE LICENSE

3.1 Restricted mode


When an alarm of license reaches the critical state, the server passes in restricted mode. According
to the OmniVista 4760 versions, this mode has a different impact.
Up to OmniVista 4760 R3.2, the client connections are completely blocked, you should update the
license file or solve the issue with other tools (force the synchronization with ntsvcclient.exe tool
(see section Launching the synchronization in restricted mode), type the attachment PCX with
dirmanag.exe, ...)
From OmniVista 4760 R4.0, the client can connect in restricted mode. Only the system directory and
the scheduler are accessible.

3.2 Presence of the file


If the nmc.license file is not found on the server, the nmclicserver service cannot enable the
license.
In Windows Explorer:
go to the 4760\etc directory,
right click to display the properties of the license file,
check the name and the extension of the nmc.license file. The extension must be .license
and not .license.txt.

3.3 Presence of attachment PCX


The checking stages are:
At the beginning, the server will identify which PCX is the attachment PCX and will mark the
Declaration node (license control) information on the level of the PCX declaration (system
directory).
Thereafter, every 24 hours, the server checks on the attachment PCX the 4760identifier. It must
be the same both sides.
In the event of repeated failure of check, the server generates alarms of increasing gravities and
ends up blocking the client accesses. More precisely:

Ed. 07 / 25 October 2007 11 TCV039


OmniVista 4760
OmniVista 4760 LICENSES

At the end of 8 days A warning alarm


At the end of 16 A major alarm
days
At the end of 24 A critical alarm
days
At the end of 32 Up to R3.2
days The client application can no longer connect and the server replies No
license for this PCX network
From R4.0
The client passes in restricted mode. The following message is displayed
during the client connection:

If the check becomes again positive, the client application goes back in normal mode and the
day meter without key check passes by again to zero.
With the Help\About menu, you can check the name of the attachment PCX as well as its identifier.
These stages are stored in the 4760\log\nmclicserver_X.log file.

[16/09/2003 05:32:16] 1104 LicServer: There is not associated PBX.


[17/09/2003 05:32:49] 1104 LicServer: Trying to find the associated PBX...
[17/09/2003 05:32:49] 1104 LicServer: Checking key of PBX
'SubnetworkNodeNumber=1101, SubnetworkNumber=11, NetworkNumber=10, o=nmc'...
[17/09/2003 05:32:50] 1104 LicServer: It is the associated PBX!
[18/09/2003 05:34:12] 1104 LicServer: Checking key of PBX
'SubnetworkNodeNumber=1101, SubnetworkNumber=11, NetworkNumber=10, o=nmc'...
[18/09/2003 05:34:12] 1104 LicServer: PBX key is right!
...
[22/12/2003 11:56:36] 540 LicServer: WARNING
Checking time for last PBX key/ control: first threshold (8 days) crossed!
Days for last control: 8

3.4 Global synchronization

3.4.1 Principle

To count the number of users compared to that allows the license, the 4760 server uses the global
synchronization of all the PCX networks declared in the system directory. This synchronization must
thus be generated on the level of the NMC entry of the system directory.

TCV039 12 Ed. 07 / 25 October 2007


OmniVista 4760
OmniVista 4760 LICENSES

Do not confuse global synchronization and complete synchronization.

By default, the global synchronization jobs are already set in the scheduler:
in OmniVista 4760 Releases 1.0 et 1.5, they are the jobs of complete and partial
synchronization,
in OmniVista 4760 Release 2.0, these jobs of synchronization are carried out during the weekly
and daily works.
The checking stages are:
Every 24 hours (from the start of services, the server checks if there was a global synchronization,
In the event of repeated failure of check, the server generates alarms of increasing gravities and
ends up by blocking the client accesses. More precisely:

At the end of 8 days A warning alarm


At the end of 16 days A major alarm
At the end of 24 days A critical alarm
At the end of 32 days Up to R3.2
The client application can no longer connect and the server replies
The license server denied the connection
From R4.0
The client passes in restricted mode

If the check is restored, the client application goes back in normal mode and the day meter
without key check passes by again to zero.
These stages are stored in the 4760\log\nmclicserver_X.log file.

[09/20/2003 01:45:11 AM] 1064 LicServer: Synchronisation of LDAP server with all
networks is starting
...
[09/21/2003 01:46:28 AM] 3648 LicServer: Program starting
[09/21/2003 01:46:28 AM] 3648 LicServer: time for last synchronization of LDAP
server with all networks: 1440 minutes (1 days)
...
[20/01/2004 15:10:37] 456 LicServer: time for last synchronization of LDAP
server with all 4400: 46784 minutes (32 days)
[20/01/2004 15:11:39] 456 LicServer: Procent of max subscriber: 252/375 = 67%
[20/01/2004 15:11:40] 456 LicServer: Error: Checking time for last
synchronization of LDAP server with all 4400: too many days (32) without
synchronization!
[20/01/2004 15:11:40] 456 LicServer: CRITICAL
Checking time for last synchronization of LDAP server with all 4400: third
threshold (30 days) crossed!
Days for last synchronization: 32
Check that synchronization of LDAP server with all 4400 is periodically
scheduled.

Ed. 07 / 25 October 2007 13 TCV039


OmniVista 4760
OmniVista 4760 LICENSES

3.4.2 Launching the synchronization in restricted mode

A global synchronization is a synchronization launched on the nmc entry of the system directory. It
must not be confused with a complete synchronization.
When the global synchronization has not been carried out for more than 31 days, the client cannot
be used anymore. As of release OmniVista 4760 R4.0, you can launch synchronization within 4760
client (restricted mode). In previous release, it is necessary to launch synchronization directly by
accessing the 4760 synchronization service NMCSynchldapPPX.
OmniVista 4760 / PCX manual synchronization
1 Launch the 4760/bin/ntsvcexClient.exe program.
2 Open a Corba connection towards a 4760 service:
under this tool, open the File/Open menu
validate Registry search
set the hosts = IP address of 4760 PC
select the SynchldapPPX service
validate the connection to service of synchronization: click on OK,
3 Require a synchronization:
in the tree, select the SynchldapPBX entry
double click on Complete load
select the tk_string type
click on OK,
in the Edit Property window, enter the value 1 in the Value field,
click on OK,
4 Wait the end of the synchronization by consulting regularly the
4760\log\NMCSynchldapPBX_x.log file
5 Reboot the OmniVista 4760 server.
Check the scheduled jobs
If the weekly and daily synchronizations are no more scheduled, restore the default jobs. These jobs
carry out global synchronization.
With OmniVista 4760 Releases 1.0 and 1.5, recreate a scheduled synchronization:
1 Open the system directory.
2 Right click on the NMC entry.
3 Select complete or partial synchronization.
With OmniVista 4760 Releases 2.0.13.01c and above, restore the weekly and daily jobs:
1 Open the scheduler.
2 Delete the entries Weekly and Daily.

TCV039 14 Ed. 07 / 25 October 2007


OmniVista 4760
OmniVista 4760 LICENSES

3 Open the system directory.


4 In the tree, right click import.
5 Select the directory 4760\data\scheduler on the server.
6 Import the Dailyjob.ldif and WeeklyJob.ldif files.
7 Reboot the server.

3.5 Number of users


The checking stages are:
the server checks if the number of users corresponds to the limits of the license.
This check is carried out:
after synchronization,
on start of service of license,
every 24 hours after the last check.
If the number is bypassed, the server generates alarms of increasing gravities and ended up by
blocking the client accesses. More precisely:

Beyond 80 % A warning alarm


Beyond 90 % A major alarm
Beyond 99 % A critical alarm
On 110% Up to R3.2
The client application can no longer connect and the server replies
Number of users bypassed
From R4.0
The client application passes in restricted mode. The following message is
displayed during the client connection:

Ed. 07 / 25 October 2007 15 TCV039


OmniVista 4760
OmniVista 4760 LICENSES

If the license is up to date, the client application will be able to be again connected in normal
mode to the server.
These stages are stored in the 4760\log\nmclicserver_X.log file.

11/10/2003 01:55:42] 3308 LicServer: Synchronization of LDAP server with PBX(s)


is finished.
[11/10/2003 01:55:54] 2620 LicServer: Procent of max subscriber: 125/250 = 50%
...
[12/10/2003 01:47:00] 1280 LicServer: Program starting
[12/10/2003 01:47:00] 1280 LicServer: time for last synchronization of LDAP
server with all networks: 1440 minutes (1 days)
[12/10/2003 01:47:00] 1280 LicServer: time for last PBX key control: 733 minutes
(0 days)
[12/10/2003 01:47:00] 1696 LicServer: Program running
[12/10/2003 01:48:00] 1696 LicServer: Procent of max subscriber: 125/250 = 50%

Note
In OmniVista 4760 Release 1.0, the margin of 110 % was calculated by Actis and the server checked
to 100 % the number of users in the license.
Thus during the migration from OmniVista 4760 R1.0 towards R2.1, the value of the user license
evolves.
Example: Management of 250 sets

Release Actis value Provided License 4760Check


R1.0 250 275 275
> R1.5 250 250 275

3.6 Number of client PCs


The checking stages are:
On each connection of an administrator client:
if there are enough available license, a token of client PC license is taken,
if there are no available licenses, the server replies Number of clients bypassed.
To release this token, the server checks regularly that the PC is always accessible.
At the end of 3 minutes, if the client PC does not reply, the server considers that it is
disconnected.
This mechanism is used to:
keep the client license if there was an accidental failure of network,
release the license if the client is disconnected in an unexpected way,
caution, if you ask a client to disconnect, it will be necessary to wait 2 to 3 minutes to be able to
use the license thus released.

TCV039 16 Ed. 07 / 25 October 2007


OmniVista 4760
OmniVista 4760 LICENSES

3.7 Use of the same license on two OmniVista 4760 servers


As of OmniVista 4760 R4.0, the server checks the unicity of the license. It detects the possible use of
a same license on an other server having the same attachment PCX.
The presence of two servers using the same license, with the same attachment PCX is acceptable
during a temporary period limited to 31 days.
For instance, if you need to install the OmniVista 4760 server on a new PC, you can decide to keep
the old PC and the new one running then after if the new one is fully operational, you remove the
old one.
If you need permanently to keep several servers 4760, you should place different order for each
4760 and get different license file.
If after 31 days, there are still 2 servers using the same license, an alarm on license failure will be
sent with increasing gravity. If you ignore all these warnings, and finally reach the exceeded gravity
of license failure, the system will turn into restricted mode. You will have to solve the issue by
providing separate license or closing the additional server.
More precisely:

At the end of 31 days A warning alarm


At the end of 51 days A major alarm
At the end of 71 days A critical alarm
At the end of 91 days An exceeded state, client go in restricted mode. In each stage, a
message is displayed when opening a client. It is important to solve
the conflict before turning into the restricted mode

Here are 2 examples of messages displayed when connecting the client:

Ed. 07 / 25 October 2007 17 TCV039


OmniVista 4760
OmniVista 4760 LICENSES

The return in normal mode will be effective only after a delay of 5 days of
functioning without conflict.

Associated logs
[28/10/2007 11:24:36] 5992 LicServer: License file check starting...
[28/10/2007 11:24:39] 5992 LicServer: Warning: Found a license with the same
4760OfferNumber on server : 155.132.33.195
[28/10/2007 11:24:40] 5992 LicServer: Error: License file(s) with same
4760OfferNumber is/are still used by other server(s).
[28/10/2007 11:24:40] 5992 LicServer: License file check is done
[28/10/2007 11:24:40] 5992 LicServer: Multi-utilization duration : 40 days, 91
allowed (status=warning)

Protection of control mechanism of license unicity


Any obstruction of control mechanism or any attempt to corrupt data or file used by the license
control will be registered as "Unexpected event". These events are counted and information
messages are displayed when connecting the client. The corresponding alarms are generated. It is
important to solve the issue before turning into restricted mode after 32 events.
More precisely:

10 events Warning
15 events Major
20 events Critical
32 events Bypass

Here are 2 examples of messages displayed when opening the client:

TCV039 18 Ed. 07 / 25 October 2007


OmniVista 4760
OmniVista 4760 LICENSES

CAUTION
The "Unexpected events" are erased only 40 days after their creation. Supposing that an event is
generated once a day (at the time of the license control) and that the counter is to 32 at the moment
or the problem is solved, the decrease will begin only 8 days later, date on which the first event will
be erased because dating more than 40 days. The system will stay in mode restricted as long as the
counter will indicate more than 31 events (8 days in this example).
Example of a particular unexpected event
The mechanism of license unicity control must write tha data on the attachment PCX.
A /usr4/tmp/ov4760 directory is created with FTP account defined by OmniVista 4760 manager
for the PCX in question (user and password Ftp).
The rights allocated to this directory and sub-directory uc are the following:

drwxr-xr-x 3 mtcl tel 4096 Sep 17 16:51 ov4760

In this example, only the creative account has the right of writing in this directory.
If the OmniVista 4760 manager changes the Ftp user for this PCX, OmniVista 4760 will not be able
to write any more in the ov4760 directory.
Each daily attempt will fail and will be counted as "unexpected event".
If the directory was created by error by mtcl account, it should be removed (ov4760 of PCX). It will
be created again by the adfexc default account after changing the management OmniVista 4760
side.
Associated logs
[9/20/2007 3:30:21 PM] 6268 LicServer: License file check starting...
[9/20/2007 3:30:24 PM] 6268 LicServer: Error: Unexpected events :
PCXConnect::putFile: Sending file c:\4760\data\temp\\4760_lock_ocppbx4.ocp-
ec.com failed : 553 4760_lock_ocppbx4.ocp-ec.com: Permission denied on server.
(Overwrite)
[9/20/2007 3:30:24 PM] 6268 LicServer: License file check is done
[9/20/2007 3:30:24 PM] 6268 LicServer: Error: Unable to check prevent file
[9/20/2007 3:30:24 PM] 6268 LicServer: Multi-utilization duration : 0 days, 91
allowed (status=ok)
[9/20/2007 3:30:24 PM] 6268 LicServer: License file multi-utilization :
unexpected events count : 26/31 (status=critical)
On first check after removing the ov4760 directory we have :
[9/20/2007 3:32:13 PM] 4692 LicServer: Error: Unexpected events : 4760 server is
supposed to be registered while it is not !
[9/20/2007 3:32:13 PM] 4692 LicServer: License file check is done
[9/20/2007 3:32:13 PM] 4692 LicServer: Multi-utilization duration : 0 days, 91
allowed (status=ok)
[9/20/2007 3:32:13 PM] 4692 LicServer: License file multi-utilization :
unexpected events count : 27/31 (status=critical)
On the following check, we no more must have errors and the counter value no more increases.

Ed. 07 / 25 October 2007 19 TCV039


OmniVista 4760
OmniVista 4760 LICENSES

4. MODIFYING THE LICENSES

4.1 Changing manually the licenses


1 Close the NMC Service Manager service using the manager of OmniVista 4760 service.
2 When all the dependent services are closed, copy the file of type xxyyyzza.sw4760 provided
by Actis/eLP, and rename it nmc.license. In Windows Explorer, check this name with right
click \Properties (nmc.licence and not nmc.licence.txt).
3 Move this file under the 4760\etc installation directory.
4 Reboot the PC.
5 Launch the client application.
6 Check that licenses have been updated using the Help\About menu.

4.2 Modifying the capacity / Adding the module


There is no tool to change the content of licenses of OmniVista 4760 server. Carry out a manual
change of license file.

4.3 Changing the CPU


Depending on the type of attachment PCX, the OmniVista 4760 license can be kept:
For OmniPCX 4400, the hard keys are saved,
possibility to keep the existing 4760 license file.
For OmniPCX Enterprise, the Handle4760 field is saved,
possibility to keep the existing 4760 license file.
For OmniPCX Office, the CPU-Id field is changed,
you should change the 4760 license.
Note
To help eLP license search, the field Handle4760 is initiated with the first purchased CPU-Id. after
rehosting an OmniPCX Enterprise CPU, the CPU-Id is modified but the Handle4760 field keeps its
initial value. Hence no need to update a 4760 license after rehosting a CPU.

4.4 Migrating OmniPCX 4400 to OmniPCX Enterprise


When migrating from OmniPCX 4400 towards OmniPCX Enterprise, the format of the hardware
identifier changes. The license moves from a check by hard key to a check by 4760Handle. The
4760 license thus should be regenerated.

4.5 Migrating the OmniVista 4760 version


When changing the version, the installation program checks the current license and compares the
version id with that required by the new version:

TCV039 20 Ed. 07 / 25 October 2007


OmniVista 4760
OmniVista 4760 LICENSES

if the version id is not compatible,


the installation program requires to supply a new 4760 license file,
if the version id is compatible but different,
the installation program requires anything,
after the update, reboot the server and wait the end of patch installation. Then you can:
continue to use the old license,
supply a new license file; to install this file, you need to carry out a manual copy of license
file,
if the version id is the same,
that is a version of maintenance corresponding to the same commercial version, therefore the
license is preserved.

Ed. 07 / 25 October 2007 21 TCV039


OmniVista 4760
OmniVista 4760 LICENSES

5. SOFTWARE LOCKS ON OMNIPCX 4400/ENTERPRISE


The access to data of various PCXs needs to have the corresponding software locks at level of each
PCX.

OmniVista 4760 Module Number of OmniPCX 4400/Enterprise software lock


Configuration 13 - ECS Engine
50 - Configuration
Accounting 42 - Accounting users
98 - Accounting for local calls (if local accounting)
99 - Accounting for ABC calls(if network accounting)
Directory 49 - STAP
Traffic observation 42 - Accounting 47XX (Do not forget)
39 - TrafObs 47XX
VoIP 42 - Accounting 47XX (Do not forget)
Alarms 47 - Alarms 47xx
Secured SSH connection with No specific software lock on OmniPCX Enterprise.
OmniPCX Enterprise Security license on OmniVista 4760

Identification of some issues related to software locks


The steps of configuration access to OmniPCX 4400/Entreprise are saved in the
4760\log\NMCCMISD_x.log file.

When the 50 Configuration PCX software lock is missing.

The configuration client return :


Rejet cmise : Association rompue

The file 4760\log\NMCCMISD_x.log


[09:33:39] 2220 CMISD: Error: The association is not accepted (AARE rejected)
(Pbx : PPP, Connection number : 1655, number of networklink (socket) : 748)
[09:33:39] 2220 CMISD: - Operation : rejected transient
[09:33:39] 2220 CMISD: - Source : acse_service_user
[09:33:39] 2220 CMISD: - Cause : application context name not supported

PCX side, activate the traces, mao +cmisd:


-> cmisd:authenticate control :station =|SRV4760| password =|L__| user = ||
-> cmisd:authenticate control : condition for check ( 47xx )
-> cmisd:authenticate control (47xx:1) status 0 )
-> cmisd:authenticate passed (47xx:1)
-> 47xx conditions and no right

TCV039 22 Ed. 07 / 25 October 2007


OmniVista 4760
OmniVista 4760 LICENSES

When the PCX 47 Alarms 47xx software lock is missing


The file 4760\log\NMCfaultmanager_A4400service_x.log
The EFD was not found -> Trying to create it
A CMISE error occurred

When the PCX PCX 42 Accounting 47xx software lock is missing


The file 4760\log\NMCsynchldap_x.log
On operation flush action on accounting
A CMISE error occurred

6. PROBLEMS AND SOLUTIONS


For any problem of license, it is necessary to study attentively the information contained in the
4760/logs/NMCLicServer_x.log file. This file must be joined for any request for assistance.

6.1 Alarms of licenses


The alarms related to license control appear in the module alarm under tree entry
NMC\Name_of_server\Licenses_Server.

Number de diagnosis Severity Criterion checked Bypass reached


4000 Warning User capacity > 80%
4001 Major > 90%
4002 Critical > 99%

4006 Warning 4760 Identifier > 1 day


4007 Major > 10 days
4008 Critical > 18 days

4011 Warning Global Synchro > 8 days


4012 Major >16 days
4013 Critical > 30 days

4027 Warning Multiple Utilization > 31 days


4028 Major > 51 days
4029 Critic > 71 days

4031 Warning Unexpected events > 10 errors


4032 Major > 15 errors
4033 Critic > 20 errors

Ed. 07 / 25 October 2007 23 TCV039


OmniVista 4760
OmniVista 4760 LICENSES

To send an e-mail when receiving an alarm related to a license:


open the Alarm module
menu Preference/Filter
add a filter: License
enter the Diagnosis filter between 4000 and 4033
fill in the e-mail address.
As of OmniVista 4760 R4.0, a pop up windows with the license alarm is displayed each time a client
connect to 4760 server.

TCV039 24 Ed. 07 / 25 October 2007


OmniVista 4760
OmniVista 4760 LICENSES

6.2 Client PC connection

R1.0 The client PC license take the dates of client and server into account
In all labs where the PCs have not the same date, the client cannot access
Workaround Set the same date on the PCs (to within a day)
Correction R1.5.08

R1.5.08.00c
CNMja13470 The client PC license requires more than one license during the connection
Thus on the sites where the PC client license is limited to 1, the server answers
Number of clients exceeded 1/1
Correction R1.5.09.

Functioning The maximum of logged clients is already reached


However less X clients are connected, wait the release of the license (3 min)

Functioning The server of licenses has denied the connection


There was not had global synchronization for more than 21 days. This can be
due:
to a deletion of daily synchronization jobs, see section Launching the
synchronization in restricted mode to launch the synchronization,
to stop of the synchldap.exe service, analyze the logs of service under the
4760\log\NMCsynchLDAPpbx_X directory

Functioning Licence =NO


there is no client license (number of PC client =0)
generate a new license with at least 1 PC client

Ed. 07 / 25 October 2007 25 TCV039


OmniVista 4760
OmniVista 4760 LICENSES

R1.0 & 1.5.08.00c


1-16832501 Server with Pentium 4, the license server refuses the connection
On Pentium 4 PC, the data base does not install. Consequently, the service
access no more the data base and the le synchldap.exe service does not start
Correction R1.5.08.00d

Management Server in initialization phase


The causes may be:
the nmclicserveur service is not started, check the nmc.license file under the
4760\etc directory,
the data base containing 4760 administration accounts has been deleted.
Launch the LDAP console with the cn=directory manager account and
check the integrity of the company side

R2.0.12.01d
CNMja14728 Too many users are stored in the NMC on OmniPCX Office
Correction R2.0.12.01.d5
It is sufficient to have a 4760 license corresponding to:
the users managed in OmniPCX Office,
and not to the maximum number of users possible OmniPCX Office side

Management Too many users are stored in the NMC

If this exceeding is due to:


an increase in the capacity of the site, it is necessary to update the license
an error of management; it will be necessary to use another application of
configuration, embedded or external, to reduce the number of users on the
PCXs
if OmniPCX Office ACD groups are counted as users, apply if necessary
the patch "4760 R4.1.13 + patch XTScf00842" ; see section OmniPCX
Office.

TCV039 26 Ed. 07 / 25 October 2007


OmniVista 4760
OmniVista 4760 LICENSES

Management No NMC license for this OmniPCX network

Cannot connect to the server since the server cannot connect to the attachment
PCX too much time or the identifiers are not the same between 4760 license
and PCX
Correction Solve the problem of ftp connection between 4760 and PCX.
Installation of a new license associated to an other attachment PCX.
Delete the previous attachment PCX. The 4760Handle identifier must
be the same in the 4760 license and in OmniPCX Enterprise
(spadmin Option 2 command)
Installation of a new license associated to a new CPU-Id of the attachment
OmniPCX Office

Information

The same license is used on 2 different servers for a long time. These 2 servers have
the same attachment PCX.

Correction Order a 2nd license


Remove one of two servers
CAUTION : The system remains in restricted mode as long as we did not
reach 5 days of functioning without conflict.

Ed. 07 / 25 October 2007 27 TCV039


OmniVista 4760
OmniVista 4760 LICENSES

Information

Misfunctioning of control mechanism of license unicity for a long time.

Correction Confirm the writing right of the current FTP user in the
/usr4/tmp/ov4760 PCX directory. If it is not the case, delete this
directory then check its re-creation with the correct rights after restarting the
NMC License Server service.
CAUTION: The remains remains in restricted mode as long as the counter
value is higher than 31; see section Use of the same license on two
OmniVista 4760 servers.
For others cases, consult the log file to identify the problem.

6.3 Alarms

Functioning
The EFD was not found -> Trying to create it
A CMISE error occurred
The software lock 47 alarms 47xx is not enabled on the PCX

6.4 Configuration

Functioning
Configuration to OmniPCX 4400/Enterprise: Rejet cmise :Association rompue
The 50 Configuration software lock is not opened on the PCX
Require a modification of the PCX license to add it

TCV039 28 Ed. 07 / 25 October 2007


OmniVista 4760
OmniVista 4760 LICENSES

6.5 Tickets

R2.0.12.01d
CNMja14682 Loading the tickets OmniPCX Office depends on the Alarm license
The synchronization attempted to save alarms, thus for sites without alarm
license:
there is a failure of the synchronization,
The tickets remain present in the directory of the server
4760\loader\networknumber\Alizenodenumber
no immediate loading of tickets in base. It was necessary to wait the
restarting of 4760 services.
Correction R2.0.12.01.e

R1.0 et R1.5
CNMja14728 Accounting Module depends on the traffic observation license
This module is common to the traffic observation, therefore for the sites
comprising only the accounting license, a java exception appears with the
opening of the module
Correction R2.0.12.01.d5

Management Access denied when retrieving the traffic observation tickets


The loading of OmniPCX 4400/Enterprise traffic observation tickets requires
the availability of the external accounting license on the PCX

Management Access denied when retrieving VoIP tickets


The loading of OmniPCX Enterprise VoIP tickets requires the availability of the
external accounting license on the PCX

Ed. 07 / 25 October 2007 29 TCV039


OmniVista 4760
OmniVista 4760 LICENSES

6.6 New license

Management Installation of a temporary license


If a temporary license were used on a site, it is no more possible to install
another temporary license. It is necessary to update a temporary license by a
final license

Management The 4760 licenses facing OmniPCX Office


The generation of the license file changed between 4760 Releases 1.5 and
2.0.
In 4760 Release 1.5, the licenses were defined in the OmniPCX Office
commercial catalog with 4 capacities. Four files were managed
independently of the CPU-Id of OmniPCX Office.
As of 4760 Release 2.0, it is necessary to have a license file which supports
on the CPU-Id of OmniPCX Office. It exists no more diskettes of pre-
initialized license according to the capacities

Information How to obtain licenses for labs?


Create a Service Request to get the licenses for labs

Information How to migrate 4400 lab licenses towards OmniPCX Enterprise


Order under eLP.
The migration to OmniPCX Enterprise version generates a 4760Handle which
will be unique for each site even the keys 0223 are kept on the PCX

TCV039 30 Ed. 07 / 25 October 2007