Load Balancing

The Oracle® Enterprise Session Border Controller supports recording server load balancing across members of a session recording group using the following strategies:

Note:

SRS groups support “round-robin” and “hunt” strategies only.

[Round-robin]: The Oracle® Enterprise Session Border Controller remembers the last SRS that was used. Each new recording session selects the next SRS in the session recording group. When simultaneous-recording-servers is greater than 1, the next n recording servers are selected from the session recording group.

[hunt]: The Oracle® Enterprise Session Border Controller successively attempts to contact SRSs in the session recording group until a successful recording dialog is established with the SRS, starting from the first SRS in the session recording group. The Oracle® Enterprise Session Border Controller attempts to contact each SRS in the session reporting group once. When contact is exhausted, the recording device is considered failed. A SIP failure (response greater than 399, timeout or TCP setup failure) causes the Oracle® Enterprise Session Border Controller to attempt the next possible SRS. When simultaneous-recording-servers is greater than 1, the Oracle® Enterprise Session Border Controller attempts to establish n recording devices in a hunting fashion.