1. Release Notes
  2. Caveats and Known Issues
  3. Caveats and Limitations

Caveats and Limitations

The following information lists and describes the caveats and limitations for this release. Oracle updates this Release Notes document to distribute issue status changes. Check the latest revisions of this document to stay informed about these issues.

Media Policing

The Acme Packet 1100, 3900 and 4600 as well as all software-only deployments do not support any Media Policing configuration.

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 you use setup entitlements to set the capacity for a transcode codec, the system may or may not require a reboot.

  • When a transcode codec is provisioned with a license key, a capacity change requires a reboot to take effect.
  • When a transcode codec is self-provisioned, a capacity change takes effect without a reboot.

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.
  • When operating as a VNF deployed in an HA configuration, the OCSBC does not support IPSec.
  • MSRP support for VNF requires a minimum of 16GB of RAM.
  • The system supports only KVM and VMWare for virtual MSRP, and it supports only the 4 core SSFD model.
  • 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.
  • When deploying the E-SBC over VMware and using PV interface mode, the number of forwarding cores you may configure is limited to 2, 4, or 8 cores.
  • Virtual LAN (VLAN) tagging is not supported when deploying the OCESBC over the Hyper-V platform.

Virtual Network Function (VNF) Limitations

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

  • FAX Detection
  • T.38 FAX IWF
  • RTCP detection
  • Remote Packet Trace
  • ARIA Cipher
  • IPSec functionality not available in VNF deployments of this release:
    • IKEv1
    • Authentication header (AH)
    • The AES-XCBC authentication algorithm
    • Dynamic reconfiguration of security-associations
    • Hitless HA failover of IPSec connections.

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

The following media-related features are not supported in pooled transcoding scenarios:

  • Lawful intercept

  • 2833 IWF

  • Fax scenarios

  • RTCP generation for transcoded calls

  • OPUS/SILK codecs

  • SRTP and Transcoding on the same call

  • Asymmetric DPT in SRVCC call flows

  • Media hairpinning

  • QoS reporting for transcoded calls

  • Multiple SDP answers to a single offer

  • PRACK Interworking

  • Asymmetric Preconditions

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 reboot.

SRTP Caveats

The ARIA cipher is not supported by virtual machine deployments.

Packet Trace

  • VNF deployments do not support the packet-trace remote command.
  • The Acme Packet 3900 does not support the packet-trace remote command.
  • The Acme Packet 1100 does not support the packet-trace remote command.
  • Output from the packet-trace local command on hardware platforms running this software version may display invalid MAC addresses for signaling packets.

Trace Tools

You may only use one of these trace tools at a time:
  • packet-trace command
  • The communications-monitor as an embedded probe with the Enterprise Operations Monitor
  • SIP Monitor and Trace

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

These platforms do not support the MSRP feature set:
  • Acme Packet 3900
  • Acme Packet 1100
When running media over TCP (e.g., MSRP, RTP) on the same interface as SIP signaling, TCP port allocation between media and signaling may be incompatible.
  • Workaround: Set the sip-port, address parameter to a different address than where media traffic is sent/received, the steering-pool, ip-address value.

Real Time Configuration Issues

In this version of the E-SBC, 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

High Availability (HA) redundancy is unsuccessful when you create the first SIP interface, or the first time you configure the Session Recording Server on theOracle® Enterprise Session Border Controller (E-SBC). Oracle recommends that you perform the following work around during a maintenance window.
  1. Create the SIP interface or Session Recording Server on the primary E-SBC, and save and activate the configuration.
  2. Reboot both the Primary and the Secondary.

Acme Packet 3900 IPSec Limitations

The following IPSec functions are not available for the Acme Packet 3900 in this release.

  • IKEv1
  • Authentication header (AH)
  • The AES-XCBC authentication algorithm
  • Dynamic reconfiguration of security-associations
  • Hitless HA failover of IPSec connections.

Dead Peer Detection

When running on the Acme Packet 6100, the E-SBC's dead peer detection does not work with IPv4.

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.