Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Noprint
Panel
borderColorgreen
bgColortransparent
borderWidth2

Back to Table of Contents

Back to SBC Network Deployment Scenarios

Back to Service Provider Deployment Scenarios

Back to Peering (NNI) Scenarios

Panel

In this section:

Table of Contents
maxLevel2
minLevel1

Scenario

Connecting an 

Spacevars
0product
 across two or more VoIP islands.

Background Information

  • The system is installed in a service-provider's network interconnecting two of its customers.
  • The system exposes only the Trunk Group- (SIP Trunk Group)-based routing and the Trunk Group/Sip Server-combination-based routing models.
  • The customers' networks are represented by specific points of contact, i.e. by Sip Servers, rather than a set of machines (SIP Trunk Group).
  • The requirements specified in the"Background Information and Dependencies" topic of  Minimal Out-Of-The-Box Configuration section are met.
  • Ports and IP Interface Groups have been configured as described in NNI-Complex route selection topic.
  • Transcoding can be applied, depending upon the operator, at the edge to normalize traffic for the core.
  • The call model is purely SIP static-routing based. Hence, it does not require registration, refreshing etc.
  • Operators tend to aggregate traffic to peering points, so scaling works well.
  • Peers are static and well known.
  • Operators benefit from extensive routing capabilities in this environment, e.g. LCR, TAR, ToD etc.
Caption
0Figure
1SBC placed across IP core networks in NNI

Image Modified

 

...

Pagebreak