RFC 7245: An Architecture for Media Recording Using the Session Initiation Protocol
In plain English — editorial summary, not part of the RFC
Session recording is a critical requirement in many communications environments such as call centers and financial trading. In some of these environments, all calls must be recorded for regulatory, compliance, and consumer protection reasons. Recording of a session is typically performed by sending a copy of a media stream to a recording device. This document describes architectures for deploying session recording solutions in an environment that is based on the Session Initiation Protocol (SIP).
Document record
- Document ID
- RFC7245
- Published
- May 2014
- Authors
- A. Hutton; L. Portman; R. Jain; K. Rehor
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- art
- Pages
- 16
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7247Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): Architecture, Addresses, and Error HandlingCurrent
May 2014
- RFC 7248Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): PresenceObsoleted
May 2014
- RFC 7163URN for Country-Specific Emergency ServicesCurrent
March 2014
- RFC 7340Secure Telephone Identity Problem Statement and RequirementsCurrent
September 2014
- RFC 7345UDP Transport Layer (UDPTL) over Datagram Transport Layer Security (DTLS)Updated
August 2014
- RFC 7131Session Initiation Protocol (SIP) History-Info Header Call Flow ExamplesCurrent
March 2014
- RFC 7118The WebSocket Protocol as a Transport for the Session Initiation Protocol (SIP)Current
January 2014
- RFC 7375Secure Telephone Identity Threat ModelCurrent
October 2014
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?