Alcatel-Lucent OmniPCX Enterprise

Communication Server

Licenses
Legal notice:

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

Alcatel-Lucent. All other trademarks are the property of their respective
owners.

The information presented is subject to change without notice.

Alcatel-Lucent assumes no responsibility for inaccuracies contained herein.

Copyright 2007 Alcatel-Lucent. All rights reserved.

The CE mark indicates that this product conforms to the following Council
Directives:
- 89/336/CEE (concerning electro-magnetic compatibility)
- 73/23/CEE (concerning electrical safety)
- 1999/5/CE (R&TTE)

 
 
 

Chapter 1
Overview

 Overview .................................................................................................... 1.1

Chapter 2
Basic description

 Basic description ................................................................................... 2.1

Chapter 3
Detailed description

 Licenses .................................................................................................... 3.1

 Locks .......................................................................................................... 3.1
 The Purchasing Process ..................................................................... 3.2
 Tools ............................................................................................................. 3.2
 First Sale/Initial Purchase ........................................................................... 3.2
 Add-ons ........................................................................................................ 3.2
 OPS Files ................................................................................................... 3.3

     0-1

 

 Risk in Case of Fraudulent Use ......................................................... 3.3

 Legal Risks ................................................................................................... 3.3
 Functional Risks .......................................................................................... 3.3
 Changing the CS Board for Maintenance ...................................... 3.4
 License Move (from R5.1) ................................................................... 3.5
 Overview ....................................................................................................... 3.5
 Transfer Principle ........................................................................................ 3.5
 Protection ..................................................................................................... 3.5
 Reusing OmniPCX 4400 CPUs .......................................................... 3.5
 Test Sets (from R5.1.1) ......................................................................... 3.6

Chapter 4
Configuration procedure

 Principle ..................................................................................................... 4.1

 Managing OPS Files with swinst .................................................. 4.1
 Saving OPS Files on the Call Server Hard Drive ...................................... 4.1
 Restoring OPS Files from the Call Server Hard Drive .............................. 4.2
 Managing OPS Files .................................................................................... 4.2
 Restart after Detecting an Inconsistency .................................................. 4.6
 Saving OPS Files on USB Key ................................................................... 4.7
 Restore OPS from USB Key ....................................................................... 4.7
 Cleaning OPS Files on USB Key ................................................................ 4.7
 Consulting Locks Via the Configuration Tool ............................. 4.8
 Processing the OPS File <offerld>.sw4760 .............................. 4.8
 Incidents/Errors ...................................................................................... 4.8

Chapter 5
License Move

0-2
    
  

 Overview .................................................................................................... 5.1

 License: 10 Phonebook users (lock 2) ....................................... 5.1
 License: CCD 5 agents pack (lock 76) ........................................ 5.1
 License: Roaming DECT (lock 90) ............................................... 5.1
 License: ECC 4980 option 10 ext pack (lock 117) .................. 5.2
 License: DECT encryption (lock 127) ......................................... 5.2
 License: ECC My softphone 10 ext pack (lock 129) .............. 5.2
 Set Licenses (locks 173, 174, 176 and 177) .................................. 5.2
 On an ABC-F Network ................................................................................. 5.3
 On a Network other than an ABC-F Network ............................................ 5.3
 License: 10 Mobile users (lock 175) ............................................ 5.3
 License: G729A Client (lock 197) ................................................. 5.4
 License: OmniCellular client for 10 users (lock 308) ............ 5.4
 License: Class service (CLIP) for 10 analog users (lock 310)
........................................................................................................................ 5.4

Chapter 6
List of Software Locks

 List of Alcatel-Lucent OmniPCX Enterprise CS Locks ............. 6.1

 Note 1 ........................................................................................................... 6.13
 Note 2 ........................................................................................................... 6.13
 Note 3 ........................................................................................................... 6.14
 Note 4 ........................................................................................................... 6.14
 Note 5 ........................................................................................................... 6.14

     0-3

 

0-4
    
 
 

1 

1.1 Overview
The system of licenses and locks allows the customer to purchase only the features that he
needs. The Call Server software is sold as a single package with a full Alcatel-Lucent
OmniPCX Enterprise Communication Server feature set. Under these conditions, it would be
unfair to charge customers for features they do not use.

     1-1

Chapter 1 

1-2
    
 
 

2
  

2.1 Basic description

The customer purchases one (or more) licenses for each feature required. Licenses are
marketing packages or sales "units". Licenses have matching locks that are functional units.
The locks, installed on the Call Server, allow the features purchased to be used.
Purchase of licenses results in delivery of OPS (Order Preparation System) files. These lock
files, also called "OPS files", are installed on the Alcatel-Lucent OmniPCX Enterprise CS. They
contain:
- A list of the locks purchased.
- The number of the system supporting the Call Server. This number is referred to as the
"CPU identifier" or CPU ID". System number (CPU ID) is a unique number stored in
PROM. It can be read by the BIOS. For a duplicated Call Server, there are two identifiers
(one for each Call Server).
- A software key. The software key is an encrypted data item that depends on the locks
purchased and system numbers (CPU IDs). The software key guarantees that the OPS
files are of Alcatel-Lucent origin in order to prevent illegal use.
With R5.1, Alcatel-Lucent introduced the concept of "license move" (transfer). This feature
allows licenses to be moved from one machine to another, provided that both machines belong
to the same customer.

     2-1

Chapter 2    

2-2
    
 
 

3   

3.1 Licenses
There are several types of licenses:
- Service Authorization License. Purchase of this type of license authorizes the
customer to use this service. For example, E-CS REDUNDANCY authorizes use of a
duplicated Call Server.
- License by steps. Purchase of this type of license allows a certain number of users to
access a service. For example, PHONEBOOK 10 EXT authorizes" 10 sets to use the
"Dial by Name service. If you want 30 sets to have access to this service, you must
purchase 3 licenses.
- License by stage. Purchase of this type of license allows a certain number of users to
access a service. For example, HOTEL UP TO 150 EXT authorizes the creation of a
maximum of 150 customer sets in a hotel. Another license authorizes the creation of a
hotel with over 500 sets. A higher release (stage) can only be purchased if a lower release
has already been purchased.
Alcatel-Lucent Marketing Services can provide a complete list of licenses.
Special case of the OmniVista 4760
The OmniVista 4760 has its own license system, similar to that of the Call Server. In addition,
for an OmniVista 4760 to supervise an Alcatel-Lucent OmniPCX Enterprise CS, the latter must
have a license which allows such supervision.
There are several supervision licenses:
- Configuration
- Alarms
- Accounting (charging)
- Directory
- Traffic Analysis

3.2 Locks
Each lock has:
- A maximum value that depends on the licenses acquired. The maximum value of a lock
can be:
0 or 1 when it corresponds to a "service authorization" license. 0: service prohibited, 1:
service authorized.
0 to 9999 (or 0 to 099999 as of R8.0) when it corresponds to "number of users"
licenses. The value of the lock is then equal to the maximum number of authorized
users. For example, the PHONEBOOK EXT lock sets the number of users authorized
to use the "Dial by Name" service.
The value 9999/099999 indicates that the feature is authorized for unlimited use.
- A current value that represents the actual number of users on this service.
Some locks are referred to as "open" when they no longer correspond to a marketing offer.

     3-1

Chapter 3   

These locks are systematically positioned at the maximum value.

Some locks are referred to as "not used" when the Call Server software no longer uses them.

3.3 The Purchasing Process

3.3.1 Tools
Alcatel-Lucent has developed the following tools:
- eCom: the Alcatel-Lucent Internet server dedicated to taking purchase orders for licenses
and also hardware.
- Actis: a software tool providing assistance in drawing up a sales proposal. Actis runs
off-line on the marketing representative's PC (laptop for example).
- eLP: a software tool providing and associating a new CPU ID in the OPS files.
There may be other tools for specific needs.

3.3.2 First Sale/Initial Purchase

The marketing representative draws up a proposal tailored to the customer's needs. He uses
Actis to do this. The main features of Actis are:
- Integrated hardware and feature catalogs.
- Existing proposals can be copied/modified.
- Consistency of selected options is checked.
When the proposal is approved, the offer becomes an order which is transmitted to the eCom
server.
The eCom server performs the following operations:
- Stores all customer configurations.
- Forwards the hardware order to the production department.
- Produces and sends the OPS files.
Orders can also be directly placed on eCom (without using Actis). However, the eCom
interface offers fewer features and requires Internet access.

3.3.3 Add-ons
There are two procedures:
- Via Actis: The marketing representative imports the old customer configuration stored on
the eCom server. He then modifies this jointly with the customer and exports it back to
eCom. As at initial purchase, eCom saves the new configuration, transmits the hardware
order to the production department if necessary, and produces and sends the new OPS
files. This is the recommended procedure.
It is also possible to recover the OPS files from the Call Server work files using
"photoconfig". This procedure is used if the OPS files are not available on Actis or eCom.
This situation arises when commissioning does not comply with standard procedure.
- Directly on eCom: After connecting to the eCom server, the marketing representative can

3-2
    
   

modify the saved configuration. If necessary, a hardware order is sent to the production
department and new OPS files are sent.

3.4 OPS Files

The OPS files are the following:
1. <offerld>.swk
2. <offerld>.hw
3. <offerld>.sw4760 (only if a OmniVista 4760 is ordered)
4. hardware.mao
5. <offerld>.zip
<offerld> is a string of characters specific to the site.
Files 1 and 3 are installed whatever the command mode. Files 2, 4 and 5 are installed with
commands performed via ACTIS.
When an add-on is installed, the Alcatel-Lucent OmniPCX Enterprise CS may have to be
rebooted for installation of the new OPS files. Reboot may or may not be necessary,
depending on the locks modified. For information on which locks require the Alcatel-Lucent
OmniPCX Enterprise CS to be rebooted, see the module Licenses - List of Software Locks .
Caution:
The <offerId>.swk file is only produced by eCom. It is only accepted by the system if the software
key is consistent with the licenses.

3.5 Risk in Case of Fraudulent Use

3.5.1 Legal Risks

It is illegal to duplicate software programs or to unlock a feature without authorization.
Offenders are liable to be prosecuted by law.

3.5.2 Functional Risks

When the system detects an inconsistency in the OPS files, it suspects illegal use and runs in
degraded mode. The phases of this degraded mode are:
- Action 1 (as soon as illegal use is detected)
Displays a message on the attendant set as soon as it enters idle mode, with a
mandatory order for the attendant to acknowledge this message.
Deletes the screen of the terminal system, and displays the incident message.
Acknowledgement is mandatory.
Stores the incident in the incidents file.
Continuous ringing on an alarm set.
Some management commands can then no longer be performed and result in the
following error: "Software protection error".
- Action 2 (4 hours later):

     3-3

Chapter 3   

Displays a predefined string on all sets with a display.

- Action 3 (8 hours later):
Loopback on actions 1 and 2.
The system checks its OPS files every four hours. If an inconsistency is detected, it initiates
the degraded mode procedure.
Note:
If the OPS files do not contain a Call Server Identification (CPU_Id), the system suspects a maintenance
operation and postpones the degraded mode procedure for 30 days.

3.6 Changing the CS Board for Maintenance

The CS board (Call Server support) may have to be changed. In this case, the identifier of the
new board no longer corresponds to the identifier declared in the OPS files. The installer has
30 days (before degraded mode is triggered) to provide notification of this change of situation.
___change-begin___
___change-end___
Figure 3.1: Block Diagram of OPS File Update Operations Following CS Board Replacement
1. Diagnosis and replacement of the CS board (replacement includes hardware operations,
software loading and configuration).
2. Retrieval of site information:
The number of the new CS board.
The number of the old CS board.
3. Site information sent to the eCom server.
4. Retrieval of new OPS files.
5. Installation of the new OPS files on the site.

3-4
    
   

3.7 License Move (from R5.1)

3.7.1 Overview
A license is acquired for a specified PCX. If you want to transfer a license for a feature from a
source PCX to a target PCX, you must carry out a "license move".
When moving licenses, the licenses not used on the source PCX are recovered for use on the
target PCX. Licenses are moved using the eCom server.
Not all licenses can be moved. Alcatel-Lucent considers that the transfer of some licenses is
not recommended due to the complexity of their implementation. See the list of transferable
licenses in the module Licenses - List of Software Locks .
Note:
License transfer/move can only be performed between two PCXs belonging to the same customer.

3.7.2 Transfer Principle

To carry out a license move the installation technician performs the following operations:
- Creates new OPS files on the eCom server (fewer on the source PCX and more on the
target PCX).
- Installs the OPS files on the PCXs.
- Increases services on the "destination" PCX and decreases services on the "source" PCX.
- Recovers the acknowledgement code from the source PCX. This acknowledgement
proves that the OPS files have been installed correctly and avoids any illegal use.
- Enters the acknowledgement code on eCom.
The acknowledgement code must be entered on eCom at the latest 30 days after creation of
the OPS files. If this deadline is not respected, Alcatel-Lucent will take legal action against the
organization performing the license move.
A specific procedure is required to move a lock, see the module Licenses - License Move .

3.7.3 Protection
Each OPS file contains a version number. To prevent illegal use, the system considers
installation of OPS files with a version number lower than that of the active files as constituting
an inconsistency. The installation technician has 5 days to rectify this.
Caution:
This protective mechanism complicates the installation technician's task. If the newly installed
OPS files present a problem, returning to the previous OPS files will result in inconsistency. The
installation technician will have to react promptly in order to rectify the inconsistency.

3.8 Reusing OmniPCX 4400 CPUs

CPU5-3 and CPU6 are reusable on a Alcatel-Lucent OmniPCX Enterprise CS (from R5.1).
There are two possible options:

     3-5

Chapter 3   

- Send the CPU back to the factory for an update. The hard keys are then removed. The
new software, Bios and appropriate OPS files are loaded.
- Change only software version on site. The hard keys are kept, an eCom business
reference called "virtual CPU-Id" is given. The appropriate OPS files are loaded.

3.9 Test Sets (from R5.1.1)

Various types of sets must be used to test the quality of voice calls on an Alcatel-Lucent
OmniPCX Enterprise CS. However, some customer configurations do not include all types of
sets.
For such specific cases, Alcatel-Lucent authorizes (without it being necessary to have the
corresponding license) creation of the following sets (one of each type):
- One IP Phone
- One analog set
- One UA set

3-6
    
 
 

4   

4.1 Principle
To configure locks, the manager must perform the following operations:
- Install the OPS files to apply the licenses acquired: Restoring OPS Files from the Call
Server Hard Drive
- Back up the OPS files in order to perform an add-on: Saving OPS Files on the Call
Server Hard Drive
- Manage OPS files: Managing OPS Files
- Restart after detecting an inconsistency: Restart after Detecting an Inconsistency
For these operations, the manager can use the following tools:
- swinst: procedure described below.
- OmniVista 4760: procedure described in the OmniVista 4760 documentation.
- Wizard: procedure described in the Wizard documentation.

4.2 Managing OPS Files with swinst

OPS configuration access:
swinst > Expert menu > OPS configuration
OPS configuration general menu:
  
      

  ! "  #  " $!

 %&  #& " $!
  $ &
' #(& "&  & )&
*  ! "  #  + !,
 %&  #& + !,
-   #  + !,
.  ! "  #  / #"",
0 %&  #& / #"",
 1(  / #"", $!
 &  / #"", $!
2 3 4 !  "&)  

5 & 6 78 29 :

The "swinst" tool has a number of functions. Only functions related to OPS files are described
here. For a full description of the "swinst" tool, see the module Swinst - Detailed description.

4.2.1 Saving OPS Files on the Call Server Hard Drive

Access:
swinst > Expert menu > OPS configuration > Backup OPS files on cpu disk

     4-1

Chapter 4  

This command is used to recreate OPS files from work files. The files created with this
command are available in either the directory /usr4/BACKUP/OPS or
"DHS3dyn/BACKUP/OPS". This operation is implemented in the case of an add-on, it is
sometimes called photoconfig. A file transfer operation (using ftp, for example) must be
performed to retrieve these files from the Call Server.

4.2.2 Restoring OPS Files from the Call Server Hard Drive
Access:
swinst > Expert menu > OPS configuration > Restore OPS from cpu disk
This command is used to install the OPS files previously copied (via ftp, for example) in the
directory /usr4/BACKUP/OPS. In some cases, swinst will ask for the Call Server to be
rebooted to apply these changes.
Caution 1:
Using the swinst tool is the only correct method for installing the OPS files. Any other method
(for example, direct copy) would cause the system to switch to fraudulent (illegal) use status with
the corresponding consequences (operation in degraded mode).
For an add-on which affects only the licenses, the only file provided is <offerId>.swk.
For an add-on which affects the licenses and a hardware item, the <offerld>.swk, <offerld>.hw,
hardware.mao, offerld.zip and <offerld>.sw4760 (optional) files are provided.
If the files to be installed have a version (release) number lower than that of the files currently
installed, the installation takes place. However, the system switches to fraudulent (illegal) use
status. The manager is informed of this by a warning message and has five days to rectify the
situation. This check is linked to the "license move" procedure.
Caution 2:
When you install OPS files for the large equipment capacity feature on a Call Server in small
equipment capacity, swinst will ask you to reboot the system to take into account the large capa-
city. You must then re-install the OPS files. You can use the command siteid to see the equipment
capacity level of the Call Server.

4.2.3 Managing OPS Files

Access:
swinst > Expert menu > OPS configuration > OPS administration
4.2.3.1 Main Menu

4-2
    
  

/", &&   &  

/",  ) #  
6 !  ) # 6& ,  
   ( #  '
%$ 6 , !,  *
+;$  
   
/",  )  $ ( #  -
/",    .
/", < $  0
=  
6  >

Note:
This swinst menu is identical to the spadmin maintenance command.

4.2.3.2 Display Current Counters/Locks (1)

Result of the command:

?@ #(& &   & >

A 
>  ?@
3& " "6 ,  & >  ?@
 , A  & > 0


1. PANIC Flag status. The Panic Flag indicates that an inconsistency has been detected in
the OPS files and that the degraded mode procedures of the system are activated:
PANIC Flag = 0 normal operation.
PANIC Flag = 1 operation in degraded mode.
2. List of counters corresponding to each lock. For example, if the manager has authorized
"Call By Name" for 9 users, the Call By Names Counter is equal to 9.
4.2.3.3 Display Active File (2)
4.2.3.3.1 General Case
Result of the command:

     4-3

Chapter 4  

/ )& >  ?@

 )& >  ?@
B )& >  ?@
# <, > #.-.$*$4 ?'@
" $ >   ?*@
" $ > $$-
+C$ #&  >   ?@
, +C$ # $ ?-@
D $ '- >   ?.@

" > & 4 . >>  ?0@

 )& > - ?@

;3& ""6 , > "> 0000 ?@
;6 4! & > ">  ?'@
;/ > "> 

;D&$ <,  > "> .* ?@
;D&$ <,  > "> .

1. Reserved for Alcatel-Lucent support.

2. Displays OPS file version.
3. Reserved for Alcatel-Lucent support.
4. Displays the software key or checksum.
5. Displays authorized CPU-Ids. If the Call Server is duplicated, there are two CPU-Ids.
6. Displays the business reference for eCom. This reference is either the CPU-Id or, if the
hard key is used, an arbitrary reference provided by eCom. This arbitrary reference is
sometimes called a virtual "CPU-Id".
7. Indicates that local system CPU-Id has been found in the list of authorized CPU-Ids.
8. Displays the authorized OmniVista 4760 CPU-Id.
9. File creation date.
10. Displays the OPS version from which this file was created.
11. List of locks with the maximum value authorized (depending on purchase options). For
moveable locks, the system adds the current value in brackets.
12. Displays hard keys if present or 0000 if there are no hard keys present.
4.2.3.3.2 Errors
Result of the command:

4-4
    
  

/ )& > 

 )& > 
B )& > 
# <, > #.-.$*$4
" $ >  
" $ > $$-
5 & , +C$ > #  ?@
, +C$  # $E ?@
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF ?@
F  & 
$,?@  #= 6   F
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
D $ '- >  
" > & 4 . >> 
 )& > -
;3& ""6 , > "> 0000

.................
1. Displays the business reference for eCom.
2. Displays that CPU-Id is incorrect.
3. Displays the number of days remaining before the procedure for switchover to degraded
operating mode is launched.
4.2.3.4 Check Active File Coherency/Consistency (3)
The tool checks whether the checksum is compatible with the locks and Call Server number.
Result of the command when the check is correct:
G 6 !
 ) # H/D$HH#(&
 <

Result of the command when the check is incorrect:

G 6 !
 ) # H/D$HH#(&
&&& > 
 6&$(& !,

4.2.3.5 Install a New File (4)

This command is identical to Restoring OPS Files from the Call Server Hard Drive .
4.2.3.6 Read the System Key/Call Server Identifier (5)
The tool displays Call Server number. For example:
If the identifier is a CPU-Id:
, +;$> ##0

If the identifier is a hard key:

5 & D&$ <,> .*

4.2.3.7 CPU-Ids (Call Server number) Management (6)

This command allows an installation technician to carry out an on-site Call Server add-on or
Call Server replacement. For sites which do not have access to eCom, the information may be
sent by telephone or fax.
Sub-menu:

     4-5

Chapter 4  

"$ > +C$  

 
;;;;;;;;;;;;;;;;;;;;;;;;;;;;
$$ +;$  
%) +;$  
+"$ +;$  
 !  "&)   '
6  >

The tool asks the operator to enter Call Server number(s) and the new software key. The
operation is only performed if the new software key is consistent.
4.2.3.8 Display Active and New File (7)
This command displays the contents of the current file and of the file to be installed in two
columns. The file to be installed should be called software.new and should be located in the
directory /DHS3data/mao. Display format is the same as that shown in section Display
Active File (2) .
4.2.3.9 Display OPS Limits (8)
 
%   I ?<4@ J *
A 4& #   J 0--
A 4& # & ! J .'
A 4& # 6#;  = J 0*
 $;  J 
A 4& #  J 
6 ;4! ?= @ J 
 J 
 J 
'* J 
D   J 
/  "&)&   J 
K ;    J 
A4 #  $", 

 J '
A4    J 
A4 # )   J *
A4  J 
&  J 
A 4& # A  K &
J 
A 4& #    #&  J 

This command displays the maximum values that can be configured on this site. These
maximum values depend on the software used and on the hardware configuration of the site.
Consequently, there is no reason to purchase locks for higher values as they cannot be used.
4.2.3.10 Display ACK Code (9)
This command displays the acknowledgement code. The acknowledgement code is used
when a license is transferred (moved).

4.2.4 Restart after Detecting an Inconsistency

Access:
swinst > Expert menu > OPS configuration > Software protection recover

4-6
    
  

This command is used when an inconsistency has been detected. This command is used to
restart station display for a duration of four hours, which gives the technician time to intervene.
This command can be repeated ten times. A reset must then be performed to re-validate the
features. This operation was formerly performed using the "sprecover" command.

4.2.5 Saving OPS Files on USB Key

This option allows to save local or remote OPS files on an USB key. This function is only
available on CPU7 step2, Appliance Server and Blade Server.
Access:
swinst > Expert menu > OPS configuration > Backup OPS files on USB key
The user is prompted to select the Alcatel-Lucent OmniPCX Enterprise CS.
A # 6 ?$#    @ ;G

By default, the local OPS files are saved.

After confirmation, the OPS files of the selected Alcatel-Lucent OmniPCX Enterprise CS are
saved on the USB key.
Note:
The USB key must be previously enabled (see: module Swinst - Operation Enable [Disable] USB Key).

4.2.6 Restore OPS from USB Key

This option allows to restore OPS files from an USB key. This function is only available on
CPU7 step2, Appliance Server and Blade Server.
Access:
swinst > Expert menu > OPS configuration > Restore OPS from USB key
Select the Alcatel-Lucent OmniPCX Enterprise CS.
6 )4 #$& &>
  
6 
6 
6 

A # #$& ?$#    @ ;G
A # 6 ?$#    @ ;G

After confirmation, the selected files are installed on the local or on the remote Alcatel-Lucent
OmniPCX Enterprise CS.
Note:
The USB key must be previously enabled (see: module Swinst - Operation Enable [Disable] USB Key).

4.2.7 Cleaning OPS Files on USB Key

Access:
swinst > Expert menu > OPS configuration > Clean OPS files on USB key
Select the Alcatel-Lucent OmniPCX Enterprise CS.

     4-7

Chapter 4  

6 )4 #$& &>

  
6 
6 
6 

A # #$& ?$#    @ ;G

The list of the OPS files is displayed and after confirmation, the selected files are deleted. This
function is only available on CPU7 step2, Appliance Server and Blade Server.

4.3 Consulting Locks Via the Configuration Tool

Lock values can be viewed using the configuration tool (mgr or OmniVista 4760).
Object name: System > Software Package
Attributes:
Package Number : Select the name of the lock to be consulted.
Authorized Limit : Displays the maximum value authorized for this lock.
Current Value : Displays the current value of the lock.

4.4 Processing the OPS File <offerld>.sw4760

The OmniVista 4760 OPS file <offerld>.sw4760 is not functional on the Alcatel-Lucent
OmniPCX Enterprise CS. However, this file is used by the ACTIS software for add-ons when
eCom is not used. The ACTIS procedure first requires the OPS files to be retrieved
(photoconfig operation). If the <offerld>.sw4760 file is not present on the PCX, it is easy to
forget it. To avoid this problem, it is highly advisable to copy this file to the PCX at installation.
To do this, proceed as follows:
- Transfer, via ftp, the file <offerld>.sw4760 to the directory /usr4/BACKUP/OPS.
- Activate the OPS files (command, swinst > Expert menu > OPS configuration >
Restore OPS from cpu disk). The <offerld>.sw4760 file is then saved, with the other
OPS files, to the directory /usr3/mao.
During the photoconfig operation (swinst > Expert menu > OPS configuration > Save
OPS files on cpu disk) the file <offerld>.sw4760 is copied to the directory
/usr4/BACKUP/OPS with all the other OPS files.
When the add-on operation is complete, do not forget to place the new file on the PCX.

4.5 Incidents/Errors
If the system detects an inconsistency, it outputs fault "5906" on a daily basis:
"xxx day(s) remaining before changing to fraudulent state"
The installation technician is thus informed of the time remaining to rectify the problem.

4-8
    
 
 

5   

5.1 Overview
The procedures described below are for one license. However, it is possible to move several
licenses simultaneously (licenses of the same type or of different types).
The eCom server accepts deferred acknowledgement, which allows the OPS files for the
source and destination PCXs to be created simultaneously.
In general, the following rule must be respected: On a PCX, you must always have locks for
the services declared. Therefore, before "reducing" (the scope of) a lock, you must "reduce"
the corresponding service and before "increasing" a service you must increase the
corresponding lock.

5.2 License: 10 Phonebook users (lock 2)

- On eCom: create new OPS files for the source and destination PCXs.
- On the source PCX:
Delete rights for the "Dial by name" feature on the selected sets.
Install the reduced OPS files.
Read the acknowledgement code.
- On the destination PCX:
Install the increased OPS files.
Assign "Dial by name" rights to the selected sets.
- On eCom: Enter the acknowledgement code read on the source PCX.

5.3 License: CCD 5 agents pack (lock 76)

Check that lock 13 (E-CS Engine) is "sufficient" on the destination node.
- On eCom: create new OPS files for the source and destination PCXs.
- On the source PCX:
Log off the agents to be moved.
Install the reduced OPS files.
Read the acknowledgement code.
Reboot the cabinet.
- On the destination PCX:
Install the increased OPS files.
Reboot the cabinet.
Log on the agents that have been moved.
- On eCom: Enter the acknowledgement code read on the source PCX.

5.4 License: Roaming DECT (lock 90)

     5-1

Chapter 5   

Check that locks 175 (Mobile users) and 82 (Mobile terminal) are sufficient on the destination
node.
Proceed in similar manner as for moving the license for 10 Phonebook users (lock 2).

5.5 License: ECC 4980 option 10 ext pack (lock 117)

In order to transfer a number (n) of licenses, you must also transfer:
- "n" 116 locks (4980 standard).
- "n" 129 locks (4980 groupware).
- "n" 197 locks (G729 client) or 198 locks (G723 client) if the 4980s are linked to multimedia
2 PCs.
Proceed in similar manner as for lock 2 "Phonebook users", but delete rights to the "4980
professional" feature (using the softphone administration tool) instead of deleting rights to the
"Dial by name" feature.

5.6 License: DECT encryption (lock 127)

Check that locks 175 (Mobile users) and 82 (Mobile terminal) are sufficient on the destination
node.
- On eCom: create new OPS files for the source and destination PCXs.
- On the source PCX:
Delete the right to encryption (only if the lock changes to 0).
Install the reduced OPS files.
Read the acknowledgement code.
- On the destination PCX:
Install the increased OPS files.
Add the encryption right (if this has not already been done).
- On eCom: Enter the acknowledgement code read on the source PCX.

5.7 License: ECC My softphone 10 ext pack (lock 129)

In order to transfer a number (n) of licenses, you must also transfer:
- "n" 116 locks (4980 standard).
- "n" 197 locks (G729 client) or 198 locks (G723 client) if the 4980s are linked to multimedia
2 PCs.
Proceed in similar manner as for lock 2 "Phonebook users", but delete rights to the "4980
groupware" feature (using the softphone administration tool) instead of deleting rights to the
"Dial by name" feature.

5.8 Set Licenses (locks 173, 174, 176 and 177)

Licenses concerned:
- Licenses: 10 UA fixed users (lock 173).

5-2
    
   

- Licenses: 10 analog users (lock 174).

- Licenses: 10 IP users (lock 176).
- Licenses: 10 SIP users (lock 177).
On the destination node, check that lock 13: E-CS engine is sufficient. In addition:
- If an IP set transfer is performed, check that lock 138 "IP equipments" is equal to lock 176.
- If a SIP set transfer is performed, check that lock 185 "SIP gateway" is set.

5.8.1 On an ABC-F Network

- On eCom: create new OPS files for the source and destination PCXs.
- On the source PCX:
Wireline (static) sets (UA and analog): delete physical equipment from the sets which
are to be transferred.
IP sets: Change set type from "IP" to "non IP" for the sets to be transferred.
SIP sets: Change set type from "SIP" to "Analog" for the sets to be transferred.
Install the reduced OPS files.
Read the acknowledgement code.
Move the sets to be transferred.
- On the destination PCX:
Install the increased OPS files.
Wireline (static) sets (UA and analog): Assign new physical equipment.
IP sets: Change set type from "non IP" to "IP".
SIP sets: Change set type to "SIP".
- On eCom: Enter the acknowledgement code read on the source PCX.

5.8.2 On a Network other than an ABC-F Network

- On eCom: create new OPS files for the source and destination PCXs.
- On the source PCX:
Export data from the sets to be moved to the OmniVista 4760 or 4760i.
Check the compatibility of the data with the capabilities of the destination PCX (and
make any modifications required).
Delete the sets transferred.
Install the reduced OPS files.
Read the acknowledgement code.
- On the destination PCX:
Install the increased OPS files.
Import set data from the OmniVista 4760 or 4760i.
- On eCom: Enter the acknowledgement code read on the source PCX.

5.9 License: 10 Mobile users (lock 175)

     5-3

Chapter 5   

On the destination node, check that lock 13: "E-CS engine is sufficient and that locks 175 and
82 have the same values.
- On eCom: create new OPS files for the source and destination PCXs.
- On the source PCX:
Export data from the sets to be moved to the OmniVista 4760 or 4760i.
Delete the mobile sets to be moved.
Install the reduced OPS files.
Read the acknowledgement code.
- On the destination PCX:
Install the increased OPS files.
Reboot the cabinet if the license is greater than 250,
Import set data from the OmniVista 4760 or 4760i.
- On eCom: Enter the acknowledgement code read on the source PCX.

5.10 License: G729A Client (lock 197)

On the destination node, check that lock 13 (E-CS Engine) is sufficient. In addition, ensure that
locks 138 (IP equipments) and 176 (10 IP users) have the same value as lock 197.
Proceed in similar manner as when moving the license for 10 UA fixed users (lock 173).

5.11 License: OmniCellular client for 10 users (lock 308)

On the destination node, check that lock 13 (E-CS Engine) is sufficient.
- On eCom: create new OPS files for the source and destination PCXs.
- On the source PCX:
Export data from Cellular Client sets to be moved to the OmniVista 4760 or 4760i.
Delete the Cellular Client sets.
Install the reduced OPS files.
Read the acknowledgement code.
- On the destination PCX:
Install the increased OPS files.
Reboot the cabinet.
Import the Cellular Client sets from the OmniVista 4760 or 4760i.
- On eCom: Enter the acknowledgement code read on the source PCX.

5.12 License: Class service (CLIP) for 10 analog users (lock 310)
On the destination node, check that lock 13 (E-CS Engine) is sufficient. In addition, if the sets
are assigned to eZ32 boards, check that lock 174 (analog users) is sufficient.
Proceed in similar manner as for lock 2 "Phonebook users".

5-4
    
 
 

6      

6.1 List of Alcatel-Lucent OmniPCX Enterprise CS Locks

A lock is "Open" when it corresponds to a free license. It is then set to 9999 or to 099999 as of
R8.0.
An "unused" lock is set to 0. It is not displayed by the swinst or spadmin commands.
For some locks, the value "0" cannot be used because the first corresponding licenses are
free.
The "Moveable" column indicates whether the lock can be moved or not.
The Reboot required column indicates whether or not it is necessary to restart the system to
apply any changes made to the relevant lock.
Number Name Possible values Moveable Reboot
required
001 Group Telephony Open lock
002 Phonebook users 0/10/20/.../9999 (15000 as Yes No
of R8.0)
003 Not used
004 Hotel guest sets 0/ 50/ 80/ 150/ 350/ 500/ No According to
1000/ 1500/ .../ 9500/ conditions, see:
9999 (15000 as of R8.0) Note 1
(> or = lock 213 if different
from 0)
005 Multilingual voice 0/1 No No
prompts
006 Hotel: AHL on V24 0/1 (= lock 126) No Yes
007 Not used
008 Not used
009 PSTN B channel Open lock
010 Voice guide 0/1 No No
011 Not used
012 DISA 0/1 No No
013 E-CS engine 0/ 50/ 80/ 150/ 250/ 500/ No Yes
1000/ 1500/ .../ 9500/
9999 (099999 as of R8.0)
= 9999 (099999 as of
R8.0) if lock 213 different
from 0
014 Integrated metering 0/1 No No
report
015 Not used
016 Not used

     6-1

Chapter 6    ! "

Number Name Possible values Moveable Reboot

required
017 Not used
018 Not used
019 Corporate networking 0/ 50/ 80/ 150/ 350/ 500/ No No
1000/ 1500/ .../ 9500/
9999 (15000 as of R8.0)
> or = lock 213 if different
from 0
020 Automated attendant 0/ 6/ 9999 (099999 as of No No
R8.0)
021 N0 of VPS ports 0/ 2/ 4/.../ 240 No No
022 Not used
023 Not used
024 Not used
025 Not used
026 Not used
027 Not used
028 Not used
029 DECT/PWT Engine 0/1 No Yes
030 Not used
031 Not used
032 Not used
033 Not used
034 Not used
035 Free Open lock
036 Free Open lock
037 Free Open lock
038 Infocenter link 0/1 No According to
conditions, see:
Note 1
039 Performance 0/ 50/ 80/ 150/ 350/ 500/ No No
1000/ 1500/ .../ 9500/
9999 (15000 as of R8.0)
(> or = lock 213 if different
from 0)
040 Real Time Incidents 0/ 50/ 80/ 150/ 350/ 500/ No No
1000/ 1500/ .../ 9500/
9999 (15000 as of R8.0)
(= lock 047)

6-2
    
    ! "

Number Name Possible values Moveable Reboot

required
041 DECT register 0/ 50/ 80/ 150/ 350/ 500/ No No
1000/ 1500/ .../ 9500/
9999 (099999 as of R8.0)
(= lock 050)
042 Accounting users 0/ 50/ 80/ 150/ 2350/ 500/ No No
1000/ 1500/ .../ 9500/
9999 (15000 as of R8.0)
(> or = lock 213 if different
from 0)
043 Not used
044 4059 SBC 0/ 1/ 2/.../ 50 No According to
conditions, see:
Note 2
045 4059 BLF 0/ 1/ 2/.../ 30 No According to
conditions, see:
Note 2
046 Fax server ABC-A link 0/ 1/ 2/.../ 28 No According to
conditions, see:
Note 3
047 Alarms 0/ 50/ 80/ 150/ 350/ 500/ No No
1000/ 1500/ .../ 9500/
9999 (15000 as of R8.0)
(> or = lock 213 if different
from 0)
048 Not used
049 Directory 0/ 50/ 80/ 150/ 350/ 500/ No No
1000/ 1500/ .../ 9500/
9999 (15000 as of R8.0)
(> or = lock 213 if different
from 0)
050 Configuration 0/ 50/ 80/ 150/ 350/ 500/ No Yes
1000/ 1500/ .../ 9500/
9999 (15000 as of R8.0)
(> or = lock 213 if different
from 0)
051 Real Time Metering on 0/ 50/ 80/ 150/ 350/ 500/ No No
V24 1000/ 1500/ .../ 9500/
9999 (15000 as of R8.0)
(= lock 042)
052 4635: Basic package 0 = none No According to
1 = 4635J conditions, see:
Note 3
2 = 4635H
053 Not used -

     6-3

Chapter 6    ! "

Number Name Possible values Moveable Reboot

required
054 Not used
055 Not used
056 4635: Networking 0/ 2/ 4/.../ 64 No According to
OctelNet (= lock 057) conditions, see:
Note 3
057 4635: Fax manager 0/ 2/ 4/.../ 64 No According to
conditions, see:
Note 3
058 4635: Call manager 0/ 2/ 4/.../ 64 No According to
(= lock 057) conditions, see:
Note 3
059 4635: Hotel manager 0/ 2/ 4/.../ 64 No According to
(= lock 057) conditions, see:
Note 3
060 4635: No of ports 0/ 2/ 4/.../ 64 No According to
conditions, see:
Note 3
061 4635: No of hours 0/ 5/ 10/.../ 40 No According to
conditions, see:
Note 3
062 4635: No of languages 0/ 1/ 2/.../ 8 No According to
conditions, see:
Note 3
063 4635: Attendant 0/ 2/ 4/.../ 64 No According to
manager (= lock 057) conditions, see:
Note 3
064 Not used
065 4635: Recording 0/ 2/ 4/.../ 64 No According to
manager (= lock 057) conditions, see:
Note 3
066 4635: Networking AMIS 0/ 2/ 4/.../ 64 No According to
(= lock 057) conditions, see:
Note 3
067 Not used
068 Not used
069 Not used
070 Not used
071 Not used
072 Not used
073 Not used
074 Not used

6-4
    
    ! "

Number Name Possible values Moveable Reboot

required
075 Network Hospital Open lock
(specific to France)
076 CCD agents 0/ 5/ 10/.../ 2000 Yes No
077 CCS mono-site 0/ 1/ 2/.../ 60 No No
078 CRI call record interface 0/1 No No
079 ISVPN 0/ 50/ 80/ 150/ 350/ 500/ No No
1000/ 1500/ .../ 9500/
9999 (15000 as of R8.0)
(= lock 019)
080 VPN 0/ 50/ 80/ 150/ 350/ 500/ No No
1000/ 1500/ .../ 9500/
9999 (15000 as of R8.0)
(= lock 019)
081 Meet me conference 0/ 1/ 2/.../ 30 No No
082 No of DECT/PWT 0/ 10/ 20/ ..../ 5000 No No
terminals (= lock 175)
083 Flow Metering on 0/ 50/ 80/ 150/ 350/ 500/ No According to
Ethernet 1000/ 1500/ .../ 9500/ conditions, see:
9999 (15000 as of R8.0) Note 4
(= lock 042)
084 4635 users 0/ 50/ 80/ 150/ 350/ 500/ No No
1000/ 1500/ .../ 9500/
9999 (15000 as of R8.0)
(> or = lock 213 if different
from 0)
085 Not used
086 Automatic directory pop 0/ 1/ 2/.../ 50 No According to
up conditions, see:
Note 2
087 Beta test release 0 = Alcatel-Lucent No No
OmniPCX Enterprise CS
version released
8 = Beta test OXE R5.0LX
9 = Beta test OXE R5.1
10 = Beta test OXE R6.0
11 = Beta test OXE R6.1
12 = Beta test OXE R6.11
13 = Beta test OXE R6.2
088 Not used
090 Mobility: Roaming 0/ 10/ 20/ .../ 5000 Yes No
DECT/PWT

     6-5

Chapter 6    ! "

Number Name Possible values Moveable Reboot

required
091 Voice guide recording 0/ 1 No No
from Reflexes sets
092 Not used
093 4635J 0/ 1 No
IDENTIFICATION
094 WMI Workforce 0/ 1 No No
management interface
095 Not used
096 Not used
097 VPS users 0/ 50/ 80/ 150/ 350/ 500/ No No
1000/ 1500/ .../ 9500/
9999 (099999 as of R8.0)
(> or = lock 213 if different
from 0)
098 Accounting for local 0/ 50/ 80/ 150/ 350/ 500/ No Yes
calls 1000/ 1500/ .../ 9500/
9999 (15000 as of R8.0)
(> or = lock 213 if different
from 0)
099 Accounting for ABC 0/ 50/ 80/ 150/ 350/ 500/ No Yes
calls 1000/ 1500/ .../ 9500/
9999 (15000 as of R8.0)
(> or = lock 213 if different
from 0)
100 CSTA profile 0 = None No Yes
2 = Call center
101 CSTA monitoring 0/ 5/ 10/.../ 9995/ 9999 No Yes
requests (099999 as of R8.0)
the Maximum depends on
OXE release.
102 CCS multi-site 0/ 1/ 2/.../ 60 No No
103 Real Time Interface 0/ 1/ 2/.../ 60 No No
104 Not used
105 Compressed calls 0/ 1/ 2/.../ 9999 (099999 No No
as of R8.0)
106 Transfix Access Open lock - -
X24/V36
108 - Not used -
109 4635 : IP Octel 0/ 2/ 4/.../ 64 No According to
Networking (= lock 057) conditions, see:
Note 3

6-6
    
    ! "

Number Name Possible values Moveable Reboot

required
110 4635 : Global message 0/1 No According to
redundancy conditions, see:
Note 3
111 Ubiquity 0/ 10/ 20/.../ 15000 No No
112 CCS LIGHT 0 / 1 / 2 / ... / 60 No No
113 CSTA pilots monitoring 0/ 1 No Yes
114 TSAPI server 0/ 5/ 10/.../ 2000 No Yes
115 CCA softphone 0/ 5/ 10/.../ 1000 No No
(< or = lock 076 if different
from 0)
116 OTUC Local My Phone 5/ 10/ 20/.../ 3000 No Yes
(= lock 129)
117 OTUC Local 4980 5/ 10/ 20/.../ 3000 No Yes
Option (< or = lock 129 if different
from 0)
118 Not used
119 4980 nomadic logged 5/ 10/ 20/.../ 600 No Yes
(= lock 129 + lock 309)
120 Not used
121 CLIP on VPS 0/ 2/ 4/.../ 240 No No
(= lock 021)
122 ACAPI via CMIP 0/ 50/ 80/ 150/ 350/ 500/ No No
1000/ 1500/ .../ 9500/
9999 (099999 as of R8.0)
(= lock 050)
123 CSTA IVR ports 0/ 5/ 10/.../ 5000 No Yes
monitored
124 Not used
125 CCWeb Agents 0/ 5/ 10/.../ 1000 No No
(< or = lock 076 if different
from 0)
126 Hotel AHL link 0/ 1 No Yes
127 Encryption DECT/PWT 0/ 10/ 20/.../ 5000 Yes No
users
128 4615 No. of Access 0/ 2/ 4 No No
129 ECC My softphone 5/ 10/ 20/.../ 3000 No Yes
(4980 Grp)
130 CSTA: Voice Recording 0/ 1/ 2 No Yes
Type
131 Remote LIO 0/ 16/ 32/ 48/ .../ 16xN No No

     6-7

Chapter 6    ! "

Number Name Possible values Moveable Reboot

required
132 IP-Trunk 0/ 9999 (099999 as of No No
R8.0)
(= lock 187)
133 Mastered conference 0/ 50/ 80/ 150/ 350/ 500/ No No
1000/ 1500/ .../ 9500/
9999 (15000 as of R8.0)
(> or = lock 213 if different
from 0)
134 Multi-tenant 0/ 50/ 80/ 150/ 350/ 500/ No No
1000/ 1500/ .../ 9500/
9999 (15000 as of R8.0)
( > or = lock 213 if
different from 0)
135 G729A Server 0/ 1/ 2/.../ 9999 (099999 No No
as of R8.0)
136 Priority 0/ 50/ 80/ 150/ 350/ 500/ No No
1000/ 1500/ .../ 9500/
9999 (15000 as of R8.0)
(> or = lock 213 if different
from 0)
137 Call restriction 0/ 50/ 80/ 150/ 350/ 500/ No No
1000/ 1500/ .../ 9500/
9999 (15000 as of R8.0)
(> or = lock 213 if different
from 0)
138 IP Clients 0/ 10/ .../ 9999 (15000 as No Yes
of R8.0)
(= lock 176 + lock 317+
lock 330)
139 Not used
140 Not used
141 Not used
142 Not used
143 TAPI premium server 0/ 5/ 10/.../ 5000 No Yes
144 Not used
145 CSTA Recording B 0/ 5/ 10/.../ 600 No Yes
Channel
146 PWT MOBILITY 0: non US market No No
(UTAM) 1: US market
(according to lock 029)
147 Not used
148 IP Call Server Open lock - -

6-8
    
    ! "

Number Name Possible values Moveable Reboot

required
149 Not used
150 Not used
151 4635 : VPIM 0/2/4/.../64 No According to
(= lock 057) conditions, see:
Note 3
152 Radio link 0/1 No No
153 SNMP TRAP 0/1 No Yes
154 Additional S0 features 0/1 No No
155 Additional safety 0/1 No No
features
156 Interphony features 0/1 No No
157 CCA nomadic 0/1 No No
158 CSTA By-pass 500/ 1000/ 1500/ .../ 9500/ No Yes
9999 (099999 as of R8.0)
the maximum depends on
the OXE release.
159 Not used
160 CCemail Agents 0/5/10/.../1000 No No
161 CCoutbound Agents 0/5/10/.../1000 No No
162 CCoutpredial Agents 0/5/10/.../1000 No No
163 Not used
164 CSTA Record 0/5/10/.../600 No Yes
networked
165 Alcatel-Lucent 30 = R5.0 LX No No
OmniPCX Enterprise 31 = R5.1
CS release
32 = R6.0
33 = R6.1
34 = R6.2
166 4980 multi device 5/10/20/.../3000 No Yes
(= lock 129)
167 ACR data base read 0/ 1 No No
168 No. of HPOV node 0/ 1/ 2/.../ 100 No No
169 Voice detection 0/ 1/ 2/.../ 315 No No
channels
170 Not used
171 Not used
172 Not used
173 Business Users 0/ 10/ 20/.../ 5000 Yes No
174 Analog Users 0/ 10/ 20/.../ 5000 Yes No

     6-9

Chapter 6    ! "

Number Name Possible values Moveable Reboot

required
175 Mobile Users 0/ 10/ 20/.../ 5000 Yes No
176 Business IP Users 0/ 10/ 20/.../ 5000 (15000 Yes No
as of R8.0)
177 SIP Users 0/ 10/ 20/.../ 1000 Yes No
178 4645 : Voice mail 0/ 1/ 2/ 3 No According to
engine conditions, see:
Note 2
179 4645 users 0/ 50/ 80/ 150/ 350/ 500/ Yes According to
1000 (15000 as of R8.0) conditions, see:
Note 3
180 Not used
181 Alcatel-Lucent 1 = Alcatel-Lucent No No
OmniPCX Enterprise OmniPCX Enterprise CS
CS
182 4645 : networking 0/ 1 No According to
conditions, see:
Note 3
183 4645 : additional 0/ 1/ 2/.../ 7 No According to
language conditions, see:
Note 3
184 Integrated Gatekeeper 0/ 1 No Yes
185 SIP Gateway 0/ 1 No Yes
186 E-CS redundancy 0/ 1 No Yes
187 H.323 (G711) network 0/ 1/ 2/.../ 1000 No According to
link conditions, see:
Note 5
188 SIP networking links 0/ 1/ 2/.../ 1000 No According to
conditions, see:
Note 5
189 CCTI agents 0/ 5/ 10/.../ 1000 No No
190 RSI call center agents 0/ 5/ 10/.../ 2000 No Yes
191 Campus DECT 0/ 1 No No
192 T2 D_REX protocol 0/ 1 No No
193 Embedded voice guides 0/ 1 No Yes
194 4645 My Messaging 0/ 10/ 20/.../ 1000 No According to
users conditions, see:
Note 3
195 CCD profil 0 = None No Yes
1 = Starter
2 = Server
(according to lock 076)
196 RSI Business agents 0/ 5/ 10/.../ 1000 No Yes

6-10
    
    ! "

Number Name Possible values Moveable Reboot

required
197 G729A Client 0/ 10/ 20/.../ 4000 Yes No
198 Not Used
199 Version 4400R5.0 Ux 0/ 1 No No
200 4400 Mobiles migration 0/ 1/ 2/... /5000 No No
201 4400 Reflexes 0/ 1/ 2/... / 5000 No No
migration
202 4400 Analogs migration 0/ 1/ 2/... / 5000 No No
203 Upgrade CCS ligth to 0/ 1/ 2/ .../ 60 NO No
CCS monosite < or = lock 112
204 - - Not used -
212
213 ECS engine physical 0 / 50 / 80 / 150 / 350 / No No-
users 500 / 1000 / 1500 / ... /
9500 / 9999 (099999 as of
R8.0)
214 - - Not used -
299
300 swk file edition 0 No No
301 hard key 1 0 No No
302 hard key 2 0 No No
303 ACK 1 0 No No
304 ACK 2 0 No No
305 ACK 3 0 No No
306 ACK 4 0 No No
307 ACK 5 0 No No
308 Remote extension 0/ 5/ 10/ 15/ 20/.../ 5000 No No
(GSM interworking)
309 XML telephony 0/ 10/ 20/.../ 3000 No Yes
310 CLIP Z 0/ 10/ 20/.../ 5000 Yes No
311 ACR networking 0/ 1 No No
312 Scripting agents 0/ 5/ 10/.../ 1000 No No
313 ECC platform 0/1/ 2/ 3 No No
314 4635 : My Messaging 0/ 10/ 20/.../ 5000 No According to
users conditions, see:
Note 3
315 Hard 0223 Key 0/ 1 No Yes
migration
316 Standard Reflexes 0/ 10/ 20/30.../ 5000 Yes No
Users (with services
restriction)

     6-11

Chapter 6    ! "

Number Name Possible values Moveable Reboot

required
317 Standard IP Users (with 0/ 10/ 20/.../ 5000 (15000 Yes According to
services restriction) as of R8.0) conditions, see:
Note 5
318 Max number of 0/ 1/ 2/... No No
connections to
applications server
(PRS)
319 EasyContact 0 = None No No
1 = EasyContact
320 Not used
321 Mobile IP-Touch 0/ 10/ 20/ .../ 100 (OXE No No
R6.1)
0/ 10/ 20/ .../ 500 (OXE
R6.2)
322 CSTA Beyond 9999 0/1 No No
instances (099999
instances as of R8.0)
323 Executive Users 0/ 10/ 20/ .../ 5000 No No
324 Executive IP Users 0/ 10/ 20/ .../ 5000 (15000 No No
as of R8.0)
325 IP-Touch Security 0/ 1 No No
Engine
326 Secured IP-Touch 0/ 10/ 20/ .../ 5000 Yes No
Phones
327 IP-Touch Security MCM 0/ 1/ 2/ .../ 120 Yes No
328 IP-SoftPhone Attendant 0/ 1/ 2/ .../ 50 Yes No
329 IP-SoftPhone Agent 0/ 10/ 20/ .../ 5000 Yes No
330 Advanced Mobile 0/ 1/ 2 .../ 5000 (15000 as Yes No
IP-Touch of R8.0)
332 PCS Max Numbers 1/2/ /240 Yes No
333 Not Used
334 CSTA Maximum 0/5/10/15 ... No No
Number of IP
Recordings
335 Number of Greeting 0/ 1/ 2/ 3 Yes Yes
Assistant
336 Number of stations with 0/ 1/ 2/ 3/ 4../ 15000 No No
IME
337 SIP External Voice Mail 0/ 1 Yes No
338 - Not used
463
464 Not used

6-12
    
    ! "

Number Name Possible values Moveable Reboot

required
465 Not used
466 Not used
467 ARS 0/ 50/ 80/ 150/ 350/ 500/ No No
1000/ 1500/ .../ 9500/
9999 (15000 as of R8.0)
(> or = lock 213 if different
from 0)
468 Not used
469 G723.1 Server 0/n No No
470 - Reserved Open lock
866

6.1.1 Note 1
The Hotel option is validated if the value of one of the following locks is different from 0:
- Lock 004: Hotel Guest set
- Lock 038: Infocenter link
When new OPS files (containing these locks) are installed and these files validate the Hotel
option, a reboot is required.
When the Hotel option has already been validated, a reboot is not required when new OPS
files increase these locks.

6.1.2 Note 2
The ABCA option is validated if the value of one of the following locks is different from 0:
- Lock 044: 4059 SBC
- Lock 045: 4059 BLF
- Lock 086: Automatic directory pop up
- Lock 178: 4645 Voice mail engine
The ABCA option is also validated if the value of one of the following parameters of the
hardware.mao file is different from 0:
- Nb of BLF
- SBC
- 4635x
- 4630
- 4855
When new OPS files (containing these locks) are installed and these files validate the ABCA
option, a reboot is required.
When the ABCA option has already been validated, a reboot is not required when new OPS

     6-13

Chapter 6    ! "

files increase these locks.

6.1.3 Note 3
Locks 46, 52, 56, 57, 58, 59, 60, 61, 62, 63, 65, 66, 107, 108, 109, 110, 151, 179, 182, 183,
194, 314: These parameters can be increased without reboot, provided the ABCA option is
enabled.

6.1.4 Note 4
Lock 83: this parameter can be increased without reboot only when accounting is started.

6.1.5 Note 5
Lock 187, 188, 317: These parameters can be increased without reboot provided compression
was used before the new SWK file installation.

6-14