Preserve SIPREC with SIP REFER Header

When the Oracle® Enterprise Session Border Controller (E-SBC) generates a new INVITE as part of terminating a SIP REFER, the E-SBC evaluates the SIPREC configuration of the realms and session agents involved in the new call leg and responds accordingly. The REFER and Transfer mechanism automatically preserves the UCID, XUCID, GUID, GUCID, and UUI in the metadata, and can forward this information to the Session Recording Server. The E-SBC can Start, Stop, Pause, and Resume SIPREC sessions in response to any re-INVITE, UPDATE, new INVITE, REFER, or specified SIP Response Message.

The E-SBC can establish a new session or update the existing session with the SIPREC server in the following ways.

• When the A-B call leg SA-realm-sipinterface is configured for SIPREC, and the B-C call leg SA-realm-sipinterface is not configured for SIPREC, the E-SBC sends metadata to the Session Recording Server to stop the recording on the sessionID associated with the original call.
• When both the A-B call leg and the B-C call leg have the same SIPREC configuration on their SA-realm-sipinterface, the E-SBC sends metadata to the Session Recording Server to stop Party A participation and start Party C participation within the same sessionID.
• When the A-B and B-C call legs have a different SIPREC configurations on their SA-realm-sipinterface, the E-SBC sends metadata to the A-B call leg Session Recording Server to stop the current recording session and sends metadata to the B-C call leg Session Recording Server to start a new recording session with a new sessionID.