Source note · Setting up SIPREC forking on CUBE for call recording
For SRTP calls, CUBE's XMF notification can carry an optional Crypto tag, present only with FORK_STARTED status, for the AES_CM_128_HMAC_SHA1_32 and AES_CM_128_HMAC_SHA1_80 suites.
Checked 2026-10-01
- Vendor
- Cisco
- Product
- Cisco Unified Border Element
- Subsystem
- Network-based recording (XMF)
- Deployment
- on-premises
- Region
- not restricted
- Release range
- IOS XE 17.6 onwards
- Checked
- 2026-10-01
Sources
- Cisco Unified Border Element Configuration Guide - Cisco IOS XE 17.6 Onwards - Network based Recording — Cisco Systems · tier 2 current vendor documentation · SRTP / Crypto tag in notification messages
Cite this note
APA
WarmTransfer. (2026, October 1). Setting up SIPREC forking on CUBE for call recording: source note cube-siprec-setup-xmf-srtp-crypto. WarmTransfer. https://warmtransfer.net/knowledge/claims/cube-siprec-setup-xmf-srtp-crypto
BibTeX
@misc{warmtransfer-claim-cube-siprec-setup-xmf-srtp-crypto,
title = {Setting up SIPREC forking on CUBE for call recording: source note cube-siprec-setup-xmf-srtp-crypto},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/cube-siprec-setup-xmf-srtp-crypto},
note = {Source note cube-siprec-setup-xmf-srtp-crypto, checked 2026-10-01}
}