ABSTRACT
This chapter (RFCs 6341, 7245, 7865, and 7866) describes media session recording. Session recording is a critical requirement in many business communications environments for XCON conferences, including call centers and financial trading floors. In some of these environments, all calls must be recorded for regulatory and compliance reasons. In others, calls may be recorded for quality control or business analytics. Recording is typically performed by sending a copy of the session media to the recording devices and the session initiation protocol (SIP) with extensions chosen for communications between the session recording server (SRS) and the devices. This chapter specifies requirements for extensions to SIP that will manage delivery of RTP media to a recording device as specified in RFC 6341 (see Section 10.1). This is referred to as SIP-based Media Recording (SIPREC). This chapter also describes architectures for deploying session recording solutions in an environment that is based on SIP, specified in RFC 7245 (see Section 10.2). The meta-data model (RFC 7865 – see Section 10.3), as viewed by the session recording server (SRS) and the recording meta-data format, is described here. Finally, this chapter, as specified in RFC 7866 (see Section 10.4), specifies the use of the SIP, the session description protocol (SDP), and the real-time transport protocol (RTP) for delivering real-time media and meta-data from a Communication Session (CS) to a recording device. The “session recording protocol” specifies the use of SIP, SDP, and RTP to establish a Recording Session (RS) between the Session Recording Client (SRC), which is on the path of the CS, and an SRS at the recording device. This specification considers only active recording, where the SRC purposefully streams media to an SRS, and all participating user agents (UAs) are notified of the recording. Passive recording, where a recording device detects media directly from the network (e.g., using port-mirroring techniques), is outside the scope of this chapter. In addition, lawful intercept is also outside the scope of this chapter. Note that media resource control protocol (MRCP) (RFC 6787), described in Chapter 14, also has the ability for media session recording functions in addition to other capabilities. However, media recording described here uses the SIP protocol even at the application level, like that of the CFW (RFC 6230 – see Chapter 8) and Media Resource Broker (MRB) (RFC 6917 – see Chapter 11), without creating new ones, providing synergy for the XCON conference system, because the focus also uses the same SIP protocol for the session (or call) control protocol (RFC 3261 – also see Section 1.2) and XCON notification service (RFC 6502 – see Chapter 7).
