Ribbon recommends using the Transparency Profile to configure transparency on the SBC Core for new deployments, as well as applying additional transparency configurations to existing deployments. Do not use IP Signaling Profile flags in these scenarios because the flags will be retired in upcoming releases.
Refer to the SBC SIP Transparency Implementation Guide for additional information.
This section describes specific scenarios involving the deployment of a SBC Session Border Controller within a Network-Network-Interface (NNI) across two carriers. The use cases described in this section illustrate the SBC features from a user’s standpoint in the peering network.
The Peering or Network-Network Interface (NNI) refers to the service control interface between two or more IP networks. The SBC acting as a peering SBC connects these IP networks (carriers, sub-networks, long-distance networks, etc.) providing extensive routing capabilities and resource management.
The SBC in this configuration is also referred to as a Trunking SBC (T-SBC). In an NNI deployment, the call model does not support registration, refreshes, etc. It supports only SIP calls conforming to a highly scalable model. The SBC in a peering deployment includes the following characteristics:
The peering SBC enforces bilateral agreements by ensuring the correct aspects and interpretations of the SIP protocol between carriers.
Peering (NNI) deployments
Additional topics: