Chapter
3
System Services
3.1 Software Licence Management
3.1.1 Software licence management
On an OXO Connect several types of devices may be connected, several services may be offered and
several applications may run.
The purpose of the feature “Software Licence Management” is to define for a given system (i.e.
customer) the service level to offer, this mainly means:
• What devices are allowed and how many of each type.
• Which service is offered.
• Which application is to open.
• How many users are allowed.
• What features the hardware can support.
The SWL (SoftWare Licence) files define the level of service requested.
The software licenses are the encoded result of the service levels and of a unique CPU ID. They
should be loaded during the installation of the system.
The software license can be managed by the normal mode. There is no user definition and the validity
of the license in open state is not limited.
Note:
In Normal mode , the SWL files are loaded to the system or updated manually using OMC
Once SWL files are available on the system in normal mode, it manages the following functions:
• Definition, modification and checking of the service level.
• Dimensioning of a system for a correct service level.
• Limitation of requested services depending on hardware installed.
• Daily or on request checking (by OMC) of the SWL files in order to adapt the service level.
• Information to user and/or installer about the state of system in terms of service level.
3.2 Software Keys
In the OXO Connect system, a software key is represented by an alphanumeric string of characters,
which opens functions. Two software keys correspond to each OXO Connect system:
• the PRINC (PRINCIPAL) software key or MAIN for the system functions (voice, system feature,
etc.)
• the CTI Software key for the CTI functions
The software key corresponds to a text file where the name is the CPU hardware number with
the .MSL (MAIN key) or .CSL (CTI key) extension.
Example:
file 000068DA.msl and 000068DA.csl for main CPU no. 000068DA.
Each system needs the Main and CTI Software keys even if no CTI application is used on the system.
The systems can be delivered with a key that is already personalized for the client. The Distributor
needs to load if necessary the personalized key on the non-factory-configured systems.
3EH21123USAA - Ed. 01 - April 2017 - Installation Manual 33/207
To Next Page
Loading...
