Oracle SBC Load Balancing for Genesys Engage

The capacity of Oracle SBC can reach tens of thousands of sessions. This is more concurrent calls than an individual Verint WFO IP Recorder can process. For this reason you must configure Oracle SBC such that a group of Recorders receives even load distribution.

To set up SRR Load Balancing, complete the following tasks, all on the Oracle SBC side (please refer to the Oracle SBC documentation for detailed instructions):

Create one Session Agent (each associated with a realm) for every Recorder. Each Session Agent must point to the SIP Trunk IP address on the switch.
Assign a Session Agent Group (SAG) to the Session Agents associated with the Recorders/call recording realms are assigned to a SAG.
Enable Load Balancing for the SAG. Set one of the following Load Balancing options:
- Least Busy—recommended to evenly distribute the load when all Recorders have the same capacity.
- Proportional—recommended when the Recorders have different capacities.
Set up a Realm for each Recorder. The Realm definition includes a SIP Interface (that is, the IP address where the SIP Trunk terminates on the SBC).
Create a CRS for each Recorder, and assign the CRSs to a corresponding Realm. The CRS defines the IP address of the Recorder server, identifying for the SBC where it should send the replicated SIP/RTP traffic.

As the SBC load balances new calls across these Realms, the call recording servers will get the replicated packets in a load-balanced manner.

To add a third primary CRS to this configuration for inbound calls, add another CRS object and set its secondary address as the as that of the server used for failover. Add a realm for this CRS (including its associated SIP Interface and Session Agent). Add the Session Agent of the new CRS to the SAG, in order to include this CRS in the Load Balancing group.

For recording both inbound and outbound calls, you should replicate the inbound configuration described above on the outbound side of the SBC (that is, the side that terminates the SIP Trunks from the service provider). Note that in order to provide load balancing for outbound calls, multiple SIP Trunks to the service provider are required, one for each CRS.

If you configure Load Balancing but do not configure Redundancy, a failed Recorder will result in the loss of recordings (that is, calls will not be redistributed across active reocrders). To ensure that all calls are recorded as desired, configure Redundancy in addition to Load Balancing.