Versions Compared

Old Version 2

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version 3

changes.mady.by.user Ribbon Communications

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Panel

...

borderColorgreen
bgColortransparent
borderWidth2
Noprint

Back to Table of Contents

Back to SBC Network Deployment Scenarios

Back to Service Provider Deployment Scenarios

Additional sections:

In this section:

Children Display
styleh5

 

...

This section describes specific scenarios involving the deployment of a 

Spacevars
0product
 Session Border Controller within a Network-Network-Interface (NNI) across two carriers. The use cases described in this section illustrate the
Spacevars
0product
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.

Spacevars
0product
acting as a peering
Spacevars
0product
connects these IP networks (carriers, sub-networks, long distance networks, etc.)  providing extensive routing capabilities and resource management.

Spacevars
0product
in this configuration is also referred to as a Trunking
Spacevars
0product
(T-
Spacevars
0product
). In NNI deployment the call model does not support registration, refreshes etc. It supports only SIP calls conforming to a highly scalable model. The
Spacevars
0product
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
    Spacevars
    0product
    sits at the edge (operator-dependent).
  • Acts as IBCF in the IMS network environment.

Peering

Spacevars
0product
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
    Spacevars
    0product
    does not understand).
  • Providing SIP Message content manipulation functionality.
Caption
0Figure
1Peering (NNI) deployments

Image Modified

Note
This diagram does not reflect that each network in an NNI deployment can have multiple
Spacevars
0product
s (
Spacevars
0product
or 3rd-party
Spacevars
0product
s) at the border.
Note

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

Pagebreak