V-Blaze and V-Cloud Online Help

V‑Blaze Licensing

Internet-based Licensing

Internet-based licensing is a robust and efficient framework that enables Voci and its customers to adapt to varying needs. Internet-based licensing operates through real-time, bi-directional messaging over an encrypted HTTPS connection between a host running V‑Blaze software and Voci's license server.

Note

An HTTPS proxy service can be used in cases where environmental or security restrictions are in place. Outbound access to the Voci license server is required over HTTPS for internet licensing to work.

There are two Internet-based license types:

Permission-based licensing

A permission license allows a requester to execute and perform the task of transcribing audio. This type of license also specifies the number of V‑Blaze instances that can run concurrently (only one instance of V‑Blaze can run on a single server) across multiple hosts, as well as specifying the various language models and ASR features available for transcription, license expiration date, and other tuning parameters.

Usage-based licensing

Usage licenses provide blocks of usage (in units of hours) that allow audio processing. In some cases, multiple usage licenses may be made available to distinguish or track utilization of different models, features, or process flows.

You can request more than one usage-based license. For example, each license can be used to transcribe various amounts of audio with different language models. If multiple licenses are available, V‑Blaze uses the license that best matches the features required for processing requests.

Requester

A requester is a unique name used by the license server to identify each running instance of Voci software. The license server also uses the requester name to report interactions with each system running Voci software. Requester names are created dynamically using the system-defined hostname. Alternatively, the requester name can be specified within the worker.cfg configuration file.

Token

Authorization tokens ensure that the requester contacting the license server is running a legitimate V‑Blaze instance and determines which particular licenses are available. One or more authorization tokens can be assigned for tracking purposes if a different combination of licenses is required. Authorization tokens are linked to billing accounts and should be protected as a shared secret. Additional tokens should be requested when deploying systems to remote/customer premises so that authorization to operate can be revoked without cancelling the entire billing account.

File-based Licensing (Legacy)

File-based or static licenses can also be used to allow ASR operation. If a file-based license is in use, the file will be located in /opt/voci/license.

Note

In specific circumstances, a static license file can be issued to allow limited operation in a completely disconnected mode. File-based licensing is uncommon and not recommended.