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.
• Default levels for scalability are set to ensure appropriate throttling based on platform capacity factors such as hypervisor type, number and role of CPU cores, available host memory and I/O bandwidth. In some scenarios, the defaults may not be appropriate and throttling may occur at lower or higher call rates than expected. Please contact Oracle Technical Support for details on how to override the default throttles, if 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 not support VLANs over SR-IOV interfaces.
• 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
• RTCP generation for G.711 or G.729
• 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.

Local Media Playback feature is incompatible with any transcoding functionality.

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

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 3900 does not support the MSRP feature set.

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

Acme Packet 3900 IPSec Limitations

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

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

Diameter Server Timeout during Save/Activate

When saving and activating a configuration, the E-SBC may disconnect from an external policy server. The cause of this disconnect is based on SCTP HEARTBEAT value configured on the Diameter policy server.

Solution: You can work around this issue by setting the policy server's SCTP HEARTBEAT to a value greater than 750ms, which exceeds the amount of time it takes to perform a save/activate on the E-SBC.