2 New Features
The S-Cz9.3.0 release of the Oracle® Enterprise Session Border Controller (ESBC) software supports the following new features.
Note:
System session capacity and performance are subject to variations between various use cases and major software releases.Preconditions and Multiple Early Dialog
You can configure the ESBC with the enhancement described here to overcome limitations in Multiple Early Dialogs (MED) call flows. To support the use of MED with preconditions, the ESBC implements preconditions processing at the dialog level.
See the Preconditions and Multiple Early Dialog section in the SIP Signaling Services chapter of the ACLI Configuration Guide for detailed information.
Note:
See the Caveats and Limitations Chapter of the S-Cz9.3.0 Known Issues and Caveats Guide for functional limitations of this feature that apply to this software release.Reject Non-Emergency Traffic using Emergency DSCP
You can configure the ESBC to reject traffic that uses emergency DSCP codes to designate itself as emergency traffic. This function applies to calls from both registered and unregistered endpoints and for both UDP and TCP traffic.
See the Reject Non-Emergency Traffic using Emergency DSCP section in the SIP Signaling Services chapter of the ACLI Configuration Guide for detailed information.
Realm Based SIP Method Statistics for SNMP
You can configure the ESBC to generate SIP method statistics for SUBSCRIBE, NOTIFY, and MESSAGE requests on a realm basis by enabling the snmp-sipmethod-stats parameter in the applicable realm-config. These statistics are only available when you perform an SNMP WALK, GET or SNMPGETNEXT from you SNMP manager.
See the Realm Based SIP Method Statistics section in the SNMP Configuration chapter of the MIB Guide for detailed information.
Supporting IOI AVPs for Unregistered Endpoints
You can configure the ESBC to include the Originating-IOI and Terminating-IOI AVPs within ACRs and Diameter based CDRs for unregistered endpoints in addition to registered endpoints. Support for registered endpoints is available without special configuration. For unregistered endpoints, you enable the ioi-for-unregistered option within the account-config element.
See the Supporting IOI AVPs for Unregistered Endpoints section in the Diameter Accounting chapter of the Accounting Guide for detailed information.
Suppressing Re-INVITEs for Call Hold/Resume Dialogs
You can configure the ESBC to suppress Re-INVITEs for Call Hold/Resume dialogs and REPLACES dialogs to reduce excess signaling traffic. From the perspective of the ESBC, a re-INVITE on one side of a session does not necessarily need to be forwarded to other side. When the ESBC receives a Re-INVITE that triggers, for example, a call hold, it can suppress that message from being sent out the egress and handle the transaction locally, between itself and the endstation that sent the re-INVITE. For this feature to work correctly, the applicable Hold and Resume Re-INVITEs must include SDP.
See the Suppressing Re-INVITEs for Call Hold/Resume Dialogs section in the SIP Signaling chapter of the ACLI Configuration Guide for detailed information.
Support of Adaptive HNT for TCP endpoints
The ESBC supports Adaptive Host NAT Traversal (AHNT) over TCP in addition to UDP. TCP AHNT configuration and behavior is largely the same as for UDP. You use sip-interface parameters that are equivalent to, but separate from the UDP parameters to configure Adaptive HNT for TCP.
See the Adaptive HNT over TCP section in the SIP Signaling chapter of the ACLI Configuration Guide for detailed information.
Incoming Request Validation
You can configure the ESBC to validate a specific set of requests and respond to these requests with the behaviors presented here when you enable the ntt-request-valid SPL option. This validation works using Surrogate Register SPL options within SurrogateRegister.spl and in conjunction with other NTT Message Converter SPL options. This processing compares values within the request, and only processes the call if they match. If they do not match, the ESBC replies with responses specific to each scenario.
See the Request Validation section in the SBC Processing Language (SPL) chapter of the ACLI Configuration Guide for detailed information.
Mapping SIP to HTTP Parameters
You can configure the ESBC with static mapping of signaling information to and from SIP INVITEs and HTTP requests or responses. This mapping provides a means of conveying SIP header and parameter information, including ICID information within HTTP headers and vice-versa. The HTTP exchanges can be during authentication and verification procedures. This feature applies to both ATIS and 3GPP modes.
See the HTTP Header Manipulation section in the STIR/SHAKEN chapter of the ACLI Configuration Guide for detailed information.
Note:
See the Caveats and Limitations Chapter of the S-Cz9.3.0 Known Issues and Caveats Guide for functional limitations of this feature that apply to this software release.Suppression of Subsequent 18x Messages
You can configure the ESBC to suppress some provisional 180 or 183 messages from a UAS within call-setup transactions to reduce excess signaling traffic. The system forwards only the first 180 or 183 and suppresses all of the subsequent 180 and 183 messages until it receives a 200 OK from the UAC. You configure this feature using an SPL option within the SuppressAdditionalProvisional SPL.
See the Suppression of Subsequent 18x Messages section in the SIP Signaling chapter of the ACLI Configuration Guide for detailed information.
Additional STUN Candidate for RTCP
You can configure the ESBC to establish a collapsed flow between itself and any STUN endpoint by enabling the rtcp-stun parameter in the applicable ice-profile. The system uses this flow for both RTP and RTCP, collapsing this traffic from two ports. As such, this configuration only applies when you have a realm supporting STUN with rtcp-mux disabled.
See the Additional STUN Candidate for RTCP section in the Advanced Media Termination Support chapter of the ACLI Configuration Guide for detailed information.
IPv4/IPv6 MSRP Packet Trace Remote Support
You can use the ESBC remote capture feature to analyze MSRP traffic, including the TCP handshake to set up connections and support MSRP traffic as well as IPv6 traffic.
See the Packet Trace Remote section in the Monitoring Guide for detailed information.
Disabling GARP and ND for out-of-subnet Addresses
You can configure the ESBC to limit its use of Gratuitous Address Resolution Protocol (GARP) or Network Discovery (ND). Specifically, you can prevent the system from performing this function for each sip-interface that is not in the same subnet as the network-interface on which they operate. External systems typically reach these addresses through static routes or other routing configurations, making the use of GARP and ND unnecessary for them.
See the Disabling GARP and ND for out-of-subnet Addresses section in the System Configuration chapter of the ACLI Configuration Guide for detailed information.
Adaptive Jitter Buffers for Transcoding Flows on vSBCs
The processing of transcoded flows on the ESBC uses an adaptive jitter buffer. This feature allows the transcoding function to adapt to changes in network conditions and packet jitter. But if necessary, the jitter buffer feature (on virtual SBC platforms only) can also be adjusted to better align to specific network conditions.
See the Adaptive Jitter Buffers for Transcoding Flows on vSBCs section in the Transcoding chapter of the ACLI Configuration Guide for detailed information.
Critical Memory Switchover
You can configure a high availability deployment of the ESBC to switch to the standby when the system detects memory utilization that is persistently high. Over-utilization of memory can trigger a system crash. This function reduces the risk of those crashes.
See the Critical Memory Switchover section in the System Configuration chapter of the ACLI Configuration Guide for detailed information.
Scheduled External Configuration Backup
You can configure the ESBC to automatically back up its current backup configuration file dataDoc.gz, which is available at /code/gzConfig/, to an external SFTP server. This feature enhances system reliability by maintaining an off-system copy of your configuration and by making restoration processes faster.
See the Scheduled External Configuration Backup section in the System Configuration chapter of the ACLI Configuration Guide for detailed information.
Oracle Enterprise Session Router Platform Support
The Acme Packet 4900 supports the Oracle Enterprise Session Router. This support begins with S-Cz9.3.0p2.
ESXI Version Support
The ESBC supports operation with ESXI version 8. This support begins with S-Cz9.3.0p2.
See the Supported Private Virtual Infrastructures and Public Clouds section in the Introduction chapter of these Release Notes for confirmation of this feature.
TACACS ARG Mode
When sending the Authorization query to the TACACS+ server, by default the ESBC sends everything typed at the ACLI in the cmd parameter. For commands, this includes the command plus all of its arguments (for example, cmd=show interfaces brief). For configurations, this includes the full path of the configuration element plus its attributes and values (for example, cmd=configure terminal security authentication type tacacs). In the TACACS+ query, the cmd-arg parameter is set to <cr>.
This support begins with S-Cz9.3.0p2.
See the Supported Private Virtual Infrastructures and Public Clouds section in the Introduction chapter of these ACLI Configuration Guide for detailed information about this feature.