Versions Compared

Key

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

Add_workflow_for_techpubs
AUTH2bscoggins
AUTH1ghoppe
REV5kvenkatraman
REV6kvenkatraman
REV3bscoggins
REV1

...

bscoggins

Panel

...

borderColorgreen
bgColortransparent
borderWidth2

...

Back to Table of Contents

Back to Installing SBC SWe Software

Back to Installation Overview

In this section:

Table of Contents

Deployment Scenarios

Two basic deployment scenarios exist for the

Spacevars
0series3
routing and policy management. 

  1. Spacevars
    0product2
    running exclusively on a server.
  2. Spacevars
    0product2
    co-hosted with other virtualized applications on a server.
Info

For graphical illustrations of test configurations using these two scenarios, please see SBC SWe Performance Metrics page.

Routing and Policy Management

The two basic configurations for routing and policy management are:

Table of Contents
maxLevel3
minLevel3

Centralized Sonus Policy Server (PSX) 

The centralized PSX server combines call routing  functionality with exceptional capacity of storing tens of millions of call routes in a single database. This SBC-Centralized PSX deployment distributes that routing intelligence to every PSX server in the network and simplifies the provisioning process.

Info
For more information on Sonus Policy Server (PSX), refer the PSX Policy Server Documentation.
For information on how to configure SBC to use external PSX, refer Configuring SBC to Use External PSX.

Figure 1 describes SBC deployed with external PSX and an EMS.

Caption
0Figure
1SBC with External PSX and EMS

Image Modified

Embedded Routing Engine (ERE)

ERE provides less routing and policy management functionality and is intended for smaller networks with no complex routing needs. 

Caption
0Figure
1SBC with ERE.

Image Modified

Info

For more information on installing the

Spacevars
0product2
application, refer Installing SBC SWe on Virtual Platforms.

Pagebreak