About licensing requirements

Last Updated : Sep 12, 2025 |
Prolog information
Metadata
Keywords:
Avaya SBC uses the Avaya Product Licensing and Delivery System (PLDS) to create licenses and download Avaya SBC software. PLDS is not integrated with WebLM. Use PLDS to perform operations such as license activations, license upgrades, license moves and software downloads.
There are two licensed versions of Avaya SBC:
  • Standard Services delivers non-encrypted SIP trunking.
  • Advanced Services adds Mobile Workspace User, Media Replication, and other features to the Standard Services offer.
Avaya Aura® Mobility Suite and Collaboration Suite licenses include Avaya SBC.
Avaya SBC uses WebLM version 8.0 or later for licensing requirements. You can install the Avaya SBC license file on a primary Element Management System (EMS) using the Device Management page.
Important:
You must not enable the local WebLM option and install an Avaya SBC license file on the secondary EMS if used in an active-active deployment. If you install a license file on a secondary EMS in an active-active deployment, the licensing system will always show that the secondary EMS is in OK state.
Ensure that the license file of the WebLM server displays the product code Session Border Controller E AE. Before you configure the license file, you can view the License State, Grace Period State, and Grace Period Expiration Date fields on the Dashboard page. You have a 30-day grace period from the day of installation or upgrade to install the license. Avaya SBC works normally during the grace period.
Important:
Licenses and a WebLM server are required for new installations or upgrades.
The license file contains the following information:
  • Product name
  • Supported software version
  • Expiration date
  • Host ID
    The primary host ID of WebLM is used for creating the license file.
  • Licensed features
  • Licensed capacity
All hardware Avaya SBC devices can use a local WebLM server for licenses. However, for mixed deployment environments with EMS on VMware and Avaya SBC on hardware, use a WebLM server installed on VMware or System Manager WebLM.
Avaya SBC supports pooled licensing. As opposed to static license allocation, Avaya SBC dynamically reserves and unreserves pooled licenses when needed. For example, customers with multiple Avaya SBC devices can use a pool of licenses dynamically across the devices as required.
For integration with Microsoft® Teams, Avaya SBC requires the Premium license and Premium HA license permissions in addition to the Standard Services and Advanced Services licenses.
For the use of AMR-WB codec, Avaya SBC requires counting license for AMR-WB codec license and AMR-WB codec HA tracking license. This is applicable to both static and dynamic licenses.
Initial Grace PeriodInitial Grace Period is when Avaya SBC is newly installed and has no connection established to licensing server. When in initial grace period Avaya SBC only allows 100 licenses per feature.
Grace PeriodGrace Period is when Avaya SBC loses its connection to licensing server after serving. In Dynamic Licensing Mode, when in Grace Period, State licensing statistics would show 0 and will be updated when connections with the licensing server are restored.
On upgrading to 10.2.1, EMS might display following warnings:
  • This system has one or more SBC(s) that does not have a valid AMR license configuration.
    This may cause calls to fail or may cause other problems with the attached SBC(s). Check the device settings and license settings to ensure that calls will be processed properly.
  • This system has one or more SBC(s) that appear to have no licensing configuration.
    This may cause calls to fail or may cause other problems with the attached SBC(s). Check the device settings and license settings to ensure that calls will be processed properly.
These warnings can be corrected by properly configuring licenses for all required features.