Rss Categories

Legacy On-Premise Licensing Overview

Reference Number: AA-02037 Views: 4573 0 Rating/ Voters

Deprecated: Legacy (On-Premise) Licensing

As of the summer of 2016, all Legacy Licensing was deprecated. All users are now advised to use the Flexible Licensing model.

How LumenVox On-Premise Licenses Work

There are two separate components to LumenVox On-Premise licensing. One is the License Server, which hosts and distributes licenses to clients. The other is the license client, which obtains and validates the licenses. The client can be a number of different components depending on how you are using the LumenVox software:

  1. In many cases, the license client is the LumenVox Media Server. This is true in any deployment that uses MRCP, such as most VXML platforms.
  2. A custom application that makes use of the LumenVox C or C++ API for ASR or TTS is a license client (in this case the client is the application which is linked against the LumenVox libraries).
  3. When you run the LumenVox Speech Tuner, it requires licenses and is thus a license client.

When the License Server is started, it loads all of the licenses it has installed. This group of licenses is called the license pool. When a client requests a resource (e.g., a decode from the ASR), it sends a message to the License Server to see if any licenses are available. A valid license is required for each active connection between the LumenVox client application and the ASR/TTS server.

When the License Server receives a request for a license, it checks its license pool and if the appropriate license is available, the License Server assigns that license to the requesting product. The License Server sends the product a license token that lets the product know that the license is available. The License Server removes that license from the pool until the product returns it.

All of this communication between the License Server and its clients happens over a proprietary version of TCP.

Licenses are tied to the machine on which they are installed and are not intended to be moved from one machine to another. They can be uninstalled from one machine and the uninstalled deployment on the website can be used in a fresh installation on a new machine by generating a server ID file from the new machine.

The client software can be installed on a machine separate from the License Server, meaning you can store all of your licenses on one machine and have multiple machines running different clients all looking at a single License Server for licenses. A client can also use more than one server, allowing for very flexible, redundant deployment options.

The On-Premise Licensing Process

The licensing process differs depending on whether you are installing licenses on your own License Servers or are using LumenVox' hosted licenses (as is the case for users with subscription licenses). If you are using subscription licenses, please see our documentation on using subscription licenses.

For users who will be hosting their own On-Premise licenses, the process is as follows:

  1. To get started licensing, the first thing you must do is to create a license Deployment.
  2. Next, after installing the License Server, generate a server ID file.
  3. Then you must upload that file and download a license file.
  4. Finally, install the license file.