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.

In local and network licensing modes, certain features that were previously treated as instance based (on/off) licenses, are now considered as count based licenses. 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. All the licenses are now count based.

Sonus SBC is enhanced and provides three ways of licensing methods:

  1. Legacy Mode: The Licenses are attached to a particular SBC and this is an xml-based SBC license model.
  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 EMS 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 a SLS server based on demand as traffic increases. When the traffic decreases, the licenses are returned to the server. These licenses can float between SBC 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

Live Monitor for Licensing

The Live Monitor feature tracks and monitors the licenses that are used in the SBC. It is embedded in EMA to provide the usage/metrics, which improves the visibility.

  • Live Monitor does not display licensing metrics in legacy mode.
  • In local license mode, the license limit is fixed.
  • In network wide license mode, the available license limit changes dynamically as licenses are retrieved and returned to the site license server.

To access the Live Monitor option:

  1. Log on to EMA.
  2. Navigate to Monitoring > Dashboard > Live Monitor.

    If you are accessing Live Monitor option for the first time, you must click Enable.

  3. Click Configure Live Monitor to customize and view the licensing metrics.


    1. From the Available Metrics list, select the required items to be monitored. The selected items are added to the Selected Metrics.
    2. Select one of the Data Collection options:
      1. Collect data from all zones and trunk groups - Populates license usage from all zones and trunk groups.
      2. Collect data from selected zones and trunk groups below -  Populates license usage from selected zones and trunk groups.

    3.  Click OK. Selected metrics are displayed.

  4. Click Settings on the specific items for customization.

    If licenses are not installed, the License Usage/Licenses Installed list will be empty.

    1. Select the required option from the Display graph for drop-down list. The value ranges from past 1 hour to past 1 week.
    2. In Licensed Usage/ Licenses Installed drop-down list, choose the appropriate license type.

      RTU Licenses Installed are selected by default. If you want to see the metrics for MRF, select the MRF Usage per Call / MRF-RTU Licenses Installed option.

    3. Click OK.

MRF Session License

In the Microservices SBC architecture, the S-SBC is enhanced to support an external Media Resource Function (MRF) using RFC4117 Session Initiation Protocol (SIP) interaction when transcoding is required. A new session license SBC-MRF-RTU is introduced to support external MRF transcoding and it is count based.

For every media session, an SBC-MRF-RTU session license plus a base SIP session license is required for external MRF transcoding. The MRF can be introduced to the call flow and subsequently removed when it is determined from the peers response that transcoding is not required. Therefore, the SBC-MRF-RTU license is checked for availability when sessions are sent towards the MRF and consumed (counted) only when the answer from the MRF indicates that transcoding is applied.

SBC-MRF-RTU license is supported when the SBC is set to local or network licensing mode.

SBC Session License for Remote PSX Access

SBC software license to restrict usage of the external PSX from the Sonus SBC.  When the SBC is configured for local or network wide licensing the customer must have purchased and applied the SBC-PSX-RTU license before call processing with an external PSX is allowed.