Skip to end of metadata
Go to start of metadata

In this section:

Overview

SBC Core licensing requires customers to use SBC features through software license keys purchased and obtained from Sonus. Once purchased, customers install and manage SBC licenses using the Embedded Management Application (EMA) License Management application. 

License files contain up to two SBC serial numbers. For a stand-alone SBC, the machine’s serial number must be contained in the license file to be valid. Likewise, for a SBC HA pair the serial numbers of both machines must be contained in the license file to be valid.

The "SBC Licenses" table below lists the currently enforceable SBC licenses. Please contact your Sonus sales representative for licensing details.

To install or delete SBC licenses, or view currently installed licenses, see System Administration - License Management.

SBC Licenses

To compare which features are supported between Basic ERE, Advanced ERE and ePSX configurations, see Routing Engines Comparison.

SBC Feature Licenses

Click here to expand:

SBC Protocol Licenses

Click here to expand:


SBC Base Licenses

Click here to expand:


ePSX Licenses

ePSX License File Architecture

The ePSX licenses are classified into five basic types: Feature, Protocol, Base, Access Protocol and Access.

Table : ePSX License File Architecture

ePSX ConfigurationLicense IdentifierClassification
Standalone ePSX

POL–EPSXS/SA<FEATURE>Exxx-CPS

Enables ePSX Standalone Features (LNP, Toll Free, Calling Name, etc.). License is based on the number of CPS of the BASE software license.

POL–EPSXS/SA<PROTOCOL>Exxx-CPS

Enables ePSX Standalone Protocols (TCAP, ITUTCAP, ENUM, etc.). License is based on the number of CPS of the BASE software license.

POL–EPSXSABASESWExxx-CPS

ePSX Standalone Base Software license. This is a mandatory license for ePSX deployments.

The BASESW CPS should equal CPS from local SBC plus calls coming from third-party elements.

POL–EPSX–SA–SIP–Exxx-CPS

ePSX Standalone SIP Access Protocol license required for third-party elements to query the ePSX using SIP.

POL–EPSX–SA-CRS–Exxx-CPS

ePSX Standalone Access license required for third-party elements to query the ePSX.
Replica ePSX

POL–EPSX–R/RP–<FEATURE>–Exxx-CPS

Enables ePSX Replica features (LNP, Toll Free, Calling Name, etc.). License is based on the number of CPS of the BASE software license.

POL–EPSX–R/RP–<PROTOCOL>–Exxx-CPS

Enables ePSX Replica Protocols (TCAP, ITUTCAP, ENUM, etc.). License is based on the number of CPS of the BASE software license.

POL–EPSX–RP–BASESW–Exxx-CPS

ePSX Replica Base Software license. This is a mandatory license for ePSX deployments.

The BASESW CPS should equal CPS from local SBC plus calls coming from third-party elements.

POL–EPSX–RP–SIP–Exxx-CPS

ePSX Replica SIP Access Protocol license required for third-party elements to query the ePSX using SIP.

POL–EPSX–RP–CRS–Exxx-CPS

ePSX Replica Access license required for third-party elements to query the ePSX.

Key:

"xxx" is the Calls Per Second (CPS) value.

ePSX License Descriptions

SBC Releases Prior to V04.02.02R2:

When installing ePSX licenses, the SBC and ePSX license bundles must include the following licenses, at a minimum, as well as be installed in the order shown in example below.

Bundle 1: Installed on SBC

  • SBC-RTU (Only include this SBC license if it is not already installed)
  • other licenses, as appropriate

Bundle 2: Installed on SBC

  • POL-BASE (This license starts the ePSX and enables ePSX functionality)

      NOTE:  To avoid the error below, wait 60 seconds before installing license Bundle 2 to allow the SBC time to start up the ePSX.

Bundle 3: Installed inside ePSX Oracle database with a reference to SBC

  • POL-EPSX-BASESW-100CPS
  • other licenses, as appropriate

If the following error displays while applying the POL-BASE license, please ignore it. It simply indicates the ePSX has not yet started. The error message will no longer display once the licenses are installed and the ePSX is up and running.

Error during ePSX license retrieval: LicenseMgmtFailException: PsxLicenseMgmtException: Connection refused.

SBC Release V04.02.02R2 and Later:

The POL-BASE license is always on following ePSX installation, thus the ePSX starts up automatically. When installing both ePSX and PSX licenses, ensure you install all ePSX licenses first before installing PSX licenses.

ePSX Feature Licenses

Click here to expand:

 

ePSX Protocol Licenses

Click here to expand:


ePSX Base Licenses

Click here to expand:

 

ePSX Access Protocol Licenses

Click here to expand:


ePSX Access Licenses

Click here to expand: