In this section:
SBC 5xx0/5400/7000 routing and policy management involves high performance SIP routing with scalable routing policies for service-provider and enterprise networks.
The SBC 5xx0/5400/7000 servers provide the following routing and policy management options for your network:
SBC is configurable to interact with up to nine centralized external PSXs, or a combination of external PSXs and ERE.
Configuration | Basic ERE | Advanced ERE | Centralized External PSX |
---|---|---|---|
Number of SBCs Deployed | Small | Small | Large |
Routing Complexity | Simple | Complex | Complex |
For performance and capacity comparison of ERE and PSX, refer to Routing Engines Comparison.
Basic ERE is the default routing engine on the SBC 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 SBC application using the EMA Platform Mode. For more information on installing SBC application (ERE Configuration), refer to Installing SBC Application.
Features | Basic-ERE | Advanced-ERE |
---|---|---|
Maximum Number of Routes | 2,000 | 100,000 |
Route Prioritization | Route prioritization | Route prioritization with more parameters such as Time of Day and overflow routing. |
Routing Mechanisms | Routing 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 Services | Not applicable | Call screening and call blocking services to enable a carrier to restrict calls based on either origination, destination or both. |
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.
To set up an external PSX for routing, perform the following:
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 SBC-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 PSX Documentation.
The following figure depicts the SBC deployed with external PSX and EMS.
To configure external PSXs as Active and Standby remote policy servers from the SBC 5xx0/5400/7000 server, refer to Configuring SBC for External PSX.
The following SBC configuration objects are controlled by the ERE.
When an instance is launched on cloud platforms, if the instance is installed with the "enableERE" option set to false in the user data provided to the instance, the ERE processes will not run, and the policy must be provided by an external PSX cluster. When an instance is launched on cloud platforms with type m-sbc or type slb, the ERE processes will not run.
Therefore, the I-SBC and S-SBC can use the local policy server, but only if it is installed with the "enableERE" set to true in the instance user data.
The following example shows only a section of the total user data file with the enableERE option set to enabled.
{ "ThirdPartyCpus": "0", "ThirdPartyMem": "0", "enableCoreEMA": "enabled", "enableERE": "enabled", "enableREST": "enabled", "enableTS": "enabled"