Small Footprint VNF

Oracle® Enterprise Session Border Controller (E-SBC) customers who want to reduce the size of their SBC deployment footprints or who may not need the maximum number of cores and amount of memory available can deploy the SBC virtually with fewer cores and memory requirements. For smaller scale deployments, the VNF software supports a minimum deployment of 2 virtual cores, 4GB RAM, and 20GB storage. In this way, Oracle provides a flexible solution that you can tailor to your requirements.

RTP TTL

The Oracle® Enterprise Session Border Controller (E-SBC) allows you to set, on a per media-policy basis, the number of hops RTP packets can traverse before they should be dropped.

See "Realms and Nested Realms" in the ACLI Configuration Guide.

Upgrade Information

The Oracle® Enterprise Session Border Controller (E-SBC) includes the check-upgrade-readiness ACLI command, which presents system information arranged to clearly tell you if you need to perform any tasks before you upgrade.

See "Upgrading Software" in the Platform Preparation and Installation Guide.

Mellanox® Support

SCZ8.2.0 supports interface card from Mellanox® for VNF deployments. Refer to "Platform Support" in these Release Notes for details on specific cards, drivers, interface modes, and functional support.

Simultaneous DTMF and Audio Payload Mapping

In addition to enabling audio payload type mapping for AMR and AMR-WB and enabling EVS AMR-WB IO payload type mapping, the audio-payload-type-mapping option, within the media-manager, configures the Oracle® Enterprise Session Border Controller (E-SBC) to support simultaneous payload type mapping for audio and DTMF RFC-2833 for AMR, AMR -WB, and EVS in AMR wideband IO mode. Payload type mapping requires fully compatible SDP, with the exception of the payload type number. Simultaneous audio and DTMF RFC 2833 payload type mapping also requires that the payload type numbers for audio and DTMF be different.

Software-Based Transcoding Support

SCZ8.2.0 adds support for software transcoding of the following codecs for VNF deployments.

• EVS (Service Provider, only)
• OPUS
• iLBC

Refer to "Transcoding Support" in these Release Notes for complete lists of transcoding codecs, based on Acme Packet and VNF platforms.

REST API

The Oracle® Enterprise Session Border Controller (E-SBC) includes a REST API that accepts Create, Read, Update, and Delete ( CRUD) operations over HTTPS. For a description of the supported REST API endpoints, see the REST API documentation.

OpenStack Heat Template

The following new parameters are available for configuration in the environmental file.

• diskPartitions—Specify the percentage of disk space that will be allocated for each partition.
• applyBaseConfiguration—Enable or disable the base configuration, which is suitable for minimal Standalone or HA-pair functionality.
• configuration—If applyBaseConfiguration is set to true, specify the input parameters for the base configuration. Sub-parameters include:
  • dosCores—Specify the number of CPU cores dedicated for denial-of-service protection.
  • forwardingCores—Specify the number of CPU cores dedicated for forwarding frames.
  • transcodingCores—Specify the number of CPU cores dedicated for transcoding media.
  • ntpServer1—Specify the IP address of an NTP server to use for time synchronization.
  • ntpServer2—Specify the IP address of an NTP server to use for time synchronization.
  • snmpCommunityName—Specify the name of the SNMPv2 community to use for SNMP management.
  • snmpIpAddress—Specify the IP address to add to the SNMPv2 community for SNMP management.
• wancom0VLAN—(Only available on Pike and newer) Specify the bootparameter VLAN value for the wancom0 interface.
• vnicBinding—Specify the virtual NIC binding type for each media interface.

For a list of all supported parameters, see the The Platform Preparation and Installation Guide.

Secure RADIUS Connection

See "Secure RADIUS Connection" in the Administrative Security Guide.

Product and Entitlement Provisioning from the Heat template

This release supports provisioning both the product and any of its entitlements when deploying virtual machines from a Heat template.

For more details, see the "Virtual Machine Platforms" chapter in The Platform Preparation and Installation Guide. For examples, see the README file located in the Heat Orchestration Template .tar.gz file.

Performance Enhancements