SIPREC Support

Imagicle Call Recording supports several native recording methods, which are described in the relevant sections, based on the Calling Platform in place.

Imagicle also supports SIPREC recording method, which can be enabled in any legacy on-prem or Cloud-based Calling Platform integrating SIPREC standardized mechanism defined mainly in RFC 7866 for recording SIP-based telephony communication sessions.

SIPREC works by replicating a live SIP session from the communication path to the Imagicle Recorder, without interfering with the original call.

Some PBXs natively support SIPREC and they can directly route recording streams through a SIP session.

In other scenarios, SIPREC recording streams are typically generated by a Media Gateway/Proxy or a SBC in charge of routing calls to the PSTN, allowing to record any external inbound/outbound call passing through it. See below an on-prem architecture sample:

If the Imagicle instance is deployed in the Cloud, Imagicle supports both OTT (Internet) and private peering to route SIPREC recording streams from source to UCX Cloud Suite. If OTT peering is adopted, SIPREC secure sessions are terminated on the Imagicle Public SBC available within the customer’s Region. If private peering is adopted, then both SIP session and RTP streams are routed through a supported peering method. See below Cloud architecture sample:

Regardless the source, a separate SIP session is established with Imagicle Call Recording, distinct from the original call. RTP or SRTP media is forked (duplicated) from the original RTP streams and sent to Imagicle, together with call-related metadata (participants, call IDs, timestamps, directions, etc.) using SDP extensions.

SIPREC is network-based and passive from the endpoint perspective: endpoints are unaware that recording is taking place.