Versions Compared

Key

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

Add_workflow_for_techpubs
AUTH2UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cd5909df, userName='null'}
AUTH1UserResourceIdentifier{userKey=8a00a0c862eadf5e0163170affe7001b8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
JIRAIDAUTHSBX-120567124354
REV5UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e98a00a0c87e188912017e4c24a00e0016, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e98a00a02355cd1c2f0155cd26cd5909df, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e98a00a02355cd1c2f0155cd26cc2c0791, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c90501da8a00a02355cd1c2f0155cd26cca00892, userName='null'}


Available_since
Release12.1.1



Include Page
_SBC 5100 5200 Unsupported
_SBC 5100 5200 Unsupported

The following table lists selected SBC Core key features, and their availability in this release by platform. Features in this table are not supported in all platforms/environments. 

Info
titleNote

 This is not a comprehensive list of features. For a more inclusive and detailed listing of features, refer to the Feature Guides.


(tick) = Supported
(error) = Not supported


Feature

Hardware-Based PlatformsSoftware-Based Platforms

Comments 

SBC 5400

SBC 7000

SBC SWe
(Virtual)

VMware/KVM

SBC SWe
(Cloud)
SBC CNe
Integrated

VMware/KVM

I-SBC in OpenStack

D-SBC in
OpenStack

AWSGCPAzure
RedHat OCP
Red Hat OCP
ERE Support(tick)(tick)(tick)(tick)(tick)(tick)(tick)(tick)

(error)2


EMA Support(tick)(tick)(tick)(tick)(tick)(tick)(tick)(tick)(error)
IP-Related Features
Alternate/Multiple IP Support(tick)(tick)(tick)(tick)(tick)

(tick)

(error)(error)(tick)
ARP Probing(error)(tick)(tick)(tick)(tick)(error)(error)(error)(tick)
DHCP Support(error)(error)(error)(tick)(tick)(tick)(tick)(tick)
N/A
NA
Direct I/O Support
N/A
NANA
N/A
(tick)
N/AN/AN/AN/A
NANANANANA
N/A
(error)
EVRC-B Codecs(tick)(tick)(tick)(tick)Pass-through(tick)(tick)(tick)(tick)
Geographical Redundancy (GRHA)(tick)(tick)(tick)(error)(error)(error)(error)(error)

(error)

Refer to SBC Core Redundancy details.

GW-GW support(tick)(tick)(tick)(tick)(tick)(tick)(tick)(tick)(error)3In SBC CNe, GW-GW is replaced with SIP-T protocol
H.323 Support(tick)(tick)(tick)(error)(error)(error)(error)(error)(error)

IMS Features

  • Rx Interface 
  • Rf Interface 
  • ATCF/EATF/SRVCC
  • AKA
(tick)(tick)(tick)(tick)(tick)(tick)(tick)(tick)(tick)
(tick)(tick)(tick)(tick)(tick)(tick)(tick)(tick)(error)
(tick)(tick)(tick)(tick)(tick)(tick)(tick)(tick)(error)
(tick)(tick)(tick)(tick)(tick)(tick)(tick)(tick)(tick)
IPsec(tick)(tick)(tick)(tick)(tick)(error)(error)(error)(error)IPsec is supported for Signaling but not supported for media
IPv6 Support(tick)(tick)(tick)(tick)(tick)(tick)
(error)
(tick)1(error)(tick)
Lawful Intercept (LI)(tick)(tick)(tick)(tick)(tick)(tick)(tick)(tick)(tick)

Link Detection:


Refer to SBC Core Redundancy for details.
N:1 Redundancy(error)(error)

(tick)

I-SBC: 4+1

(error)

(tick)

(tick)

S-SBC: 4+1
M-SBC: 4+1

(error)(error)(error)

(tick)

SC pod: N+K

(N max is 47, K max is 3)

Refer to Distributed SBC Architecture for details.
NIC Teaming(error)(error)(tick)

Note: Not in KVM
(error)(error)(error)(error)(error)(error)
Physical link detection(tick)(tick)(tick)(error)(error)(error)(error)(error)(error)NOTE: Physical link detection is supported only on Direct I/O Packet Interfaces on the SBC SWe.
Registration Display Enhancement(tick)(tick)

(tick)


(tick)

(

1:1 deployments

)

(tick)

S-SBC

only
(

1:1 deployments

)

only

(tick)

(tick)

(tick)

(error)Refer to SIP Registration
SIP over SCTP(tick)(tick)(tick)(error)(error)(error)(error)(error)(error)
SIP Registrar(tick)(tick)(tick)(tick)(error)(error)(error)(error)(error)NOTE: An SBC Core acting as a SIP Registrar is only available on the SBC HW and the SBC SWe I-SBC deployments, and not on the D-SBC and SBC CNe deployments. For more information, refer to SIP Registrar Functionality.
Can act as SLB(error)(error)

(tick)

(tick)(tick)(tick)(tick)(tick)(tick)
SR-IOVN/A

Can sit behind SLB(tick)(tick)
N/A

(tick)

(tick)(tick)(tick)
(error)
(tick)
(error)
(tick)(tick)
SRTP

SR-IOV
(tick)
NA
(tick)
NA(tick)(tick)
(error)
(tick)(tick)
(tick)
(error)(error)
GW-GW support(tick)
(tick)
(tick)(tick)

SRTP(tick)(tick)(tick)(tick)(error)
3In SBC CNe, GW-GW is replaced with SIP-T protocolERE support
(tick)(tick)(tick)(tick)
(tick)

Standby Packet Port Support(error)
(tick)
(tick)
(tick)
(error)(error)
2
Lawful Intercept
(
LI
See note 1)
(tick)
(error)
(tick)
(error)
(tick)
(error)(tick)
(tick)

Media-Related Features
Direct Media Anti Trombone
(tick)
(tick)(tick)
(error)

IMS features

  • Rx/Rf interface functionality
  • ATCF/EATF/SRVCC
  • AKA
(tick)(tick)
(tick)
(error)(tick)(tick)(tick)(tick)
(tick)(error)Media-Related FeaturesFax transcoded calls
Refer to SIP Trunk Group - Media.
Fax Transcoded Calls(tick)(tick)(tick)(tick)(error)(error)(error)(error)(tick)Refer to Fax Over IP.
  • G.711–T.38 (V0)
(tick)(tick)(tick)(tick)(error)(error)(error)(error)(tick)
  • G.711–T.38 (V3)
(tick)(tick)(error)(error)(error)(error)(error)(error)(error)
  • T.38 (V0)–T.38 (V0)
(tick)(tick)(tick)(tick)(error)(error)(error)(error)(tick)
Fax/Modem Fallback(tick)(tick)(tick)(error)(error)(error)(error)(error)(tick)
GPU Transcoding(error)(error)

(tick)

 

(tick)(tick)(tick)(tick)(error)(error)
Opus Transcoding

JITC/FIPS/DoD(tick)(tick)(tick)(tick)(tick)(tick)(tick)
(error)
(tick)
UC (Video, BFCP, Content Share)(tick)(tick)(tick)(tick)(error)
(error)
(error)(error)(error)

MSRP/TCP relay/Application Media(tick)(tick)(tick)(tick)(tick) 
(MSRP / Application Media)



(error)

Opus Transcoding(tick)(tick)(tick)(tick)
JITC/FIPS/DoD
(tick)(tick)(tick)(error)(tick)
UC (Video, BFCP, Content Share)(tick)(tick)(tick)(tick)(error)(error)(error)(error)(error)


Anchor
Notes
Notes


1The SBC Core SWe/Cloud on AWS and GCP does not support IPv6. However, AWS infrastructure supports IPv6, but GCP infrastructure does not.

2ERE functionality is not supported as part of the SBC CNe. For the SBC CNe, the PSX CNe is mandatory. Ribbon recommends that customers who have typically used ERE for routing to work with Ribbon Professional Services to migrate their configuration to the PSX CNe.

3GW-GW (Ribbon proprietary protocol for communication between the SBC-GSX and SBC-SBC) functionality is not supported as part of the SBC CNe. Instead of GW-GW protocol, SIP-T protocol is recommended for the SBC CNe.