2 Technical Specifications
Following are the Cloud Native SBC technical specifications.
RedHat Specifications and Services
Following are the prerequisites for the RedHat platform. This list contains the mandatory services for the Cloud Native SBC.
Table 2-1 Prerequisites
| Software Package | Version/Release | Description |
|---|---|---|
| Red Hat OpenStack Platform | 17.1 or later | Cloud computing platform where the Cloud Native SBC is deployed. |
| Red Hat Openshift Container Platform | 4.18 with patch 4.18.19 or later | Container platform where the Cloud Native SBC is deployed.
Note: Refer to Red Hat’s official documentation and select the appropriate RHEL version based on the compatibility matrix published by Red Hat. |
| Red Hat Enterprise Linux | 9.4 or later | Operating system for the Cloud Native SBC. |
| Kubernetes | 1.31 or later | Container orchestration platform for the Cloud Native SBC. |
| Prometheus or Thanos | As per platform | Collects and stores the Cloud Native SBC metrics. |
| Alert Manager | As per platform | Manages and monitors the Cloud Native SBC alerts generated by Prometheus monitoring system. |
| Grafana | As per platform | It is used to view the pre-configured Cloud Native SBC dashboards. |
| Logging Stack (EFK or LokiStack) | As per platform | Log visualization dashboard for the Cloud Native SBC logs. |
| NFS CSI Provisioner | As per platform | To enable the dynamic provisioning of RWX volume |
| Jaeger | As per platform | Distributed tracing platform for the Cloud Native SBC call traces. |
| cert-manager | As per platform | Used for automated TLS certificates via Certificate Authority, etc. |
| Core-dump management | As per platform | Manages core dump files.
Note - The Cloud Native SBC toolset includes a core dump manager, designed to handle Cloud Native SBC core dump files, especially on platforms without built-in solutions for core dump management. |
| Openshift Router and Nginx | As per platform | It is used for Ingress management and external route handling. |
| Helm | As per platform | Used to deploy the Cloud Native SBC. |
| OpenShift Data Foundation Storage | As per platform | It is used to manage shared storage for the Cloud Native SBC. |
Supported NICs and Drivers
In private virtual infrastructures, Cloud Native SBC supports the following interface input-output modes, ethernet controller, drivers, and traffic type based on input-output modes.
Supported Interface Input-Output Modes for Private Virtual Infrastructures
- Para-virtualized
- SR-IOV
Supported Ethernet Controller, Driver, and Traffic Type based on Input-Output Modes
The following table lists supported Ethernet Controllers (chipset families) and their supported driver that Oracle supports for the Cloud Native SBC deployments. Reference the host hardware specifications, where you run your hypervisor, to learn the Ethernet controller in use.
Note:
The Cloud Native SBC does not support media interfaces when media interfaces of different NIC models are attached to the same pod(Signaling/Media/Transcode Engine) in a SR-IOV network mode.Supported Virtual Network Interfaces and Drivers for Paravirtualization
For paravirtualization network mode, the following vNIC types are supported. You can use any make/model NIC card on the host as long as the hypervisor presents it to the virtual machine as one of these vNIC types.
Table 2-2 Virtual Network Interface
| Virtual Network Interface | DPDK Driver | Interface |
|---|---|---|
| KVM (PV) | virtio | Media Interface |
Supported Ethernet Controllers and Drivers for SR-IOV
For accelerated media/signaling using SR-IOV mode use the following card types.
Table 2-3 Ethernet Controller
| Ethernet Controller | Driver | SR-IOV |
|---|---|---|
| Intel X710 / XL710 / XXV710 | iavf | Media Interface |
| Intel E810 | iavf | Media Interface |
Supported Codec Types
The Cloud Native SBC supports a comprehensive set of industry-standard codecs for transcoding between codecs, ensuring compatibility and optimal media quality across a variety of network scenarios and endpoints. The table below details the currently supported codecs, associated bit rates, RTP payload types, and packetization intervals (ptime). Supported ptime values provide flexibility for different application requirements. Packetization times (ptime) up to 60 ms are supported for select codecs.
| Codec | Supported Bit Rate (kbps) | RTP Payload Type | Default Ptime (ms) | Supported Ptime (ms) |
|---|---|---|---|---|
| G.711 PCMU | 64 | 0 | 20 | 10, 20, 30, 40, 50, 60 |
| G.711 PCMA | 64 | 8 | 20 | 10, 20, 30, 40, 50, 60 |
| G.722 | 48, 56, 64 | 9 | 20 | 20, 40, 60 |
| G.723.1 | 5.3, 6.3 | 4 | 30 | 30, 60 |
| iLBC | 13.33 | 96-127 | 30 | 20, 30, 40, 60 |
| 15.2 | 96-127 | 20 | 20, 30, 40, 60 | |
| G.729/A/B | 8 | 18 | 20 | 10, 20, 30, 40, 50, 60 |
| AMR | 4.75, 5.15, 5.90, 6.70, 7.40, 7.95, 10.2, 12.2 | 96-127 | 20 | 20, 40, 60 |
| AMR-WB (G.722.2) | 6.6, 8.85, 12.65, 14.25, 15.85, 18.25, 19.85, 23.05, 23.85 | 96-127 | 20 | 20, 40, 60 |
| G.726 | 16,24,32,40 | 2,96-127 | 20 | 10,20,30,40,50 |
| EVS | 5.9 to 128 | 96 - 127 | 20 | 20,40,60 |
Protocol and Stack Compatibility Matrix
The Protocol and Stack Compatibility Matrix provides an overview of supported network protocols and IP versions across different network interfaces in Cloud Native SBC. This matrix helps customers quickly determine which protocols are compatible with various network segments, including the internal Kubernetes pod network, service (signaling/media) networks, and external load balancer networks. Where a protocol is not relevant for a specific interface, it is denoted as N/A (Not Applicable). Use this table as a reference to ensure optimal deployment and interoperability with your network infrastructure.
Table 2-4 Protocol Stack Compatibility Matrix
| Protocol | Primary Network(Kubernetes Internal Pod Network) | Service Network (Signaling/Media) | Kubernetes External Load balancer network |
|---|---|---|---|
| Inter-Pod communication | IPv4, IPv6 | N/A | N/A |
| SIP over UDP/TCP/TLS | N/A | IPv4, IPv6 | N/A |
| RTP | N/A | IPv4, IPv6 | N/A |
| RTCP | N/A | IPv4, IPv6 | N/A |
| SRTP | N/A | IPv4, IPv6 | N/A |
| DNS | IPv4, IPv6 | IPv4, IPv6 | N/A |
| Lawful Intercept (X1 interface) | N/A | N/A | IPv4, IPv6 |
| Lawful Intercept (X2 interface) | N/A | IPv4, IPv6 | N/A |
| Lawful Intercept (X3 interface) | N/A | IPv4, IPv6 | N/A |
| Configuration Manager's REST/HTTPS | N/A | N/A | IPv4, IPv6 |
| Console GUI's HTTPS | N/A | N/A | IPv4, IPv6 |
| CLI HTTPS | N/A | N/A | IPv4, IPv6 |
| STIR/SHAKEN | N/A | IPv4, IPv6 | N/A |
| CDR/SFTP | IPv4, IPv6 | N/A | N/A |
| Core Dump Manager/SFTP | IPv4, IPv6 | N/A | N/A |
| Cloud Native SBC Operator to OpenStack Controller | IPv4, IPv6 | N/A | N/A |
| Automated Test Suite GUI HTTPS | N/A | N/A | IPv4, IPv6 |
| Automated Test Suite REST/HTTPS | N/A | N/A | IPv4, IPv6 |