Versions Compared

Old Version 2

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version Current

changes.mady.by.user Ribbon Communications

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Automatic update to correct links
Panel
borderColorgreen
bgColortransparent
borderWidth2
Noprint

Back to Table of Contents

Additional sections:

Children Display
depth2
styleh6

Add_workflow_for_techpubs
AUTH1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
JIRAIDAUTHSBX-74291
REV5UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26ced50c99, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c9b802f6, userName='null'}

 

Panel

In this section:

Table of Contents
maxLevel4

Info
iconfalse

Related articles:

Children Display

Spacevars
0series
and 
Spacevars
0series2
routing and policy management involves high performance SIP routing with scalable routing policies for service-provider and enterprise networks.

Key Features

  • Screening, blocking, routing, presentation, call type filters
  • Route prioritization
  • Leading digit routing; International routing; URI based routing
  • Digit/parameter manipulation
  • E911 support; Priority Call handling
  • Toll-free routing
  • Least cost routing
  • Number portability

Policy Server Modes

The 

Spacevars
0series
and 
Spacevars
0series2
servers provide the following

...

routing and policy management options for your network:

  • Embedded Routing Engine (ERE) – ERE provides less routing and policy management functionality and is intended for smaller networks with no complex routing needs.

...

  • External
    Spacevars
    0

...

Spacevars
0series2

...

  • company
     Policy

...

  • Server (PSX)

...

  •  –  PSX combines complex call-routing functionality with exceptional capacity to support larger networks.

Spacevars
0product
is configurable to interact with

...

up to nine

...

centralized external PSXs, or a combination of external PSXs and ERE.

Caption
0Table
1Policy Server Modes

Configuration

Basic ERE

Advanced ERE

...

Replica ePSX
(Connected to External Master PSX)

 Centralized External PSX

Number of SBCs Deployed
(Small: 1-3, Large: more than 3)

...

SmallSmallLarge
Routing ComplexitySimpleComplexComplex

...

 

For performance and capacity comparison of ERE

...

and PSX, refer to Routing Engines Comparison

...

.

...

Deployment Scenarios

SBC ERE

Basic and Advanced ERE

...

Basic ERE is the default routing engine on the SBC 5000 series for performing basic call routing services. The Advanced ERE is a licensed option for customers requiring expanded routing functionality.

The ERE can be installed by selecting the embedded routing engine (ERE) option while installing the

Spacevars
0product
application using the EMA Platform Mode. For more information on installing 
Spacevars
0product
application (ERE Configuration), refer to Installing SBC Application

...

.

Caption
0Figure
1SBC with ERE

Image Modified

The Advanced ERE is a licensed option for customers requiring expanded routing functionality.

Caption
0Table
1Basic ERE vs. Advanced ERE
Features
Basic-ERE
Advanced-ERE
Maximum Number of Routes2,000100,000
Route PrioritizationRoute prioritizationRoute prioritization with more parameters
such as Time of Day and overflow routing.
Routing MechanismsRouting mechanisms such as
User Name and Standard
Destination Based Routing.		Routing mechanisms such as User Name,
Standard Destination Based Routing, Call Type,
Digit Type and Time Range.
Call Screening and Blocking ServicesNot applicableCall screening and call blocking services to
enable a carrier to restrict calls based on either
origination, destination or both.

ERE With External PSX

You can configure the SBC to use an external PSX for routing and the ERE for fallback routing. When the external PSX is up and running, all routing is handled by the external PSX and ERE routing configurations are ignored.

Thus, in the unlikely event that the external PSX goes down, you can fall back to ERE routing by simply setting the SBC's remote server state to 'disabled' from the EMA UI.

Caption
0Figure
1ERE With External PSX

Image Modified

To set up an external PSX for routing, perform the following:

  1. Configure remote server from EMA (

...

  1. refer to Policy Server - Remote Server for details).
    1. Navigate to Configuration > SystemSetup tab.
    2. Click the arrow next to Policy Server perspective in the navigation panel, and select Remote Server option. The "Remote Server" configuration window displays.
    3. Configure the remote policy server settings to use the external PSX.
  2. Provision routing for the 
    Spacevars
    0product
    in the external PSX using the PSX Manager.
  3. Provision routing from EMA (

...

  1. refer to Category - Call Routing for details).
    1. Navigate to Configuration > System Provisioning tab.
    2. From the Category drop-down menu, select Call Routing.
    3. Choose applicable perspectives to provision routing using ERE.

 

Info
For more information on the routing and policy management features supported by ERE, refer to Routing Engines Comparison. 

Centralized PSX

The centralized PSX server combines call

...

routing functionality with the exceptional capacity

...

of storing tens of millions of call routes in a single database. This 

Spacevars
0product
-Centralized PSX deployment distributes that routing intelligence to every PSX server in the network and simplifies the provisioning process. For more information

...

on PSX

...

, refer to the Policy Server (PSX) Documentation.  

The following figure depicts the

Spacevars
0product
deployed with external PSX and EMS.

Caption
0Figure
1SBC with External PSX and EMS

Image Modified

To configure external PSXs as Active and Standby remote policy servers from the 

Spacevars
0series
or
Spacevars
0series2
server,

...

refer to Configuring SBC

...

for External PSX.

Standalone ePSX

 The following figure depicts the standalone ePSX which uses EMA for provisioning.  

Caption
0Figure
1SBC with Standalone ePSX

Image Removed

The ePSX provides the ability to run a fully functional PSX within a virtual machine running on

Spacevars
0series
/
Spacevars
0series2
hardware. One of the advantages of this ability is that it eliminates the need for a physically separate PSX machine in the network. As with the PSX, the ePSX is intended for larger networks with complicated routing.

The core technology of virtualization is the hypervisor. A hypervisor manages virtual machines, allocates resources and provides hardware emulation to the guest systems.  A type 1 hypervisor runs directly on the hardware, providing services for all running systems.  A type 2 hypervisor runs under a native operating system and provides services to all but the host system. KVM (Kernel-based Virtual Machine) is a type 2 hypervisor for Linux systems and is used to provide SBC virtualization services. The ePSX application executes as a completely independent machine from the host 

Spacevars
0product
system.

The ePSX shares the host’s network interfaces, but maintains a separate IP address. This is accomplished by linking the physical and virtual interfaces via a Linux bridge device. The bridge is a layer 2 software switch that allows multiple logical interfaces to be combined on the same physical interface. Network processor (NP) enhancements to support multiple virtual interfaces are needed to maintain network performance and security.

The ePSX is delivered as an additional package in SBC software bundle. During SBC installation, either ERE or ePSX can be selected as the routing engine. The ePSX is delivered as an OVF (Open Virtualization Format) package. OVF is an emerging standard for the distribution of virtual machines, and provides mechanisms for defining the resource requirements of the guest and for tailoring applications to their target environment.

To enable ePSX functionality during initial 

Spacevars
0product
application installation from the EMA, the user first chooses ePSX option instead of ERE. Once the
Spacevars
0product
application is installed on both servers, the ePSX OVA package (a tar archive file including the OVF directory) is installed.

Warning

The ePSX cannot be added to an SBC with an existing ERE configuration. A fresh installation is required.

The ePSX supports two modes: Replica ePSX and Standalone ePSX. In Replica ePSX mode, the ePSX functions like a PSX slave, where all configuration data is replicated from its designated master. In Standalone ePSX mode, the ePSX behaves similar to a PSX master where all configuration data is provisioned via EMS/EMA. The Standalone ePSX does not replicate data to any external PSX slaves.

Note

The ePSX is not supported on SBC 5100 due to the hard drive size limitation.

Note

ePSX is not supported in SBC Software Edition (SBC SWe).

For more information on installing and configuring a Standalone ePSX, see Installing Standalone ePSX on a Standalone SBC, Installing Standalone ePSX on HA Pair SBC, Call Routing: System Provisioning - ePSX and Configuring SBC to Use External PSX.

For more information on the PSX policy server capabilities, refer to Sonus Policy Server (PSX) documentation.

Replica ePSX

The following figure depicts replica ePSX deployments using an external PSX Master for provisioning and external EMS for FCAPS functionality.

Caption
0Figure
1SBC Deployments Using Replica ePSX

Image Removed

Image Removed

For more information, see Installing Replica ePSX on HA Pair SBC, Call Routing: System Provisioning - ePSX, Configuring SBC to Use External PSX, and/or Allowing a Replica ePSX Installed with a Higher Version than the Master PSX. For more information on the PSX policy server capabilities, refer to Sonus Policy Server (PSX) documentation.

Note

The sequence to upgrade PSXs when there is a replica ePSX acting as a slave to an external PSX Master is similar to the existing Master-Slave PSX upgrade scenarios.  For more information on the LDM or other upgrade scenario sequences, refer the Sonus Policy Server (PSX) documentation.

Hidden SBC Configuration Objects When ePSX is Installed

The following SBC configuration objects are not available (hidden) when the ePSX is installed because the configurations are controlled by PSX.

Noprint

Click to view

Toggle Cloak

Configurations Controlled by PSX

The following SBC configuration objects are controlled by the PSX.

  • Aor Group
  • Call Parameter Filter Profile
  • Call Recording Criteria
  • Carrier (Global object)
  • Class of Service
  • Codec Entry
  • Codec List Profile
  • Codec Routing Priority
  • Country (Global object)
  • Crypto Suite Profile
  • DM/PM Criteria (Digit Parameter Handling object)
  • DM/PM Rule (Digit Parameter Handling object)
  • e911 (Servers object)
  • e911VpcDevice (Servers object)
  • Element Routing Priority Profile

...

  • enumDomainName
  • enumDomainName Label
  • Enum Service (Servers object)
  • Feature Control Profile
  • Holiday Profile
  • IP Signaling Peer Group
  • Ip Signaling Profile
  • Lwresd Profile
  • Media Qos KPI Profile
  • Call Routing
  • NPA/Nxx (Global object)
  • Number Globalization Profile
  • Numbering Plan (SIP Trunk Group Policy)
  • Number Translation Criteria (Digit Parameter Handling object)
  • Packet Service Profile
  • Prefix Profile (Digit Parameter Handling object)
  • Route (Call Routing object)
  • Routing Label (Call Routing object)
  • Script (Global object)
  • Signaling Profile
  • Signaling QoS KPI Profile
  • SIP Domain (Global object)
  • Srs Group Cluster
  • Srs Group Profile
  • Subscriber (Global object)
  • Time Range Profile

...

  • Trunkgroup

...

 

...

...

Basic Call Flow Using ePSX

  • Voip Subscriber

Pagebreak

...

...