This section describes the licensing process on the SBC Edge and SBC SWe Lite systems. 

The SBC Edge is delivered with standard functions. For additional SBC Edge features and supplementary services (which are not available as standard functions of the SBC Edge), you must obtain software licenses purchased from Ribbon. Once obtained, you receive instructions for accessing the licensing portal. Through the portal, you enter the SBC serial number and generate a license, which you then install on the SBC Edge (Refer to Installing Licenses). This process also applies to license upgrades/expansions.

SBC 1000, SBC 2000 Licenses

General Licenses

Feature licenses enable features or supplementary services not available as standard functions on the physical SBC Edge, such as increased SIP to/from (↔) SIP sessions or enabling physical ports on the FXS, FXO, BRI and PRI-related hardware modules/line cards. See below for a list of available feature licenses.

SBC 1000 Gateway License Concepts

Ribbon offers the SBC 1000 in basic gateway configurations to address cost-sensitive and basic TDM ↔ IP deployments. By offering the SBC 1000 in a gateway configuration, Ribbonprovides you with the flexibility to select the most cost-effective session border controller solution for your network.

Premium Features

To support the cost sensitive deployments, a subset of SBC features ("Premium Features") are initially deactivated. This includes the following features that are activated through feature/supplementary service license:

Premium Feature "Top-Up" Licenses Available for SBC 1000 Gateway Configurations

Ribbon offers an option in the SBC 1000 to "top-up" the gateway to a comparable standard SBC configuration. With the top-up, the device activates all premium features that do not require a feature/supplementary service license; the device also accepts and no longer ignores any feature/supplementary service licenses. To top-up an SBC 1000 gateway, purchase and apply the appropriate Premium Feature Flag License listed below:

SBC SWe Lite Licenses

Overview

Ribbon Communications offers customers deploying the SBC SWe Lite with a wide variety of licenses to tailor the SBC to address the required enterprise use case at minimal costs. The features are available in both Azure-based deployments as well as on-premises Microsoft Hyper-V/VMware ESXi/KVM VMM (Virtual Machine Monitor) deployments. The licenses enable:

1. Base and trial feature set.
2. SIP signaling sessions with corresponding media stream capabilities:
   
   1. For both Azure and on-premises deployments, SIP sessions with RTP media stream support limited to RTP Direct Media & RTP proxy media without encryption services;
   2. For both Azure and on-premises deployments, SIP sessions with RTP media stream support limited to:
      1. RTP direct media;
      2. RTP proxy media with encryption services;
      3. RTP media manipulation services without transcoding.
   3. For both Azure and on-premises deployments, SIP sessions with complete RTP media stream support:
      1. RTP direct media;
      2. RTP proxy media with encryption services;
      3. RTP media manipulation Services with transcoding.
3. Transcoding "top-up" to pre-existing SIP sessions for both on-premises & Azure deployments.
4. 250 Session activation, both on-premises and in Azure.
5. Supplementary features for both on-premises and in Azure.

SBC SWe Lite License Format Overview

The SBC SWe Lite displays the License Format attribute [refer to Viewing Licenses (SBC SWe Lite)], alongside the list of features enabled through the application of a license file. License format clarifications:

• License Format refers to the mechanism that creates the license file; the SBC SWe Lite instance uses this mechanism to activate purchased features.
• License Format does not refer to any individual purchased features (i.e., SIP sessions, SIP registrations, call forking, etc.).
• On occasion, License Format may change to account for modifications made in SBC SWe Lite license file generation and interpretation.

As of Release 8.0.3, two license formats exist. See below.

On-premises vs. Microsoft Azure Targeted License Restrictions

SBC SWe Lite licenses for Azure-based deployments may not be assigned to an SBC SWe Lite deployed on-premises within the context of a Microsoft Hyper-V/VMware ESXi/KVM managed VM.  Similarly, SBC SWe Lite  licenses for on-premises based deployments may not be assigned to an SBC SWe Lite deployed within the context of a public cloud environment such as Microsoft Azure.  An attempt to apply licenses as described in the aforementioned manner will result in the SBC SWe Lite reporting  an error, along with the rejection of the licenses being accepted. Please contact Ribbon for more information if needed regarding the restriction.

Microsoft Azure-Based SBC SWe Lite Deployment Licenses

Base Software & Trial License

SIP Signaling & RTP Media Session Licenses

SIP Signaling & RTP Direct Media/RTP Proxy Sessions Without Encryption Services

All licenses that end with -SG-CLOUD enable the following features within a public cloud deployment:

• SIP signaling sessions

• Alongside each SIP signaling session, a corresponding RTP media channel that may be either of the following:
  • RTP direct media mode session
  • RTP proxy media mode session, without encryption services.

Note:

• No RTP media manipulation nor encryption services are available with -SG-CLOUD licenses;. 
• On-premises related -SG licenses will be rejected by an SBC SWe Lite deployed in Azure;
• Refer to Calculating Virtual Machine Requirements for an SBC SWe Lite Deployment for use cases with -SG-CLOUD licenses.

SIP Signaling with RTP Direct Media, RTP Proxy Sessions, and Partial RTP Media Manipulation Services

All licenses that end with -SGX-CLOUD enable the following features within a public cloud deployment:

• SIP signaling sessions

• Alongside each SIP signaling session, a corresponding RTP media channel that may be either of the following:
  • RTP direct media mode session
  • RTP proxy media mode session, with encryption services.
  • RTP media manipulation mode session, without transcoding or transrating.

Note:

• No transcoding services are available with -SGX-CLOUD licenses;
• On-premises related -SGX licenses will be rejected by an SBC SWe Lite deployed in Azure.
• Refer to Calculating Virtual Machine Requirements for an SBC SWe Lite Deployment for use cases with -SGX-CLOUD licenses.

SIP Signaling with Complete RTP Media Services

All licenses that end with -SP-CLOUD enable the following features within a public cloud deployment:

• SIP signaling sessions

• Alongside each SIP signaling session, a corresponding RTP media channel that may be either of the following:
  • RTP direct media mode session
  • RTP proxy media mode session, with encryption services.
  • RTP media manipulation mode session with transcoding and transrating.

Note:

• On-premises related -SP licenses will be rejected by an SBC SWe Lite deployed in Azure.
• Refer to Calculating Virtual Machine Requirements for an SBC SWe Lite Deployment for use cases with -SP-CLOUD licenses.

Transcoding "Top-Up" Licenses

All licenses that end with -ME-CLOUD add the following services to a pre-existing licensed SIP session, previously acquired through an -SG-CLOUD or -SGX-CLOUD license: 

• RTP proxy media mode session, with encryption services.
• RTP media manipulation mode session with transcoding and transrating.

Note:

• The -ME-CLOUD license adds no new features to SIP sessions previously acquired through an -SP-CLOUD license;
• On-premises related -ME licenses will be rejected by an SBC SWe Lite deployed in Azure.
• Refer to Calculating Virtual Machine Requirements for an SBC SWe Lite Deployment for use cases with transcoding.

250 Session Threshold License

Regardless of the number of licensed SIP signaling and RTP media sessions, the SBC SWe Lite requires an additional license to activate the capability to process 250 simultaneous sessions and beyond. See below for parameters:

• The 250 session threshold license does not activate any sessions i.e. this license does not replace any licenses in the aforementioned sections.
• If 250 or more SIP signaling & RTP media session licenses have been applied to the SBC SWe Lite instance while the 250 session threshold license remains absent, the SBC SWe Lite confines itself to completing no more than 249 simultaneous sessions.
• The 250 session threshold license may be acquired at any time, regardless of the presence of SIP signaling & RTP media session licenses (or not).

Contact Ribbon for more information.

Feature Licenses

On-Premises SBC SWe Lite Deployment Licenses

Base Software & Trial License

SIP Signaling & RTP Media Session Licenses

SIP Signaling & RTP Direct Media/RTP Proxy Sessions Without Encryption Services

All licenses that end with -SG enable the following features within an on-premises deployment:

• SIP signaling sessions

• Alongside each SIP signaling session, a corresponding RTP media channel that may be either of the following:
  • RTP direct media mode session
  • RTP proxy media mode session, without encryption services.

Note:

• No RTP media manipulation nor encryption services are available with -SG licenses;. 
• Azure-related -SG-CLOUD licenses will be rejected by an SBC SWe Lite deployed on-premises;
• Refer to Calculating Virtual Machine Requirements for an SBC SWe Lite Deployment for use cases with -SG licenses.

SIP Signaling with RTP Direct Media, RTP Proxy Sessions, and Partial RTP Media Manipulation Services

All licenses that end with -SGX enable the following features within an on-premises deployment:

• SIP signaling sessions

• Alongside each SIP signaling session, a corresponding RTP media channel that may be either of the following:
  • RTP direct media mode session
  • RTP proxy media mode session, with encryption services.
  • RTP media manipulation mode session, without transcoding or transrating.

Note:

• No transcoding services are available with -SGX licenses;
• Azure-related -SGX-CLOUD licenses will be rejected by an SBC SWe Lite deployed on-premises.
• Refer to Calculating Virtual Machine Requirements for an SBC SWe Lite Deployment for use cases with -SGX licenses.

SIP Signaling with Complete RTP Media Services

All licenses that end with -SP enable the following features within an on-premises deployment:

• SIP signaling sessions

• Alongside each SIP signaling session, a corresponding RTP media channel that may be either of the following:
  • RTP direct media mode session
  • RTP proxy media mode session, with encryption services.
  • RTP media manipulation mode session, with transcoding and transrating.

Note:

• Azure-related -SP-CLOUD licenses will be rejected by an SBC SWe Lite deployed on-premises.
• Refer to Calculating Virtual Machine Requirements for an SBC SWe Lite Deployment for use cases with -SP licenses.

Transcoding "Top-Up" Licenses

All licenses that end with -ME add the following services to a pre-existing licensed SIP session, previously acquired through an -SG or -SGX license: 

• RTP proxy media mode session, with encryption services.
• RTP media manipulation mode session, with transcoding and transrating.

Note:

• The -ME license adds no new features to SIP sessions previously acquired through an -SP license;
• Azure-related -ME-CLOUD licenses will be rejected by an SBC SWe Lite deployed on-premises.
• Refer to Calculating Virtual Machine Requirements for an SBC SWe Lite Deployment for use cases with transcoding.

250 Session Threshold License

Regardless of the number of licensed SIP signaling and RTP media sessions, the SBC SWe Lite requires an additional license to activate the capability to process 250 simultaneous sessions and beyond. See below for parameters:

• The 250 session threshold license does not activate any sessions i.e. this license does not replace any licenses in the aforementioned sections.
• If 250 or more SIP signaling & RTP media session licenses have been applied to the SBC SWe Lite instance while the 250 session threshold license remains absent, the SBC SWe Lite confines itself to completing no more than 249 simultaneous sessions.
• The 250 session threshold license may be acquired at any time, regardless of the presence of SIP signaling & RTP media session licenses (or not).

Contact Ribbon for more information.

Feature Licenses

Refer to Contacting Ribbon for more information about licensed features and hardware modules.

Related Topics

• Decoding License Keys
• Installing Licenses
• Viewing Licenses
• Attach License Label - Skype for Business and Windows OS
• SBC 1000/2000 Performance and Capacity (details on the use of SIP session licenses for SIP↔SIP call flows for SBC 1000 & SBC 2000 platforms)
• SBC SWe Lite Performance and Capacity (details on the use of SIP session licenses for SIP↔SIP call flows for the SBC SWe Lite)