Source note · Setting up SIPREC forking on CUBE for call recording
RFC 7866 requires an SRC to include the siprec option tag in the Require header of a recording session INVITE, so user agents without recording support reject it with 420 Bad Extension.
Checked 2026-10-01
- Vendor
- not restricted
- Product
- not restricted
- Subsystem
- SIPREC protocol
- Deployment
- any
- Region
- not restricted
- Release range
- RFC 7866 (May 2016)
- Checked
- 2026-10-01
Sources
- RFC 7866: Session Recording Protocol — IETF / RFC Editor · tier 1 standards and regulators · Section 6.1.1 (SRC initiating a recording session)
Cite this note
APA
WarmTransfer. (2026, October 1). Setting up SIPREC forking on CUBE for call recording: source note cube-siprec-setup-rfc7866-siprec-option-tag. WarmTransfer. https://warmtransfer.net/knowledge/claims/cube-siprec-setup-rfc7866-siprec-option-tag
BibTeX
@misc{warmtransfer-claim-cube-siprec-setup-rfc7866-siprec-option-tag,
title = {Setting up SIPREC forking on CUBE for call recording: source note cube-siprec-setup-rfc7866-siprec-option-tag},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/cube-siprec-setup-rfc7866-siprec-option-tag},
note = {Source note cube-siprec-setup-rfc7866-siprec-option-tag, checked 2026-10-01}
}