3 New Features
Backup and Restore
The Backup and Restore Operator has been introduced to automate the backup and restore of Cloud Native SBC application configurations, enabling faster disaster recovery to ensure business continuity and minimize downtime. This feature supports both scheduled and on-demand backups, enabling enhanced data protection and operational flexibility. The entire backup and restore lifecycle—including task scheduling, verification, and secure storage in object storage—is managed via newly introduced custom resource definitions (CRDs). The administrators can perform seamless backups of configurations, LRT files, and CA certificate files. The Backup and Restore Operator is part of the Cloud Native SBC Operator component, and its lifecycle—including install, upgrade, rollback, and uninstall—is managed through the Cloud Native SBC Operator Helm chart.
Restoration is a one-time activity and temporarily restricts application upgrades during execution. For detailed setup instructions, refer to the Oracle Cloud Native Session Border Controller Installation Guide.
In addition, the Cloud Native SBC Console supports periodic and on-demand backups using Helm. For periodic backups, update the backup parameters in the Console values YAML file. Then run a Helm upgrade to apply the changes. For on-demand backups, create and apply a Kubernetes YAML manifest in the Console namespace. On-demand restore of the Console is currently not supported.
For more information about disaster recovery, refer to the Disaster Recovery chapter of the Oracle Cloud Native Session Border Controller Disaster Recovery Guide.
Overlapping IP Address Support Across VLANs
The Cloud Native SBC solution supports overlapping IP address ranges across multiple VLANs on a single interface by utilizing 802.1q VLAN tagging for both IPv4 and IPv6. Each physical network supports a maximum of 500 tagged service networks, with an overall limit of 1,500 tagged service networks across all physical networks. Service networks and the VLAN tagged networks are configurable through Cloud Native SBC Console GUI and Cloud Native SBC applications REST API. Any changes to service networks configuration takes effect after successful activation. Additionally, overlapping IP address functionality remains available during high availability switchovers, ensuring continuous operation, scalability, and manageability in line with other Cloud Native SBC Console features.
Note:
The Service Network parameters have been moved from the Cloud Native SBC application values YAML file to the Cloud Native SBC Console GUI.To learn more about overlapping IP support and the types of service network, refer to the Service Network Element chapter in the Oracle Cloud Native Session Border Controller User Guide.
To learn more about the REST APIs associated with the service network, refer to the Oracle Cloud Native Session Border Controller Application REST API Guide.
SIPREC Functionality
The Cloud Native SBC's SIPREC(Session Initiation Protocol Recording) functionality offers a targeted call recording solution designed to enhance both media and signaling efficiency on recording servers. It enables selective recording capabilities, and effectively isolates the Recording Server (RSS) from the active communication session.
To learn more about the SIPREC functionality, refer to the Selective Call Recording SIPREC chapter in the Oracle Cloud Native Session Border Controller User Guide. For information on the metrics and alerts associated with SIPREC, see the Oracle Cloud Native Session Border Controller Observability Guide.
Emergency Location Identification Number (ELIN) Support
The Cloud Native SBC supports Emergency Location Identification Number (ELIN) gateways for integration with E911 service providers. The gateway replaces VoIP extension URIs with ELIN numbers during emergency calls, enabling accurate location identification and reliable user callbacks. The Cloud Native SBC supports ELIN numbers, employing intelligent reuse to accommodate multiple concurrent E911 calls. An internal mapping table retains ELIN-to-extension associations for a configurable period, ensuring Public Safety Answering Point (PSAP) callbacks reach the correct caller.
For more information about ELIN support, refer to the Emergency Location Identification Number (ELIN) Gateway Support chapter in the Oracle Cloud Native Session Border Controller User Guide.
SNMP Support for Prometheus Alert Manager
The Cloud Native SBC supports Management Information Base (MIB) files, enabling seamless integration of Prometheus Alert Manager webhook support for SNMP traps. This feature allows you to leverage SNMP-based alerting and enhances observability and operational responsiveness within the Cloud Native SBC. The Cloud Native SBC requires Prometheus Alert Manager for alarm management and does not support observability tools that do not integrate with Prometheus. SNMP v2 and v3-compatible MIB files define all alert rules, simplify trap receiver configuration, and ensure smooth integration with observability systems. Each SNMP trap includes unique Object Identifiers (OIDs) mapped to Cloud Native SBC alerts, supporting efficient categorization and troubleshooting in trap receiver logs.
For more information about SNMP alerts, refer to Alert Manager chapter in the Oracle Cloud Native Session Border Controller User Guide.
Integration of Cloud Native SBC with Microsoft Teams
The Cloud Native SBC can integrate with Microsoft Teams, allowing organizations to securely connect on-premises telephony systems with Teams. This supports Microsoft Teams integration in Non-media bypass mode only, providing a secure and interoperable bridge between legacy telephony infrastructure and Microsoft 365. Proper configuration and Microsoft certification for Direct Routing are required.
For more information about integration of Cloud Native SBC with Microsoft Teams, refer to the Configuring Objects to integrate MS Teams section in the Realms and Nested Realms chapter of the Oracle Cloud Native Session Border Controller User Guide.
Enhanced Support for Virtualized Cloud Environments with Intel E810 Network Interface
For accelerated media and signaling workloads using SR-IOV mode, Cloud Native SBC supports the Intel E810 Ethernet controller with the iavf driver, providing optimized performance for media interfaces in high-throughput environments. This enhancement enables organizations to leverage the latest generation of optical network interfaces from Intel, supporting performance, compatibility, and future-ready scalability.
To learn more about Intel E810 network interface card (NIC), refer to the Supported NICs and Drivers section in the Oracle Cloud Native Session Border Controller Release Notes.
Cloud Native SBC Bare Metal Deployment on Red Hat Openshift
The Cloud Native SBC supports deployment on Red Hat Openshift environments running on bare metal infrastructure. This enables carriers and enterprises to reduce complexity and lower total cost of ownership by running Cloud Native SBC workloads on Openshift deployed on bare metal. All Cloud Native SBC components—including the Cloud Native SBC application, Cloud Native SBC Console, Cloud Native SBC Operator, Automated Test Suite, and Data Collector—are fully supported in Openshift bare metal environments. SR-IOV network mode is supported with Openshift bare metal. Organizations running previous releases of Cloud Native SBC can upgrade to this release. Orchestration tooling remains unchanged, with continued support for Prometheus exposition format, OpenTelemetry, and Multus for multiple vNIC assignments. All features are available on Openshift bare metal, with platform-specific validation provided as needed.
For detailed information about preparing the platform to install Cloud Native SBC, refer to the Oracle Cloud Native Session Border Controller Platform Preparation Guide for OpenShift on Bare Metal. For instructions on installing Cloud Native SBC for OpenShift on bare metal, refer to the Oracle Cloud Native Session Border Controller Installation Guide
Documentation Changes
The following information outlines the documentation changes included in this release.
- The book previously titled Oracle Cloud Native Session Border Controller Platform Preparation Guide for OpenShift has been renamed to Oracle Cloud Native Session Border Controller Platform Preparation Guide for OpenShift on OpenStack.
- The book previously titled Oracle Cloud Native Session Border Controller GUI Guide has been renamed to Oracle Cloud Native Session Border Controller Console GUI Guide.
- The Oracle Cloud Native Session Border Controller Platform Preparation Guide OCCNE has been removed from the Cloud Native SBC documentation package.
- The Cloud Native SBC documentation package includes two new books titled as below:
- Oracle Cloud Native Session Border Controller Platform Preparation Guide for OpenShift on Bare Metal
- Oracle Cloud Native Session Border Controller Troubleshooting Guide