About SIPREC

MBG's SIPREC service allows a CRE, referred to in RFC 7866 as a SIP Recording Server (SRS), to record audio calls to or from SIP devices connected to MBG. MBG provides the B2BUA Recording Model as described in RFC 7866 and is, oddly, referred to as an SRC (Session Recording Client).

SIPREC does not use TLS mutual authenticated connections, the CRE does not initiate connections to SRC. SRC is configured with the CRE addresses (see below) and it is the SRC that connects to the CRE.

SIPREC message flows follow the original SIP message flows through MBG. However, only call setup/teardown is shared. This takes the form of a SIP INVITE message, sent by SRC to CRE and a response to that INVITE from the CRE that will contain SDP (requesting a tap) or no SDP (not requesting a tap). Additional information about the call is sent from the SRC to the CRE in the form of extra "metadata" attached to the SIP messages.

SIPREC is supported for:
Note:

To configure MBG for a call recording deployment with SIPREC, follow these steps:

  1. Review the call recording port ranges.
  2. Enable SIP TCP or TLS transport.
  3. Restrict codecs for SIP if required by your CRE.
  4. Configure your SIP devices.
  5. Add your SIP Recording Server. See Configure SIPRECfor details.

To review the list of CREs actively recording calls, see Call recording status.