Initialization and Periodic Checking

Last Updated : Dec 12, 2023 |
Prolog information
Metadata
Keywords:
Within the License file is the feature mask, an information set that controls which features are enabled or not on the Customer Options and Special Applications screens. Each of the approximately 150 feature mask entries is one of the following three types:
  • Type I: features with a simple on or off state, for example, DCS Call Coverage.
  • Type II: features with an alphanumeric setting value associated with them, for example, Logged-in ACD Agents.
  • Type III: includes the product ID, for example, license serial identification number, release number, and capacities.
    Type III features cannot be changed by any login, for example, applies to IP Telephones, IP Softphones, and IP Agent.
    License error messages
    Name of the mode
    Error message displayed
    Description
    No-License
    License File is Missing or Corrupted
    License could not be decrypted.
    Checksum did not match, data possibly lost.
    Mismatched settings:
    • Offer Category
    • Version
    • Call Center Release
    • Model
    Min. and Max. values of “* and # in vector collect step” do not match the License file.
    IP product defined in translations but not defined in the License file.
    No-License
    The License has Expired
    The License has expired.
    No-License
    Software Version Mismatch
    The current software version does not match the software version in the License file.
    No-License
    Offer Category Mismatch
    The Offer Category in translation does not match the Offer Category in the License file.
    License-Error
    Golden IPSI Not Responding G430/G450 Motherboard Not Responding
    The reference source’s serial number does not match the serial number in the License file, or the reference source is not responding.
    License-Error
    Feature Usage Exceeds Limits
    The value of the Used field for any TYPE II or TYPE III field on the Customer Options forms pages 1, 5, 6, and 9 is greater than the value of the field.
    To identify which of these TYPE II and TYPE III features is causing the error more quickly, compare the Used field with the value of the field itself in the License file value.
    Before usage is checked, if the value of the field is not between the upper and lower values in the License file, the value of the field is changed in translation to the lower value in the License file.