U‑Capture and SIPREC
This topic provides general architecture details for the Uniphore SIPREC integration. For system deployment details specific to a customer environment please refer to the customer’s Solution Design Document from Uniphore.
Integration Overview
SIPREC is an open SIP-based protocol for call recording. The standard is defined by the Internet Engineering Task Force (IETF) and is supported by many platforms, though each may differ slightly in the supported features and required configuration described later in this document.
SIPREC requires two parties to facilitate call recording – a Session Recording Client (SRC), which is the role performed by a telephony platform or Session Border Controller (SBC), and a Session Recording Server (SRS), in this case the U‑Capture Collector.
The SRC establishes the session with the SRS via a SIP INVITE, and sends replicated media towards the SRS, providing an active call recording integration.
Call metadata, such as participant information (called number, other party name, etc), is delivered to the Collector from the SRC in XML format.
SIPREC Call Flow
The RTP Collector provides multi-NIC capture of audio data and works in sync with the SIP RAM (Recording Acquisition Module) – the SIP RAM manages the SIP dialog and the RTP Collector owns the RTP session.
SIP message exchange between SRC and SRS.
SIP RAM requests RTP Collector session.
RTP Collector provides endpoint for audio delivery.
Audio sent from SRC to RTP Collector for recording.
 |
Resiliency
The SIPREC integration allows for Parallel mode (2N) resiliency (two Primary Collectors). In this configuration there are two Primary Collectors in a Collector Service Group, each recording the same calls and having the same configuration. In the event of a critical error (failure) of a Collector, the other Collector will simply continue to capture data without loss of recordings.
