Avaya Experience Portal licenses

Last Updated : Mar 05, 2025 |
Prolog information
Metadata
Keywords:
Experience Portal Manager (EPM) contacts an Avaya WebLM server to determine the number of licenses authorized for your account. For security reasons, the license server must run WebLM 8.1 or later versions. Install a valid Avaya Experience Portal release 8.x license on the license server. You must reinstall the license file while upgrading from a previous Experience Portal version that uses an older WebLM version.
To eliminate any timing-related issues when multiple Experience Portal systems try to access the license server, use the enterprise license model for sharing a license between multiple Experience Portal systems. This configuration enables the controlling of the license values. Experience Portal supports direct access to the licenses when a single Experience Portal system accesses the license server.
After receiving the current information about the authorized licenses, Experience Portal allocates the available licenses among the servers.
Experience Portal requires a license for the following entities:
Component
Description
Telephony ports
Each license authorizes you to use a single port for the telephony activities.
Note:
To configure an authorized telephony port on your Experience Portal system, establish an H.323 or SIP connection.
Automatic Speech Recognition (ASR) connections
Each license authorizes you to use a single connection or port for speech recognition activities. If you do not purchase an ASR license, you cannot configure an ASR server on your Experience Portal system.
You need an ASR proxy license for each call that requires ASR resources. The license is unavailable until the call is completed.
Google Automatic Speech Recognition (ASR) connections
Each license authorizes you to use one connection for the Google Speech Recognition engine. If you do not purchase any Google ASR licenses, you cannot use configured Google ASR servers on your Experience Portal system.
Note:
The Google Speech Recognition engine is also called Google Cloud Speech-to-Text, a cloud-based speech transcription service that transcribes speech into text. For more information on Google Speech Recognition, see Google Speech recognition.
Text-to-Speech (TTS) connections
Each license authorizes you to use one connection or port for the speech synthesis activities. If you do not purchase any TTS licenses, you cannot configure TTS servers on your Experience Portal system.
You need one TTS proxy license while a call uses the TTS resources. As soon as the call stops using the TTS resources, the license becomes available to other calls.
Google Dialogflow Connections
Each license authorizes you to use one connection for the Google Dialogflow service. If you do not purchase any Google Dialogflow licenses, you cannot use any configured Google Dialogflow servers on your Experience Portal system.
For more information, see Google Dialogflow.
Conversation Speech Connections
Each license authorizes you to use one connection for a conversation speech service such as Nuance Mix DLGaaS. If you do not purchase conversation speech connection licenses, you cannot use any configured Nuance Mix DLGaaS service on your Experience Portal system.
Call Anchoring Ports
Defines the number of Call Anchoring Ports on your Experience Portal system.
This setting is for the maximum number of calls that can be simultaneously anchored at a time.
Zones
Defines the licenses required for configuring zones in the Experience Portal system.
If the value is non-zero (positive), the zone feature is enabled. If the value is zero, the zone feature is disabled.
Email units
Defines the licenses required for configuring the email resources, such as email processors and email connections.
The licenses features for email units provide the ability to charge customers according to the capacity required.
SMS units
Defines the licenses required for configuring SMS resources (SMS processors and SMPP/HTTP connections).
The licenses features for SMS units provide the ability to charge customers according to the capacity required.
HTML Units
The number represents the daily HTML processing capacity on your Experience Portal system. An HTML unit is required to handle an incoming HTML request.