2 New Features
The S-Cz10.0.0 release of the Oracle Communications Session Border Controller (SBC) software supports the following new features.
Note:
System session capacity and performance are subject to variations between various use cases and major software releases.Note:
TEMPLATE - See the Caveats and Limitations Chapter of the S-Cz10.0.0 Known Issues and Caveats Guide for functional limitations of this feature that apply to this software release.Expanded DNS Functions and Tools
With this release, the SBC allows you to fetch additional DNS statistics and extract DNS resolution information using the show dns command on the ACLI. In addition to basic DNS statistics, using the ACLI show dns command, new arguments provide more specific statistics, resolutions and information.
See the DNS Statistics section in the ? chapter of the Maintenance and Troubleshooting Guide for detailed information.
OCOM Filtering
With this release, you can configure the SBC to filter the data it sends to a monitor collector to simplify your system monitoring and troubleshooting. You do this by configuring one or more filter-profile elements within the comm-monitor elements.
See the Filtering Data for Operations Monitor section in the ? chapter of the Maintenance and Troubleshooting Guide for detailed information. Additional supporting information is available in the ACLI Reference Guide.
Sending SIP Pings from Multiple Realms to Global Session Agents
With this release, you can configure the SBC to send SIP OPTION pings to multiple physical agents through multiple realms using a global session-agent (SA). This feature monitors status of global SA targets on the system, supporting applicable deployments including UCaaS topologies that include multiple tenancies. You enable this feature by setting the egress-realm-id attribute of a session-agent to multiple realm names.
See the SIP Pings from Multiple Realms to Global SAs section in the "Session Routing and Load Balancing" chapter of the ACLI Configuration Guide for detailed information.
Enhancement to Early Media Gating Functionality
With this release, you can configure the SBC to bypass gating and forward early media to untrusted domains. This feature resolves early media problems for situations including PEM gating when an UPDATE goes from the trusted side towards the untrusted side and the system prevents an early media announcement to play through the subsequent 18x. In this case, the default SBC behavior would be to gate the early media. To configure this feature, you enable the pass-pem-in-update option on the ingress sip-interface.
See the Bypassing Early Media Gating section in the SIP chapter of the ACLI Configuration Guide for detailed information.
STIR/SHAKEN MAN Compliance
With this release, you can configure the SBC to include compliance behaviors for the Number Authentication Mechanism 2.0 operations standards by enabling the man-compliance option in the sti-config. The Number Authentication Mechanism 2.0 standard, often referenced as MAN 2, is a French standard for CLI anti-spoofing. It was developed via a collaborative effort between the French Telecoms Federation (that unifies telco operators in France) along with ARCEP (Regulatory Authority) and the APNF (French association of standardization platforms for inter-operator flows).
In addition to this support, this release extends upon STIR/SHAKEN support to include:
- Accepting Non-Standard verstat
- Bypass STI-AS Signature and STI-VS Verification Requests
- Media Policy within the http-server element
- TLS Session Key Logging
- Remove the verstat from Incoming Requests
- Extract verifyResults Content from div Passports for 3GPP
- Managing Curl within HTTP Server Interactions
See the Number Authentication Mechanism Standards Compliance Features section in the STIR/SHAKEN chapter of the ACLI Configuration Guide for detailed information on STIR/SHAKEN MAN Compliance. Additional feature support is also documentation in the STIR/SHAKEN chapter of the ACLI Configuration Guide.
TACACS+ support by SBC REST API
This release of the SBC adds support for TACACS+ users to access the SBC from the REST interface, restricting their actions via TACACS+ authorization and recording those actions with TACACS+ accounting.
This functionality is documented in the ACLI Configuration Guide and ACLI Reference Guide including:
- In the SBC Configuration Guide, the "User Accounts" > "TACACS+ Authorization" section has a new section called "TACACS+ Authorization for the REST API".
- In the REST API documentation, a link to the previous topic is added to the Authenticate topic.
- The authentication reference topic in the ACLI Reference Guide is updated to add the rest-authorization-accounting attribute.
Egress Enhancement to the Separate Clock Rates on Audio and 2833 Feature
Release 9.0.0p3 introduced a feature that provided support for different codec and telephone-event rates in the SDP. This feature allows you to configure the SBC to support flows when using different clock rates for audio and telephone events. This allows the SBC to adapt to environments that do not follow the recommendation for the same rates in RFC 4733. This feature, however, was limited to ingress interfaces. This release of the SBC adds this same support for egress interfaces.See the Separate Clock Rates for Audio and Telephone Events section in the Transcoding chapter of the ACLI Configuration Guide for detailed information.
Software FAX Transcoding on virtual SBC
This release of the SBC removes the limitation that excluded software FAX transcoding on virtual SBCs, including those running on AMD CPUs. Verification of the removal of this limitation is provided in the Known Issues and Caveats Guide.
Expanded Transcoding Support for virtual SBC
This release of the SBC removes the limitation that excluded transcoding on some virtual SBCs, including those running on AMD CPUs. Verification of the removal of this limitation is provided in the Known Issues and Caveats Guide.
Resource Monitoring
In addition to specific function and operation monitoring, the SBC provides you with the ability to monitor overall system resource utilization to protect against undesirable behavior caused by the cumulative utilization of resources. You configure this feature using the resource-monitoring-profile element. This monitoring function operates independently on HA pairs, protecting the standby from resource over utilization independently from the active.
See the System Resource Monitoring section in the System chapter of the ACLI Configuration Guide for detailed information. SNMP information related to this feature is also available in the MIB Guide
System CPU Load Limiting
- Begins rejecting SIP requests when the CPU reaches its throttling threshold
- Rejects all SIP requests when the CPU reaches its maximum utilization
See the SMP-Aware Task Load Limiting section in the System Management chapter of the Maintenance and Troubleshooting Guide for detailed information.
Monitoring Wancom1 and Wancom2 Using SNMP
With this release, you can configure the SBC to trigger alarms and traps when your HA wancom interfaces, including wancom1 and/or wancom2, go down. This allows you to more quickly recognize disruptions and re-establish your HA deployment's functionality.
See the Alarms and Traps for Wancom1 and 2 Interfaces section in the High Availability Notes chapter of the ACLI Configuration Guide for detailed information.
Additional Commands in Show support-info
With this release, the SBC includes additional commands in its output when you run the show support-info command.
See the Included Data section in the Fault Management chapter of the Maintenance and Troubleshooting Guide for a complete list of the commands displayed in the show support-info output.
Archiving support-info and Logfiles
With this release, the SBC, you can configure the SBC to include show support-info and Log Files with using the same mechanism is uses to archive configuration file backups. The SBC can also raises an alarm and issue a simultaneous SNMP trap to notify you each time access to a push-receiver fails.
See the Scheduled External Backups section in the System chapter of the ACLI Configuration Guide for detailed information.
Re-Registering Surrogate-agents After Switchover over TCP
You can configure the SBC to re-register all of its surrogate agents immediately after an HA switchover. This behavior is valid for all surrogate agent, regardless of transport, but is limited to 10,000 surrogate agent registrations to prevent a registration avalanche. If the system has more than 10,000 surrogate agent registrations to perform, the remaining agents re-register normally.
See the Surrogate Agents Re-Register after Switchover section in the SIP chapter of the ACLI Configuration Guide for detailed information.
Removal of the AMR-NB Entitlement
You can now configure the SBC to use this codec without setting an entitlement, and there is no longer a licensed capacity limit. When observed from HDR, the REST API or SNMP, the limit displays as 0, which means no limit.
Account Servers over IPv6
You can configure the SBC to use IPv6 over the RF interface in addition to IPv4 to support Diameter Accounting Servers. This allows you to support ACR exchanges between the system and CRF servers using IPv6. In addition, you can configure your account-server elements to perform A and AAAA DNS lookups for servers using IPv4 or IPv6 addressing.
See the Diameter Accounting chapter of the Accounting Guide and the ACLI Reference Guide for information confirming this feature.
Intel 800 Series Support - IAVF
With this release, Oracle has extended upon the support available on the SBC.
See the Requirements for Machines on Private Virtual Infrastructures section in the Introduction Chapter of these Release Notes to see details about the platforms and applications wherein you can use the Intel 800 Series network interfaces.
Acme Packet 6400 Platform
With release S-Cz10.0.0p1, you can deploy the SBC on the Acme Packet 6400 platform.
Note:
Make sure your software image is S-Cz10.0.0p1 or later.See the Acme Packet 6400 Appendix in the Platform Preparation and Installation Guide for information about deploying on this platform. Also see the Acme Packet 6400 Installation Guide for detailed physical installation information about this hardware platform.