IMPORTANT

Ribbon recommends using the Transparency Profile to configure transparency on the SBC Core 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. SBC acting as a peering SBC connects these IP networks (carriers, sub-networks, long distance networks, etc.)  providing extensive routing capabilities and resource management.

SBCin this configuration is also referred to as a Trunking SBC (T-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:

  • Provides protection to the core both from malicious attacks and genuine but high traffic levels.
  • Acts as a B2B UA to bridge/bond the ingress/egress SIP sessions while maintaining distinct networks at the lower layers.
  • Provides facilities for protocol repair and adaptation.
  • Polices/enforces bandwidth and resource utilization.
  • Provides encryption services.
  • Interwork between combinations of IPv6 and IPv4 for both media and signaling (does not translate between IP address types).
  • Performs a key role in routing by selecting between different carriers.
  • Provides transcoding functionality and normalizes traffic to the core since SBC sits at the edge (operator-dependent).
  • Acts as IBCF in the IMS network environment.

Peering SBC enforces bilateral agreement by ensuring the correct aspects and interpretations of the SIP protocol between carriers.

  • Ensuring each side receives the expected SIP headers, formats and content.
  • Applying ingress/egress signaling filters.
  • Ensuring transparency of SIP content (operators may use information the SBC does not understand).
  • Providing SIP Message content manipulation functionality.

Peering (NNI) deployments

This diagram does not reflect that each network in an NNI deployment can have multiple SBCs (SBC or 3rd-party SBCs) at the border.

The example graphic depicts the SBC 5000, but all the platforms are supported.

 

 

Additional topics:

 

 

  • No labels