In this section:
The following table lists selected SBC Core key features, and their availability in this release by product. Features in this table are not supported in all platforms/environments.
This is not a comprehensive list of features. For a more inclusive and detailed listing of features, refer to the Feature Guides.
= Supported
= Not supported
Feature Availability
Hardware-Based Platforms | Software-Based Platforms | Comments | |||||||
SBC 51x0 / 52x0 / 5400 | SBC 7000 | SBC SWe VMware/KVM | SBC SWe (Cloud) | ||||||
Integrated SBC in OpenStack | D-SBC | AWS | GCP | Azure | |||||
IP-Related Features | |||||||||
Link Detection: | Refer to SBC Core Redundancy for details. | ||||||||
Physical link detection | NOTE: Physical link detection is supported only on Direct I/O Packet Interfaces on the SBC SWe. | ||||||||
ARP Probing | |||||||||
Standby packet port support | (See note 2 below) | Refer to SBC Core Redundancy for details. | |||||||
Geographical Redundancy (GRHA) | Refer to SBC Core Redundancy details. | ||||||||
N:1 Redundancy | S-SBC: 4+1 M-SBC: 4+1 | Refer to Distributed SBC N:1 Redundancy Architecture for details. | |||||||
EVRC-B Codecs | Pass-through | ||||||||
H.323 Support | gap for cloud | ||||||||
SR-IOV | N/A | N/A | |||||||
Direct I/O Support | N/A | N/A | N/A | N/A | N/A | N/A | N/A | ||
DHCP Support | |||||||||
NIC Teaming | Note: Not in KVM | ||||||||
SIP over SCTP | |||||||||
SRTP | |||||||||
Alternate/Multiple IP Support | |||||||||
IPv6 Support | |||||||||
SLB | |||||||||
Media-Related Features | |||||||||
Fax transcoded calls | Refer to Fax Over IP | ||||||||
| |||||||||
| |||||||||
| |||||||||
Fax/Modem Fallback | |||||||||
UC (Video, BFCP, Content Share) | |||||||||
GPU Transcoding |
| ||||||||
Opus Transcoding | Not available for 5100/5200 |
1Full support for VMware available starting with SBC 8.1.
2Supported for four packet port configuration only. Not supported for any other packet port configuration.
3The SBC Core SWe/Cloud on AWS and GCP does not support IPv6. However, AWS infrastructure supports IPv6 and GCP does not support IPv6.
The SBC in GCP includes the following limitations when compared to the feature set for the SBC running in AWS and Azure:
Subnet gateways in the GCP are virtual. You cannot use them for Link Detection on the SBC, as they do not respond, resulting in continuous switchovers.
For Link Detection configurations of HFE instances in GCP, provide any communicable IP address between the HFE and SBC. Ribbon recommends providing nic2 IP addresses for HFE 2.1, and nic3 and nic4 IP addresses for HFE 2.0.
To use a bastion server for SBC in GCP to access the management interface using private IP addresses, you must create the server in a subnet separate to the management interface.
The SBC in Azure includes the following limitations when compared to the feature set for the SBC running in AWS and GCP:
The SBC in Azure includes the following known feature limitations:
The following limitations apply to Accelerated NICs from the Azure platform:
While carrying out maintenance, the performance of the SBC may get affected, or its service may get interrupted because maintenance freezes the VM for a few seconds..
The maintenance tips given below are applicable to Azure VMs, and not the SBC. Refer to relevant Microsoft documentation for details.
To maintain and handle updates for VMs in Azure, follow the instructions based on your preferred method of interaction with Azure: