Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

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.



The SBC provides three ways of licensing methodssupports 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 EMS 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 SBC SBCs based on the demand. Licenses are pooled centrally in the SLS server which is co-located with the EMS.


  • From the xml bundle at CLI or EMA for a local license and legacy licenses.

  • From the Required License Table, in case of network licensing.



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

  • In a local or legacy license mode - Once the license is expired, the SBC treats the licensed functionality as disabled system wide. Any existing sessions that are active on expiry continues unimpaired.
  • In a network license mode - Once the license is expired, the SLS does not
  • serve any more
  • serve expired licenses to the SBC.

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.






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