This section describes the licensing process on the 

Spacevars
0 product

and

Spacevars
0 product3

systems. 

The 

Spacevars
0 product

 is delivered with standard functions. For additional 

Spacevars
0 product

 features and supplementary services (which are not available as standard functions of the 

Spacevars
0 product

), you must obtain software licenses purchased from

Spacevars
0 company

. 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 

Spacevars
0 product

 (Refer to Installing Licenses). This process also applies to license upgrades/expansions.

SBC 1000, SBC 2000 Licenses

Note
An SBC 1000 Module or SBC 2000 line card requires a license to enable ports for use on the node.

General Licenses

Info

No special licensing considerations for Teams Direct Routing on the SBC 1000 & SBC 2000 There are no feature limitations that must be accounted for via licensing for Teams Direct Routing. For example: Teams Phone System ↔ FXS/FXO/PRI calls are supported with no additional licensing over and above FXS/FXO/PRI port licensing (if required). Teams Phone System ↔ SIP client (SIP trunks, SIP phones, SIP-based IP PBX, etc.) calls are supported with no additional licensing over and above SIP session licensing.

Feature licenses enable features or supplementary services not available as standard functions on the physical 

Spacevars
0 product

, 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.

Caption
0 Figure 1 Feature Licenses
Type License ID Description SBC 1000 SBC-1K-LIC100REG 100 licenses supporting Registrar feature SBC-1K-LIC10SIP 10 sessions supporting SIP↔SIP functionality SBC-1K-LIC25SIP 25 SIP↔SIP sessions SBC-1K-LIC5SIP 5 SIP↔SIP sessions SBC-1K-LIC-BRI 4 BRI ports on the SBC 1000 SBC-1K-LIC-BSURV Local Survivability with Broadworks on the SBC 1000 SBC-1K-LIC-CCPE Applies Custom Configuration on the SBC 1000 SBC-1K-LIC-FORK SBC Call Forking, up to 8 destinations SBC-1K-LIC-FXS 4 FXS ports on the SBC 1000 SBC-1K-LIC-RBA Resilient Branch Appliance (RBA) function for Microsoft Lync at Branch Office SBC-1K-LIC-ROUTG OSPF IP Routing Protocol on SBC 1000 SBC-1K-LIC-FXO 4 FXO ports on the SBC 1000 SBC-1K-LIC-T1E1 1 T1/E1 port on the SBC 1000 SBC-1K-LIC-VIDEO Video support on the SBC 1000 SBC-1K-LIC-WBGSM AMR-WB use on the SBC 1000 SBC 2000 SBC-2K-LIC100REG 100 licenses for Registrar functionality SBC-2K-LIC100SIP 100 SIP↔SIP sessions, plus transcoding SBC-2K-LIC10SIP 10 SIP↔SIP sessions, plus transcoding SBC-2K-LIC25SIP 25 sessions of SIP to SIP and enables transcoding SBC-2K-LIC5SIP 5 sessions of SIP to SIP and enables transcoding SBC-2K-LIC-BSURV Local Survivability with Broadworks on the SBC 2000 SBC-2K-LIC-CCPE Custom Configuration ability on the SBC 2000 SBC-2K-LIC-FORK SBC Call Forking, up to 8 destinations SBC-2K-LIC-RBA Resilient Branch Appliance (RBA) function for Microsoft Lync at Branch Office SBC-2K-LIC-ROUTG OSPF IP Routing Protocol on SBC 2000 SBC-2K-LIC-T1E1 1 T1E1 port on the SBC 2000 SBC-2K-LIC-VIDEO Video support on the SBC 2000 SBC-2K-LIC-WBGSM AMR-WB use on the SBC 2000 SBC 1000/2000 SBC-1K2K-LYNC10-LIC Microsoft Lync 2010 SBA (Survivable Branch Appliance) License. Applicable to both SBC 1000 and SBC 2000 devices with ASM Module Execution of the Lync 2010 SBA requires a Windows Server 2008 R2 OS license. Confirm the availability of the OS license; if the OS license is not available, please also acquire a SBC-1K2K-WIN08-LIC license. Refer to Skype for Business - Best Practice Downgrade to Lync 2010 SBA. The SBC-1K2K-LYNC10-LIC part is a physical license (document and/or license label) only. No license key is generated. SBC-1K2K-LYNC13-LIC Microsoft Lync 2013 SBA (Survivable Branch Appliance) License. Applicable to both SBC 1000 and SBC 2000 devices with ASM Module. Execution of the Lync 2013 SBA requires either a Windows Server 2008 R2 OS license or a Windows Server 2012 R2 OS license. An SBC 1000/2000 device with an ASM always includes a licensed copy of one of these two operating systems, no OS availability check is required. The SBC-1K2K-LYNC13-LIC part is a physical license (document and/or license label) only. No license key is generated. SBC-1K2K-SKYPE-LIC Microsoft Skype for Business 2015 SBA (Survivable Branch Appliance) License. Applicable to both SBC 1000 and SBC 2000 Devices with ASM Module. Execution of Microsoft Skype for Business SBA requires a Windows Server 2012 R2 OS license. Confirm the availability of the OS license; if the OS license is not available, please also acquire a SBC-1K2K-WIN12-LIC license. Refer to Skype for Business - Best Practice Upgrade to Skype for Business 2015 SBA. The SBC-1K2K-SKYPE-LIC part is a physical license (document and/or license label) only. No license key is generated. SBC-1K2K-WIN08-LIC Microsoft Windows Server 2008 R2 License. Applicable to both SBC 1000 and SBC 2000 Devices with ASM Module. If acquiring the SBC-1K2K-WIN08-LIC to support the execution of the Lync 2010 SBA, please also order a SBC-1K2K-LYNC10-LIC. Refer to Skype for Business - Best Practice Downgrade to Lync 2010 SBA. If acquiring the SBC-1K2K-WIN08-LIC to support the execution of the Lync 2013 SBA, please also order a SBC-1K2K-LYNC13-LIC. Refer to Best Practice Downgrade to Lync 2013 SBA for Windows Server 2008R2. The SBC-1K2K-WIN08-LIC part provides both a physical license (document and/or license label) along with an electronic license key. The license key must be installed on the SBC 1000/2000 to enable the Windows Server 2008 R2 OS. For more information, refer to Installing Licenses. SBC-1K2K-WIN12-LIC Microsoft Windows Server 2012 License. Applicable to both SBC 1000 and SBC 2000 Devices with ASM Module. If acquiring the SBC-1K2K-WIN12-LIC to support the execution of the Microsoft Skype for Business 2015 SBA, also order a SBC-1K2K-SKYPE-LIC. Refer to Skype for Business - Best Practice Upgrade to Skype for Business 2015 SBA. If acquiring the SBC-1K2K-WIN12-LIC to sUPport the execution of the Lync 2013 SBA, also order a SBC-1K2K-LYNC13-LIC. Refer to Skype for Business - Best Practice Upgrade to Lync 2013 SBA on Windows Server 2012 R2. The SBC-1K2K-WIN12-LIC part provides both a physical license (document and/or license label) along with an electronic license key. The license key must be installed on the SBC 1000/2000 to enable the Windows Server 2012 R2 OS. For more information, refer to Installing Licenses.

SBC 1000 Gateway License Concepts

Spacevars
0 company

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,

Spacevars
0 company

provides you with the flexibility to select the most cost-effective session border controller solution for your network.

 

Note
SBC 1000 Gateways do not include the additional 2 GiB of Local storage (interior) included with the SBC Edge 7.0 release.

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:

Caption
0 Table 1 Premium Features Deactivated Within SBC 1000 Gateways 3 Premium Feature Set Licenses
Premium Feature Complementary Feature/Supplementary Service License Ignored by the SBC 1000 Gateway SIP Calls SBC-1K-LIC10SIP, SBC-1K-LIC25SIP, or SBC-1K-LIC5SIP SIP Registrations SBC-1K-LIC100REG Forking SBC-1K-LIC-FORK SBA N/A Active Directory N/A transcoding N/A OSPF SBC-1K-LIC-ROUTG RIP SBC-1K-LIC-ROUTG IPsec SBC-1K-LIC-RBA RBA SBC-1K-LIC-RBA QoE N/A BroadSoft Subscriber SBC-1K-LIC-BSURV AMR-WB SBC-1K-LIC-WBGSM Video Passthrough  SBC-1K-LIC-VIDEO SIP VQ Reporting SBC-1K2K-NECTAR-PROMO or SBC-1K2K-NECTAR-LIC

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

Spacevars
0 company

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:

Spacevars
0 product3

 Licenses

Overview

Ribbon Communications offers customers deploying the 

Spacevars
0 product3

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.

Available_since
Type Available Since Release 8.0.3

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

Caption
0 Table 1 License Types - Availability 3 license_types
License Source Type Also Identified As Availablility SBC SWe Lite License Format Version 2 v2

Available since Release

Supported in only Releases 6.1

.Supported in Releases prior

to 8.

1.

0.

Planned to be obsolete May 2020

3. SBC SWe Lite License Format Version 3 v3 Introduced with Release 8.0.3. Supported in Release 8.0.3 and later, unless noted elsewhere.

Anchor
warning_license_format warning_license_format

Warning
title ACTION REQUIRED - UPGRADE TO RELEASE 8.0.3 IMMEDIATELY TO ADDRESS LICENSE FILE FORMAT CHANGE
Ribbon strongly recommends the following actions by no later than May 2020 to avoid any service disruption: Upgrade the SBC SWe Lite to the Release 8.0.3 (if not already on Release 8.0.3). If the SBC SWe Lite displays License Format Version 2, contact Ribbon Support for a courtesy (free of charge) feature equivalent to SBC SWe Lite License Format Version 3. Update the SBC SWe Lite with the newly received license file (formatted to Version 3), and confirm all features previously available prior to the license update are present. After June 1, 2020, SBC SWe Lite License Format Version 2 will no longer be recognized by any Ribbon supported SBC SWe Lite image. For further license guidance, contact Ribbon Support.

 

WARNING - IF YOUR LICENSE FORMAT IS NOT VERSION 3 (OR YOU DO NOT KNOW) PERFORM THE FOLLOWING STEPS BEFORE JUNE 15, 2020 TO PREVENT A SERVICE DISRUPTION
The License Format Version 2 is obsolete as of the SBC SWe Lite Release 8.0.4 and later (see the License Types - Availability table). SBC SWe Lite instances with License Format Version 2 may experience service disruption after June 15, 2020. To prevent a service disruption, use the following procedure to update the License Format Version 2 to License Format Version 3. Log into your SBC SWe Lite to locate and record the Software Version (refer to Viewing the Software Version and Hardware ID). Perform the rest of this procedure based on your Software Version: If your Software Version is 8.0.3, locate and record the License Version. If your License Version is Version 3, upgrade the SBC SWe Lite to Release 8.0.4 and skip the rest of this procedure; or Version 2, proceed to the next step. If your Software Version is 8.0.2 or earlier, your License Format Version is 2. Upgrade the SBC SWe Lite to Release 8.0.3 and then proceed to the next step. Anchor contact_support contact_support Contact Ribbon Support for a courtesy (free of charge) feature equivalent to the SBC SWe Lite License Format Version 3. Update the SBC SWe Lite with the newly received license file (formatted to Version 3), and confirm all features previously available prior to the license update are present. Upgrade the SBC SWe Lite to Release 8.0.4. After June 15, 2020, the SBC SWe Lite License Format Version 2 will no longer be recognized by any Ribbon supported SBC SWe Lite image. For further license guidance, contact Ribbon Support.
Warning
title IMPORTANT
Note the presence of the License Version Attribute in the SBC SWe Lite Release 8.0.3 System Overview Display. For an 8.0.3-enabled SBC SWe Lite, take the following action: If the License Version is Version 2: Update the license by no later than May 2020 to prevent a service disruption. To update the license, refer to Obtaining and Installing an SBC SWe Lite Production License. If the License Version is Version 3: No action necessary.

On-premises vs. Microsoft Azure Targeted License Restrictions

Spacevars
0 product3

 licenses for Azure-based deployments may not be assigned to an

Spacevars
0 product3

 deployed on-premises within the context of a Microsoft Hyper-V/VMware ESXi/KVM managed VM.  Similarly, 

Spacevars
0 product3

  licenses for on-premises based deployments may not be assigned to an 

Spacevars
0 product3

 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 

Spacevars
0 product3

reporting  an error, along with the rejection of the licenses being accepted. Please contact Ribbon for more information if needed regarding the restriction.

Anchor
Cloud Licenses Cloud Licenses

Microsoft Azure-Based 

Spacevars
0 product3

Deployment Licenses

Base Software & Trial License

SIP Signaling & RTP Media Session Licenses

Anchor
SG license cloud SG license cloud

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

Warning
Do Not Acquire and Apply *-SG-Cloud Licenses for Teams Direct Routing  Microsoft Teams Direct Routing requires enhanced media services of the SBC SWe Lite’s virtual DSP feature, available with either the *-SGX-CLOUD/*-SP-CLOUD licenses. The *-SG-CLOUD licenses will result in limited/erroneous Teams Direct Routing call 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 

  Spacevars
  0 product3

   deployed in Azure;
• Refer to Calculating Virtual Machine Requirements for an SBC SWe Lite Deployment for use cases with -SG-CLOUD licenses.

Anchor
SGX license cloud SGX license cloud

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

Tip
Applicable for Teams Direct Routing; the *-SGX-CLOUD licenses do not support transcoding.

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 

  Spacevars
  0 product3

   deployed in Azure.
• Refer to Calculating Virtual Machine Requirements for an SBC SWe Lite Deployment for use cases with -SGX-CLOUD licenses.

Anchor
SP license cloud SP license cloud

SIP Signaling with Complete RTP Media Services

Tip
Applicable for Teams Direct Routing, with transcoding available.

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 

  Spacevars
  0 product3

   deployed in Azure.
• Refer to Calculating Virtual Machine Requirements for an SBC SWe Lite Deployment for use cases with -SP-CLOUD licenses.

Anchor
ME license cloud ME license cloud

Transcoding "Top-Up" Licenses

Tip
Applicable for Teams Direct Routing, with transcoding available.

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 

  Spacevars
  0 product3

   deployed in Azure.
• Refer to Calculating Virtual Machine Requirements for an SBC SWe Lite Deployment for use cases with transcoding.

Anchor
250 license cloud 250 license cloud

250 Session Threshold License

Regardless of the number of licensed SIP signaling and RTP media sessions, the 

Spacevars
0 product3

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 

  Spacevars
  0 product3

  instance while the 250 session threshold license remains absent, the 

  Spacevars
  0 product3

  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.

Anchor
feature license cloud feature license cloud

Feature Licenses

Anchor
On-premises Licenses On-premises Licenses

On-Premises 

Spacevars
0 product3

 Deployment Licenses

Base Software & Trial License

SIP Signaling & RTP Media Session Licenses

Anchor
SG license SG license

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

Warning
Do Not Acquire and Apply *-SG Licenses for Teams Direct Routing  Microsoft Teams Direct Routing requires enhanced media services of the SBC SWe Lite’s virtual DSP feature, available with either the *-SGX/*-SP licenses. The *-SG licenses will result in limited/erroneous Teams Direct Routing call 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 

  Spacevars
  0 product3

   deployed on-premises;
• Refer to Calculating Virtual Machine Requirements for an SBC SWe Lite Deployment for use cases with -SG licenses.

Anchor
SGX license SGX license

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

Tip
Applicable for Teams Direct Routing; the *-SGX licenses do not support transcoding.

 

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 

  Spacevars
  0 product3

   deployed on-premises.
• Refer to Calculating Virtual Machine Requirements for an SBC SWe Lite Deployment for use cases with -SGX licenses.

Anchor
SP license SP license

SIP Signaling with Complete RTP Media Services

Tip
Applicable for Teams Direct Routing, with transcoding available.

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 

  Spacevars
  0 product3

   deployed on-premises.
• Refer to Calculating Virtual Machine Requirements for an SBC SWe Lite Deployment for use cases with -SP licenses.

Anchor
ME license ME license

Transcoding "Top-Up" Licenses

Tip
Applicable for Teams Direct Routing, with transcoding available.

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 

  Spacevars
  0 product3

   deployed on-premises.
• Refer to Calculating Virtual Machine Requirements for an SBC SWe Lite Deployment for use cases with transcoding.

Anchor
250 license 250 license

250 Session Threshold License

Regardless of the number of licensed SIP signaling and RTP media sessions, the 

Spacevars
0 product3

 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 

  Spacevars
  0 product3

   instance while the 250 session threshold license remains absent, the 

  Spacevars
  0 product3

   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.

Anchor
feature license feature license

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)

Pagebreak