Session Recording Group

The Oracle® Enterprise Session Border Controller uses the session-recording-group attribute under the session-router object in the ACLI to set high availability (HA) for 3rd party call recorders. Using this object, you can define a collection of one or more SRSs. The Oracle® Enterprise Session Border Controller utilizes SIP’s transport mechanism and keeps track of statistics on each SRS to manage the distribution of traffic and load balancing. (For more information on Oracle® Enterprise Session Border Controller load balancing in session recording groups, see Load Balancing). When multiple SRSs are in a session recording group, the Oracle® Enterprise Session Border Controller uses heuristics to intelligently route the recording dialog to one or more SRSs utilizing the selection strategy.

The simultaneous-recording-servers configuration attribute controls the number of simultaneous SIP dialogs that the Oracle® Enterprise Session Border Controller establishes to the SRSs in the session recording group per communication session. For instance, if a session recording group contains 3 SRSs, and simultaneous-recording-servers is set to 2, the recording agent initiates a SIP INVITE to the next two SRSs based on the session recording group strategy. In this way, duplicative recording sessions are instantiated, allowing for recording redundancy in multiple SRSs or within a session recording group.

Note:

The Oracle® Enterprise Session Border Controller streams media to all SRSs. Each SRS chooses whether or not to ignore the media by returning a recvonly(receive only) media line. This permits an SRS to select specific media to record in the recording session, as well as determine whether or not to record the media.

The number of simultaneous recording servers does not dictate the number of recording devices required to be active for a communication session. If two SRSs exist in a session recording group and simultaneous-recording-servers is set to 2, if at least one recording device to any of the servers completes, the recording server is treated as being established.