|Sonus Documentation Portal|
The Transparency Profile is the recommended method of configuring transparency on the SBC Core for new deployments as well as when 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. SBC acting as a peering SBC connects these IP networks (carriers, sub-networks, long distance networks, etc.) providing extensive routing capabilities and resource management.
An SBC in this configuration is also referred to as a Trunking SBC. In 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 peering deployment includes the following characteristics:
Peering SBC enforces bilateral agreement by ensuring the correct aspects and interpretations of the SIP protocol between carriers.
The example graphic depicts the SBC 5000, but all the platforms are supported.