Feature Availability by Platform

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. 

= Supported
= Not supported

Feature	Hardware-Based Platforms		Software-Based Platforms							Comments
	SBC 5400	SBC 7000	SBC SWe (Virtual) VMware/KVM	SBC SWe (Cloud)					SBC CNe
				Integrated SBC in OpenStack	D-SBC OpenStack	AWS	GCP	Azure	RedHat OCP
IP-Related Features
Alternate/Multiple IP Support
ARP Probing
DHCP Support									N/A
Direct I/O Support	N/A	N/A		N/A	N/A	N/A	N/A	N/A
EVRC-B Codecs					Pass-through
Geographical Redundancy (GRHA)										Refer to SBC Core Redundancy details.
H.323 Support
IPsec
IPv6 Support							1
Link Detection:										Refer to SBC Core Redundancy for details.
N:1 Redundancy			I-SBC: 4+1		S-SBC: 4+1 M-SBC: 4+1				SC pod: N+K (N max is 47, K max is 3)	Refer to Distributed SBC Architecture for details.
NIC Teaming			Note: Not in KVM
Physical link detection										NOTE: Physical link detection is supported only on Direct I/O Packet Interfaces on the SBC SWe.
Registration Display Enhancement				(1:1 deployments)	S-SBC only (1:1 deployments)					Refer to SIP Registration
SIP over SCTP
SIP Registrar										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.
SLB
SR-IOV	N/A	N/A
SRTP
GW-GW support									3	In SBC CNe, GW-GW is replaced with SIP-T protocol
ERE support									2
Lawful Intercept (LI)
IMS features Rx/Rf interface functionality ATCF/EATF/SRVCC AKA
Media-Related Features
Fax transcoded calls										Refer to Fax Over IP
G.711–T.38 (V0)
G.711–T.38 (V3)
T.38 (V0)–T.38 (V0)
Fax/Modem Fallback
GPU Transcoding
Opus Transcoding
UC (Video, BFCP, Content Share)
MSRP/TCP relay/Application Media					(MSRP/Application Media)
JITC/FIPS/DoD

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

²ERE 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.

³GW-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.