A license is an authorization given to the end-user to use the application legally and specifies the terms of use. License enforcement is implemented on SBC to ensure that licensed functionality is restricted to the amount of sessions or licensed features purchased.

A count based license can be dynamically floated and shared among the SBC in a network licensing mode. It also allows the enforcement of the number of sessions purchased in local and network licensing modes. 

The SBC supports three license modes:

  1. Legacy Mode: The Licenses are encoded to a unique SBC instance based on system information to a particular SBC and this is an xml-based SBC license model.

    Legacy licensing mode is only supported for hardware platforms of SBC 5xx0 and SBC 7000.

  2. Local Mode: The licenses are fixed to the SBC and cannot be shared by other devices in the network. Licenses are installed on SBC through EMA or a new CLI interface by applying an xml-based license bundle. The xml-based license adopts the new license format, which includes additional data such as purchase order information.

  3. Network Mode: The licenses are assigned dynamically by an SLS server based on demand as traffic increases. When the traffic decreases, the licenses are returned to the server. These licenses can float between SBCs based on the demand. Licenses are pooled centrally in the SLS server which is co-located with the EMS.

The system supports a countable license in the range of 0-x units:

 License Encoded with Fingerprint Capability

License Floating

License floating enables a limited number of licenses to be shared among a number of network devices It is applicable when the SBC is deployed on network wide licensing with a centralized SLS distributing licenses to the SBCs connected to it.

License Floating Functionality

License Deletion

There are two ways to delete a license:

The license deletions are allowed:

Any existing sessions that are initiated prior to the license being removed can continue, but new calls will be denied access to the associated licensed functionality.

License Expiry


For information related to Alarms/Traps, refer to Alarm Changes.

For CLI configuration, refer to Configuring License Using CLI.