RFC 6341: Use Cases and Requirements for SIP-Based Media Recording (SIPREC)
In plain English — editorial summary, not part of the RFC
Session recording is a critical requirement in many business communications environments, such as 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. This document specifies requirements for extensions to SIP that will manage delivery of RTP media to a recording device. This is being referred to as SIP-based Media Recording. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6341
- Published
- August 2011
- Authors
- K. Rehor; L. Portman; A. Hutton; R. Jain
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- art
- Pages
- 16
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6336IANA Registry for Interactive Connectivity Establishment (ICE) OptionsObsoleted
July 2011
- RFC 6332Multicast Acquisition Report Block Type for RTP Control Protocol (RTCP) Extended Reports (XRs)Current
July 2011
- RFC 6365Terminology Used in Internationalization in the IETFCurrent
September 2011
- RFC 6366Requirements for an Internet Audio CodecCurrent
August 2011
- RFC 6376DomainKeys Identified Mail (DKIM) SignaturesUpdated
September 2011
- RFC 6377DomainKeys Identified Mail (DKIM) and Mailing ListsCurrent
September 2011
- RFC 6295RTP Payload Format for MIDICurrent
June 2011
- RFC 6416RTP Payload Format for MPEG-4 Audio/Visual StreamsCurrent
October 2011
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?