RFC 7866: Session Recording Protocol

Publisher

IETF / RFC Editor

URL

https://www.rfc-editor.org/rfc/rfc7866.html

Published

2016-05-01

Updated

unknown

Accessed

2026-09-25

HTTP status

200

License

IETF Trust Legal Provisions (BCP 78); no-redistribution; short excerpts and locators only

Source notes citing this source

• The SIPREC metadata body part carries Content-Disposition type recording-session. in context
• RFC 7866 says the SRC SHOULD (not MUST) include a full metadata snapshot in the initial INVITE that establishes the recording session. in context
• RFC 7866 as published names the SIPREC metadata content type application/rs-metadata, without the +xml suffix. disputed in context
• The SRC can send recording metadata in an INVITE request, in an UPDATE request, or in a 200 response to an offerless INVITE. in context
• When a SIPREC SIP message carries both an SDP offer and recording metadata, the body must use content type multipart/mixed. in context
• RFC 7866 permits persistent recording, in which a recording session is established in the absence of any communication session. in context
• RFC 7866 defines the SDP attribute a=record with values on, off and paused to indicate recording state to recording-aware participants. in context
• RFC 7866 defines the SDP attribute a=recordpref with values on, off, pause and nopreference, which a participant uses to express a recording preference. in context
• An SRC must include the siprec option tag in the Require header when initiating a recording session so that a UA without Session Recording Protocol support rejects the INVITE with 420 (Bad Extension). in context
• RFC 7866 requires the recording session to be at least as secure as the communication session being recorded, including at least the same cipher-suite strength. in context
• In a recording session the SRC typically marks each offered media stream a=sendonly. in context
• Under RFC 7866 the Session Recording Client must include the +sip.src feature tag in the Contact URI of the recording session. in context
• The SRS normally answers each recording media stream with a=recvonly because it typically only receives RTP from the SRC. in context
• RFC 7866 (Session Recording Protocol) is a Standards Track RFC published in May 2016. in context
• RFC 7866 requires both SRC and SRS to support SIP over TLS version 1.2. in context

Cite this source record

APA

WarmTransfer. (2016, May 1). RFC 7866: Session Recording Protocol. WarmTransfer. https://warmtransfer.net/knowledge/sources/rfc-7866-siprec-protocol

BibTeX

@misc{warmtransfer-rfc-7866-siprec-protocol,
  title  = {RFC 7866: Session Recording Protocol},
  author = {{WarmTransfer}},
  year   = {2016},
  url    = {https://warmtransfer.net/knowledge/sources/rfc-7866-siprec-protocol},
  note   = {IETF / RFC Editor, accessed 2026-09-25}
}