You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Back to Table of Contents

Back to Installing SBC SWe Software

Back to Installation Overview

In this section:

Deployment Scenarios

Two basic deployment scenarios exist for the

Unable to show "metadata-from": No such page "_space_variables"
routing and policy management. 

  1. Unable to show "metadata-from": No such page "_space_variables"
    running exclusively on a server.
  2. Unable to show "metadata-from": No such page "_space_variables"
    co-hosted with other virtualized applications on a server.

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:

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.

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.

SBC with External PSX and EMS

Embedded Routing Engine (ERE)

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

SBC with ERE.

For more information on installing the

Unable to show "metadata-from": No such page "_space_variables"
application, refer Installing SBC SWe on Virtual Platforms.

  • No labels