Source note · Setting up SIPREC forking on CUBE for call recording
Because Cisco states CUBE compliance against draft-ietf-siprec-metadata-17 and draft-ietf-siprec-protocol-16 rather than RFC 7865 and RFC 7866, a recorder's SIPREC conformance claim alone does not prove CUBE interoperability; confirm the recorder vendor's tested CUBE integration.
inferred · Checked 2026-10-01
- Vendor
- Cisco
- Product
- Cisco Unified Border Element
- Subsystem
- SIPREC interoperability
- Deployment
- on-premises
- Region
- not restricted
- Release range
- IOS XE 17.6 onwards
- Status
- inferred
- Checked
- 2026-10-01
Sources
- Cisco Unified Border Element Configuration Guide - Cisco IOS XE 17.6 Onwards: SIP Forking — Cisco Systems · tier 2 current vendor documentation · Prerequisites for SIPREC Recording, third and fourth bullets
Cite this note
APA
WarmTransfer. (2026, October 1). Setting up SIPREC forking on CUBE for call recording: source note cube-siprec-setup-draft-vs-rfc-compat. WarmTransfer. https://warmtransfer.net/knowledge/claims/cube-siprec-setup-draft-vs-rfc-compat
BibTeX
@misc{warmtransfer-claim-cube-siprec-setup-draft-vs-rfc-compat,
title = {Setting up SIPREC forking on CUBE for call recording: source note cube-siprec-setup-draft-vs-rfc-compat},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/cube-siprec-setup-draft-vs-rfc-compat},
note = {Source note cube-siprec-setup-draft-vs-rfc-compat, checked 2026-10-01}
}