The articles in the section Configuring SBC Core describe configuration tasks that apply generally across the SBC Core product family, including both hardware-based SBCs and the virtualized SBC Software Edition (SWe). However in some cases, a virtualized environment or the different deployment options offered by SBC SWe impact configuration procedures.
The articles in this section describe the configuration models supported when SBC SWe is configured as a cluster and deployed with Insight EMS. It also provides configuration information that applies specifically to SBC SWe deployments. The procedures indicate to which types of SWe deployments they apply. For more information on the different types of SBC SWe deployments, refer to SBC Software Edition - SBC SWe.
Table of Contents
- SBC SWe Configuration Management
- SBC SWe Configuration Procedures
- Activating Callmix Profile on SBC SWe
- Basic SBC SWe Configuration using SBC Configuration Manager
- Configuring Gateway to Gateway Signaling on I-SBC and D-SBC
- Configuring Intra-Cluster VNFC Communication Using Packet Ports
- Configuring PSX FQDN as Remote Policy Server
- Configuring SBC SWe in OpenStack Cloud Environment for GPU Transcoding
- Configuring the SBC for Lawful Interception
Note
In prior releases, a designated “Headend” SBC was used to configure SBC SWe clusters. Beginning with SBC release 8.0, the OAM node and Direct Single configuration models replace the Headend model. Refer to SBC SWe Configuration Management for an overview of these models. To enable migration to one of the new models, Insight EMS 12.x continues to support the Headend configuration model for SBC clusters on prior releases. However SBC SWe clusters on release 8.0 or later must use either the OAM node or Direct Single configuration model.
Overview
Content Tools