Static Flows and Media Policing

The Acme Packet 1100, 3900, and 4600 as well as all software-only deployments do not support the average-rate-limit parameter in a static-flow configuration when the profile applies to static flows.

Overlap of Data Between Widgets During Periods of Inactivity

When the dashboard is left open for 20 minutes or more without performing any action other than keeping the session alive on the WebGUI, the data between different widgets may overlap occasionally. Workaround: Refresh the page to resolve this issue.

New Keys Required for High Availability

If you replace a peer in HA from a system running software prior to S-Cz9.1.0p9 to this version or higher, the old keys become irrelevant resulting in SFTP failures using the old keys on the new peer. High Availability collect operations fail unless the old keys are manually deleted on the active peer. This situation is rare. This issue also occurs if you copy an old configuration into any new peer.

The SBC Generates RTCP Towards the PSTN

Scenario: In a pooled transcoding configuration, the transcoding Session Border Controller (SBC) has a single realm with rtcp-policy enabled. On the MSTeams realm, rtcp-policy is enabled on the signaling SBC and rtcp-policy is disabled on the PSTN realm.

Behavior: Because rtcp-policy is enabled on the transcoding realm, the PSTN will also receive rtcp packets even though rtcp-policy is not enabled on the PSTN realm. MSTeams will receive RTCP packets, as intended.

The Web GUI Shows No Configuration Data After Clicking "View Configuration"

When you set the process level or system log level to DEBUG, the Web GUI may not display any configuration information for large configurations when you click "View Configuration".

Acquire Config and acp-tls-profile

The acquire-config process fails if your configuration includes an acp-tls-profile. The system does, however, successfully synch this profile after HA is established.

Workaround: Disable your acp-tls-profile on the active system before performing an acquire-config procedure. Re-enable this profile after aquire-config completes successfully.

VNF in HA Mode

When the SBC VNF is running in HA mode, any existing IPSec tunnels do not fail over the standby SBC.

Toggling SIP Interfaces Running TCP

You must reboot the system any time you disable, then enable an active SIP interface that is using TCP.

Provisioning Transcode Codec Session Capacities

When a transcode codec was originally provisioned in an earlier software version with a license key, a capacity change using the setup entitlements command requires a reboot to take effect.

Virtual Network Function (VNF) Caveats

The following functional caveats apply to VNF deployments of this release:

• The OVM server 3.4.2 does not support the virtual back-end required for para-virtualized (PV) networking. VIF emulated interfaces are supported but have lower performance. Consider using SR-IOV or PCI-passthru as an alternative if higher performance is required.
• To support HA failover, MAC anti-spoofing must be disabled for media interfaces on the host hypervisor/vSwitch/SR-IOV_PF.
• You may need to enable trust mode on the host PF, when using Intel X/XL7xx [i40e] NICs with SR-IOV, before you can use VLANs or HA virtual MAC on the guest VF. Refer to the Intel X710 firmware release notes for further information.
• MSRP support for VNF requires a minimum of 16GB of RAM.
• The system supports only KVM and VMWare for virtual MSRP.
• CPU load on 2-core systems may be inaccurately reported.
• IXGBE drivers that are a part of default host OS packages do no support VLANs over SR-IOV interfaces.
• Software-based transcoding on vSBCs is not supported on servers with AMD CPUs.

Virtual Network Function (VNF) Limitations

Oracle® Enterprise Session Border Controller (ESBC) functions not available in VNF deployments of this release include:

• FAX Detection
• T.38 FAX IWF
• RTCP detection
• H.323 signaling or H.323-SIP inter-working
• ARIA Cipher

Transcoding - general

Only SIP signaling is supported with transcoding.

Codec policies can be used only with realms associated with SIP signaling.

T.38 Fax Transcoding

T.38 Fax transcoding is available for G711 only at 10ms, 20ms, 30ms ptimes.

Pooled Transcoding for Fax is unsupported.

Pooled Transcoding

DTMF Interworking

RFC 2833 interworking with H.323 is unsupported.

SIP-KPML to RFC2833 conversion is not supported for transcoded calls.

H.323 Signaling Support

If you run H.323 and SIP traffic in system, configure each protocol (SIP, H.323) in a separate realm.

Media Hairpinning

Media hairpining is not supported for hair-pin and spiral call flows involving both H.323 and SIP protocols.

Fragmented Ping Support

The Oracle® Enterprise Session Border Controller does not respond to inbound fragmented ping packets.

Physical Interface RTC Support

After changing any Physical Interface configuration, you must reboot the system.

SRTP Caveats

The ARIA cipher is not supported by virtual machine deployments.

Packet Trace

• Output from the packet-trace local command on hardware platforms running this software version may display invalid MAC addresses for signaling packets.
• The packet-trace remote command does not work with IPv6.
• If any conflicting applications are enabled, the packet-trace command displays a warning. Conflicting applications are comm-monitor, call-trace, and SIP Monitor and Trace.

Trace Tools

See the Monitoring Warning in the Call Monitoring Guide before running any monitoring service like SIPREC, Communications Operation Monitor, Packet Trace, call-trace, or SIP Monitoring and Trace (on the ESBC).

RTCP Generation

Video flows are not supported in realms where RTCP generation is enabled.

SCTP

SCTP Multihoming does not support dynamic and static ACLs configured in a realm.

SCTP must be configured to use different ports than configured TCP ports for a given interface.

MSRP Support

The Acme Packet 1100 platform does not support the MSRP feature set:

Real Time Configuration Issues

In this version of the ESBC, the realm-config element's access-control-trust-level parameter is not real-time configurable.

Workaround: Make changes to this parameter within a maintenance window.

High Availability

Offer-Less-Invite Call Flow

Call flows that have "Offer-less-invite using PRACK interworking, Transcoding, and dynamic payload" are not supported in this release.

Fragmented SIP Message Limitations

Fragmented SIP messages are intercepted but not forwarded to the X2 server if IKEv1/IPsec tunnels are configured as transport mode.

Workaround: Configure IKEv1/IPsec tunnels as "tunnel mode".

HA Deployment on Azure

HA deployments on Azure are not supported.

Graphical User Interface

When maximizing and minimizing the browser, the WEB GUI is not currently compensating correctly for display changes in tables that require scrolling. This can corrupt the display of tables in ESBC GUI management dialogs.

Simultaneous Use of Trace Tools

See "Trace Tools" caveat.

IKE

ECDSA certificates are not supported with IKEv2 configurations.

Acme Packet 3950/4900 Power Button

When running release 9.0.0 on the Acme Packet 3950 and the Acme Packet 4900, the power button may not function correctly. Upgrade to 9.0p1 or later to correct this.

Acme Packet 3950/4900 Excluded Features

Acme Packet 3950/4900 Transcoding Module Compatibility

The transcoding modules in the Acme Packet 3950 and Acme Packet 4900 are not compatible with other physical platforms.

IWF

IWF (SIP-H323) appears at the setup entitlements prompt on virtual platforms when H.323 is not supported.

SIPREC Post REFER Processing

For SIPREC calls that use the Universal Call ID SPL and also exercise SIPREC on main call flow, the ESBC does not include UUID in ACK or BYE messages post REFER processing.

Acme Packet 1100 Debug log Level

Do not set log level to DEBUG on the Acme Packet 1100.

Acme Packet Platform Monitoring Caveats

The SFP INSERTED and SFP REMOVED Alarms and corresponding traps are not supported on the following platforms:

IPSec Trunking Tunnel Caveat

The setup entitlements command allows to set a maximum of 2500 IPSec trunking tunnels. Each IPSec trunking tunnel secures signaling and media traffic for more than one SIP session. You can either set a maximum of 2500 trunking tunnels or less, while configuring the session capacity. Setting a maximum value for trunking tunnel does not limit the configured session capacity.

Playback Headers and Hairpin Calls

Playback headers are not supported in hairpin calls.