Source note · Setting up SIPREC forking on CUBE for call recording
Where the Unified CM leg is SRTP and the carrier leg is RTP, the SIPREC media class has to go on the carrier-facing dial-peer, because only the RTP leg can be forked.
inferred · Checked 2026-10-01
- Vendor
- Cisco
- Product
- Cisco Unified Border Element
- Subsystem
- SIPREC design
- 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 · Restrictions for SIPREC Recording; show voip recmsp session field table
Cite this note
APA
WarmTransfer. (2026, October 1). Setting up SIPREC forking on CUBE for call recording: source note cube-siprec-setup-srtp-internal-forces-carrier. WarmTransfer. https://warmtransfer.net/knowledge/claims/cube-siprec-setup-srtp-internal-forces-carrier
BibTeX
@misc{warmtransfer-claim-cube-siprec-setup-srtp-internal-forces-carrier,
title = {Setting up SIPREC forking on CUBE for call recording: source note cube-siprec-setup-srtp-internal-forces-carrier},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/cube-siprec-setup-srtp-internal-forces-carrier},
note = {Source note cube-siprec-setup-srtp-internal-forces-carrier, checked 2026-10-01}
}