Cluster Membership

• Each SBC may be a member of only one cluster, and a cluster may be associated with only one SLB redundant pair.

Protocol Support

• The Oracle Communications Session Border Controller's FTP Server is deprecated. Only SFTP server services are supported.
• When handling TCP calls through load-balanced clusters, the SBC, in some scenarios, attempts to initiate the TCP handshake using the ephemeral port established for SIP services over the SBC-SLB tunnel instead of the end station's port. These calls fail because the SBC cannot utilize the tunnel properly. Example scenarios include:

  • After an HA SBC pair that is a member of a cluster fails over, the new active contains correct registrations, but not end station sockets. TCP calls to those end stations fail. When these end stations refresh their registrations, these calls can succeed.
  • TCP calls originating from the core to an SBC that is a member of a cluster, then the SLB, then toward end stations that are not registered at the SBC fail. The target end stations must register for these calls to succeed.

Fragmented Ping Support

• The Oracle Communications Session Border Controller does not respond to inbound fragmented ping packets.

Inactivity Age-out of Trusted Endpoints

• The inactivity age-out functionality for trusted endpoints is not yet implemented.

Physical Interface RTC Support

• After changing any Physical Interface configuration, a system reboot is required.
• Output from the packet trace local feature on hardware platforms running this software version may display invalid MAC addresses for signaling packets.

Command Line Interface Discrepancies

• The SLB's tunnel-config element includes a tls-profile parameter. This parameter is not functional.
• A platform running as a Subscriber-Aware Load Balancer (SLB) can still configure Session Border Controllers (SBC)-specific group-names.