IMPORTANT

The SBC 5100, SBC 5110, SBC 5200, and SBC 5210 platforms are no longer supported beginning with the SBC Core 10.0.0R0 release. This release supports SBC 5400/7000/SWe/Cloud Native edition (CNe) platforms. Contact Ribbon Sales for upgrade information.

The following table lists the SBC feature license keys that apply in the Domain Locked (DL) environment. DL license keys contain a "-D" suffix to distinguish them from similar license keys used in Node-Locked licensing.

About Counts
  • Count means the feature license key has an associated integer value that denotes the number of concurrent calls/transactions per second/concurrent active SIP registrations that may receive the service denoted by the feature license key.
  • On/Off means the feature license key activates an SBC-wide service. 


Feature IDUsageType

DSP-AMRNB-D

RTU media interworking using AMRNB. Use license to enable AMR-NB audio transcoding. 

Count

DSP-AMRWB-D

RTU media interworking using G.722.2/AMR-WB. Use this license to enable AMR-WB audio transcoding. Count

DSP-EVRC-D

RTU media interworking using EVRC. Use this license to enable all variants of EVRC audio transcoding. 

Note: This license is not applicable to SBC SWe because EVRC is not supported.

Count

DSP-EVS-D

RTU media interworking using EVS. Use this license to enable all variants of EVS transcoding. Count
DSP-L16-DEnables LINEAR16 (Linear PCM) codec processing on any RTP media session receiving  Virtual DSP services (latter activated with the VDSP-RTU-D).Count
DSP-OPUS-DAdds OPUS codec processing on any RTP media session receiving  Virtual DSP services (latter activated with the VDSP-RTU-D).Count

DSP-SILK-D

RTU media interworking using SILK. Use license to enable SILK transcoding.Count
ENCRYPT-DEncryption function for signaling using TLS, IPsec.Count
LB-INSTANCE-DActivates an SBC SWe SLB (SIP-Aware Front-End Load Balancer) instance within the domain for operation. SIP sessions carried across the SLB are licensed separately (SBC-LB-D).On/Off

SBC-1X10GMP-D

SBC 5400 RTU license to enable media port(s) operating at 10 Gbps. This will activate two 10 Gbps packet ports.On/Off

SBC-4X1GMP-D

SBC 5400 RTU license to enable all four media ports. each operating at 1 Gbps.

Note: If the SBC 5400 is configured for two 1 Gbps media ports (default configuration), no license is required).

On/Off
SBC-CNE-INSTANCE-D

This license differentiates the CNF deployments from those handled by the same RAMP. Without this license, total calls up to 47 concurrent calls are supported on a CNe deployment. The maximum active SC pods can be 47, one call per SC pod is supported. 

The OAM is the only pod which will connect to the license manager. In case of completion of 90 days grace period, OAM communicates the information to SC pod to stop processing the calls.

Modified: for 12.1.1

On/Off
SBC-ETSI-LI-D

Enables ETSI/3gpp-related Lawful Intercept services.

Refer to Lawful Intercept for more information on the supported specifications and extent of support.

On/Off
SBC-FIPS-INST-D

Enables SBC device-wide FIPS-140 supporting operation.

Notes:

  • SIP session specific FIPS-140 operation requires the session to have licensed signaling & media encryption (ENCRYPT-D & SRTP-D, respectively) and FIPS-140 operations (SBC-FIPS-RTU-D).
  • All sessions on any SBC device configured for FIPS-140 operation must all be licensed for SIP session specific FIPS-140 operation, as described above.
On/Off
SBC-FIPS-RTU-D

Enables SIP session-specific FIPS-140 supporting operation.

Notes:

  • SIP session specific FIPS-140 operation requires the session to have licensed signaling & media encryption (ENCRYPT-D & SRTP-D, respectively).
  • SIP session specific FIPS-140 operation also requires the SBC to have licensed device-wide FIPS-140 operation (SBC-FIPS-INST-D).
  • All sessions on any SBC device configured for FIPS-140 operation must all be licensed for SIP session specific FIPS-140 operation, as described above.
Count
SBC-LB-DActivates support for a SIP session on an SBC SWe SLB (SIP-Aware Front-End Load Balancer) instance. The SLB instance is licensed separately (LB-INSTANCE-D).Count

SBC-LI-D

Enables PacketCable-related Lawful Intercept services.

Refer to Lawful Intercept for more information on the supported specifications and extent of support.

On/Off

SBC-MRF-RTU-D

This license is required to enable transcoding using an external Media Resource Function (MRF) device.

The SBC-MRF-RTU-D license is not a substitute for the SBC-RTU-D session license. Both licenses are required to allow a session towards the MRF. The SBC-MRF-RTU-D license is only applicable to the S-SBC when deploying the distributed-SBC architecture.

Count

SBC-POL-E911-D

RTU license for E911 service.On/Off

SBC-POL-ENUM-D

SBC ERE support for accessing ENUM databases.On/Off

SBC-POL-RTU-D

Enables on-board Advanced ERE (Embedded Routing Engine) services query support for a given SIP session (The latter is activated with the SBC-RTU-D license).

Notes:

  • Ribbon recommends off-board PSX policy and routing services as opposed to the limited services available with the Advanced ERE (Refer to Routing Engines Comparison for more information).
  • If Advanced ERE services are required, the count of SBC-POL-RTU-D must match the count of licensed concurrent SIP sessions (via the SBC-RTU-D) for proper operation.
Count
SBC-PSX-RTU-D

Enables off-board PSX policy and routing services query support for a given SIP session (latter activated with the SBC-RTU-D).

Notes:

  • Ribbon recommends off-board PSX PSX policy and routing services as opposed to the limited services available with the Advanced ERE (refer to Routing Engines Comparison for more information).
  • If PSX services are required, the count of SBC-PSX-RTU-D must match the count of licensed concurrent SIP sessions (via the SBC-RTU-D) for proper operation.
Count
SBC-RCS-D

Enables OOD (Out of Dialog) SIP session-related RCS (Rich Communications Services) support.

Notes:

  • License key is associated with a value that identifies an OOD RCS transaction rate on a per second basis;
  • Refer to Rich Communication Suite Support for more information.
Count

SBC-RTU-D

Controls the right-to-use (RTU) for SIP sessions. The following types of media sessions are enabled:

  • Pass-through audio (no DSPs)
  • Pass-through audio and video (no conferencing)
  • Transcoded audio
Count

SBC-SIP-I-D

SIP-I interworking function.Count

SBC-SIP323-D

SIP/H.323 Interworking function.On/Off

SBC-SIPREC-D

SIPREC session recording support.Count
SBC-STSH-D

Adds STIR SHAKEN-related processing on an SIP session (latter activated with the SBC-RTU-D).

Refer to STIR-SHAKEN Support for more information.

Count
SBC-SURV-D

Adds Local Survivability support on an SIP session (latter activated with the SBC-RTU-D).

Refer to SIP Trunk Group - Local Survivability for more information.

Count
SBC-TOIP-DEnables T.140/Text over IP processing on any RTP media session receiving  Virtual DSP services (latter activated with the VDSP-RTU-D).On/Off

SBC-VIDEO-D

Video interworking support, including Content Sharing (BFCP), Far-End Camera Control (FECC) and H.239 for H.323Count
SIP-REG-D

DL Feature license for SIP Registrar functionality (Domain E-LIC FOR SIP-REG ON SBC Core). For DL licenses, the maximum license count is equal to the maximum registrations supported by the SBC.

The Interval statistics logic reports the peak stable registrations during an interval and stores it in the pms file. The SBC uses this logic for DL License calculations, as described below.

  • The real-time stable registrations count at the start of the interval is collected.
  • If at any time during the interval the stable registrations increase, that value becomes the new peak.   
  • The peak stable registrations are reported for every interval and stored in the pms file.
  • This count (e.g., the REG_STABLE_COUNT reported in the pms file) is used for the DL License calculation.
Count

SRTP-D

Encryption function for media using Secure Real-time Transport Protocol (SRTP).Count

SWE-INSTANCE-D

Activates an SBC SWe instance within the domain for operation.On/Off

VDSP-RTU-D

Enables RTP media processing services in the SBC Core software based products (SBC SWe, SBC CNe).

The SBC delivers RTP media processing services through the application of the Virtual DSP (Digital Signal Processing) feature to a media session. Examples of such services include (partial list):

Transcoding

  1. Example transcoding scenarios are G.711 (common codec in enterprises) ↔ G.729ab (common codec in public networks) translation, G.711 A-law ↔ G.711 µ-law normalization, etc.
  2. The VDSP-RTU-D includes select codec transcoding support without additional codec specific licensing.
    1. The included codecs are G.711, G.729, T.38, G.723, G.722 variants other than G.722.2, & iLBC.     
    2. All other codecs require a supplementary license for transcode support. Examples of such codecs (partial list) are all variants of SILK, OPUS, Linear-16, EVS, EVRC, AMR-NB/AMR-WB, T.140/Text over IP, etc.
  3. Refer to Supported Codecs and Transcoding for the list of codecs supported by the SBC;

Transrating

Transrating includes call legs that carry a different time sample size of media, where the SBC performs the translation. Transrating is used often when enterprises or the service provider is looking to save bandwidth by reducing packet count at the expense of voice quality (should a packet be dropped).

Silence Suppression

The SBC removes RTP packets carrying no meaningful media to save packet traffic.

Fax Call Support

  1. Fax tone detection and interworking to T.38
  2. G.711 fax media pass-through, as DSP intervention reduces the likelihood of in-band fax signaling/media issues

In-band ↔ Out-of-band Interworking

Required for the following:

  1. In-band DTMF tone detection interworking with out-of-band RFC 4733 (supersedes RFC 2833)
  2. In-band DTMF tone detection interworking with SIP INFO messages
  3. Interworking RTP dynamic payload types, required when the subtended SBC peers use differing payload type identifiers from the dynamic RTP payload range (for example 96 - 127) to identify a common payload format (in other words,  codec)

Media That Originates From the SBC in Support of Call Developments

For example:

  1. Announcement playback;
  2. Local ringback tone;
  3. Music on Hold;
  4. Comfort noise.

Jitter Compensation

Used to maximize user experience with voice quality.


Notes: 

  • If the VDSP-RTU-D value is non-zero, the value specifies the number of concurrent calls on the system that may receive DSP-based RTP media services. If zero, no calls receive such services.
  • The VDSP-RTU-D count should be always less than or equal to SBC-RTU-D count. If not, no transcoded calls are allowed.
  • Any additional emergency oversubscription is not supported for transcoded emergency calls.
Count
WEBSOCKET-D

Enables WebRTC-related processing on an SIP session (latter activated with the SBC-RTU-D).

Notes:

  • Transcoding, encryption, and other features subject to licensing must be acquired to tailor WebRTC-related session services to use case.
  • Refer to SBC for WRTC for more information.
Count