Feature Entitlements
You enable the features that you purchased from Oracle, either by self-provisioning using the setup entitlements command, or installing a license key at the system, license configuration element.
This release uses the following self-provisioned entitlements and license keys to enable features.
The following table lists the features you enable with the setup entitlements command.
| Feature | Type |
|---|---|
| Admin security | Enabled or Disabled |
| Advanced | Enabled or Disabled |
| Advanced Security Suite (JITC) | Enabled or Disabled |
| Data integrity (FIPS) | Enabled or Disabled |
| Session Capacity | Number of sessions |
| STIR/SHAKEN Client | Enabled or Disabled |
| Transcode AMR-NB | Enabled or Disabled |
| Transcode AMR-WB | Enabled or Disabled |
| Transcode EVRC | Enabled or Disabled |
| Transcode EVRC-B | Enabled or Disabled |
| Transcode EVS | Enabled or Disabled |
| Transcode OPUS | Enabled or Disabled |
| Transcode SILK | Enabled or Disabled |
The following tables lists the features for the Oracle Communications' Session Router (SR) you enable with the setup entitlements command. When setting up an SR, you choose between either the Session Stateful or the Transaction Stateful Session Routers. The Enterprise Session Router entitlements are the same.
This first SR table lists entitlements for the Session Stateful Session Router.
| Feature | Type |
|---|---|
| Session Capacity | Number of sessions |
| Accounting | Enabled or Disabled |
| Load Balancing | Enabled or Disabled |
| Policy Server | Enabled or Disabled |
| STIR/SHAKEN Client | Enabled or Disabled |
| Admin security | Enabled or Disabled |
| ANSII R226 Compliance | Enabled or Disabled |
This second SR table lists entitlements for the Transaction Stateful Session Router.
| Feature | Type |
|---|---|
| MPS Capacity | Number of sessions |
| Admin security | Enabled or Disabled |
| ANSII R226 Compliance | Enabled or Disabled |
| Load Balancing | Enabled or Disabled |
Encryption for Virtual SBC
You must enable encryption for virtualized deployments with a license key. The following table lists which licenses are required for various encryption use cases.
| Feature | License Key |
|---|---|
| IPSec Trunking | IPSec |
| SRTP Sessions | SRTP |
| Transport Layer Security Sessions | TLS Foot 1 |
| MSRP | TLS |
Footnote 1 The TLS license is only required for media and signaling. TLS for secure access, such as SSH, HTTPS, and SFTP is available without installing the TLS license key.
To enable the preceding features, you install a license key at the system, license configuration element. Request license keys at the License Codes website at http://www.oracle.com/us/support/licensecodes/acme-packet/index.html.
After you install the license keys, you must reboot the system to see them.
Upgrading To S-Cz9.3.0 From Previous Releases
When upgrading from a previous release to S-Cz9.3.0, your encryption entitlements carry forward and you do not need to install new license keys.