Licensing requirements

Last Updated : Oct 28, 2025 |
Prolog information
Metadata
Keywords:
POM is a managed application on Avaya Experience Portal. The license requirement and the availability of POM depend on Avaya Experience Portal.
Experience Portal Manager (EPM) contacts Avaya WebLM server to determine the number of licenses that are authorized for your POM application. After receiving information about the authorized licenses, EPM allocates the available licenses among the Media Processing Platform (MPP) servers in the system. For security reasons, ensure that the license server runs WebLM version 4.4 or later, and install a valid Avaya Experience Portal license on the license server.
Avaya Experience Portal requires licenses for the following components:

Experience Portal

Component
Description
Telephony ports
The number of telephony connections or ports. You can use one connection or port for voice activities with each license. An Avaya Experience Portal system supports up to 10,000 telephony ports.
For agent-based campaigns, you need a telephony port each for:
  • enabling an agent nail-up connection
  • dialing out a customer
  • bridging the agent nailed-up call with the customer call.
The third port is used for bridging the connection and then released.
Note:
To configure an authorized telephony port on the Avaya Experience Portal system, you must establish an H.323 or SIP connection. For agent-based campaigns, you must have a SIP connection.
Automatic Speech Recognition (ASR) connections
The number of ASR connections or ports. You can use one connection or port for speech recognition activities with each license. If you do not purchase any ASR licenses, you cannot configure ASR servers on your system.
You need one ASR license for each call that requires ASR resources. The license becomes available again after the call is complete.
Text-to-Speech (TTS) connections
The number of TTS connections or ports. You can use one connection or port for speech recognition activities with each license. If you did not purchase any TTS licenses, you cannot configure TTS servers on your system.
You need one TTS license while a call is using TTS resources. When the call stops using TTS resources, the license becomes available to other calls.
SMS licenses
The number of SMS licenses. You must configure adequate number of SMS licenses to run SMS campaigns. For more information about SMS licenses, see Avaya Experience Portal documentation.
Email licenses
The number of Email licenses. You must configure adequate number of email licenses to run email campaigns. For more information about email licenses, see Avaya Experience Portal documentation.

Proactive Outreach Manager

POM uses separate licenses for Outbound ports, Manual agents, Preview agents, Predictive agents, and Agent Web API Service. You can allocate licenses to different zones and then to different organizations under each zone. If you do not have zones, all licenses are assigned to the default zone and default organization.
Component
Description
Maximum Outbound Ports
Displays the number of ports configured for Outbound calls for Agentless Notification campaigns.
Important:
Configure outbound ports equal to or less than the telephony ports configured in Avaya Experience Portal.
Manual Agents
Displays the number of Manual agent licenses configured for Manual campaigns.
Predictive Agents
Displays the number of Predictive agent licenses configured for Predictive campaigns.
Preview Agents
Displays the number of Preview agent licenses configured for Preview campaigns.
Agent Web API Service
Displays the number of licenses for Agent Web API service. Use this when integrating an Agent Desktop with POM.
SMS Channels
Displays a boolean license. If you have SMS licenses, the value is non-zero else the value is zero. The presence of this license allows POM to utilize the Avaya Experience Portal Email capability.
EMAIL Channels
Displays a boolean license. If you have email licenses, the value is non-zero else the value is zero. The presence of this license allows POM to utilize the Avaya Experience Portal Email capability.
Version
Displays the current major version of POM.
Last Successful Poll
Displays the time stamp of the last successful instance of POM polling.
Last Changed
Displays the time stamp of the last changes.
icon
Use the icon to edit the license information.
Note:
License allocation can be either reserved or dynamic as specified in the Campaign Strategy.

Reserved licenses

The licenses which are not reallocated to other jobs or tasks unless recalculation occurs are called reserved licenses.
In case of reserved licenses, the campaign job or task does not release the licenses though the campaign job or task might not need the licenses.
The licenses allocated to the reserved job or task will be retained till the recalculation happens. Jobs or tasks with reserved licenses cannot trigger the recalculation.
The license recalculation can occur when:
  • A new job starts.
  • A job is stopped.
  • A job is paused.
  • A job is resumed.
  • If you change the priority, minimum port, or maximum ports value through the Supervisor Dashboard.
  • A dynamic job is not using the allocated quota, and there are other jobs in the system who need more licenses.
    In case of dynamic jobs with outbound or notification licenses, if the job does not make call attempt for a duration of 1 minute then it is considered that the dynamic job does not need more licenses.
Whenever license recalculation is triggered, the license quota for all jobs is recalculated irrespective of their allocation type.

Dynamic licenses behavior for agentless campaigns

Proactive Outreach Manager helps in allocation and license management with the help of dynamic licensing. Dynamic licensing is useful for a job or a task that does not require all allocated licenses. There are other jobs or tasks that require more licenses than the allocated licenses, simultaneously. With the help of dynamic licensing, the system can release some licenses and assign the licenses to the other jobs or tasks.
You can choose to use reserved licensing or dynamic licensing. If you choose dynamic licensing, you must remember that:
  • Only dynamic jobs or the tasks can donate the additional or excess licenses
  • Any job or the task can borrow the additional or excess licenses
  • No job or the task can use more licenses than the maximum value specified in the campaign strategy
  • Dynamic jobs or the tasks always reserve minimum licenses specified the campaign strategy although the job or task might not need the licenses.
  • Dynamic jobs or the tasks start donating licenses. Only the current job or the task does not request for a license and the other jobs need more licenses.
  • After donating licenses, dynamic jobs or the tasks get the license back only when the dynamic job or the task needs the licenses.
  • The system allocates the licenses that are released by dynamic job to other jobs according to their priorities, and the minimum and the maximum values.

Dynamic licensing behavior for agent based campaigns

POM allocates licenses to the job only when the agents are logged in and are attached to a job, and releases the licenses from the job whenever the agents are detached from the job. When the job snoozes, POM releases all the agents immediately along with the licenses. The license goes back to the license pool. During manual movement of agents, POM moves the licenses too, along with the agents.

Licensing hierarchy

Manual campaigns can work if the customer has Manual, Preview, or Predictive licenses. Manual license is added to the existing agent licenses - Preview and Predictive. The hierarchy of licenses is as follows:
License type
Manual campaign
Preview campaign
Predictive campaign
Predictive
Yes
Yes
Yes
Preview
Yes
Yes
No
Manual
Yes
No
No
  • Predictive license: Can be used for Predictive, Preview, and Manual campaigns
  • Preview license: Can be used for Preview and Manual campaigns.
  • Manual license: Can be used only for Manual campaigns.