Source note · Setting up SIPREC forking on CUBE for call recording
Because Cisco shows the media class on an inbound Unified CM-facing dial-peer in one example and on an outgoing dial-peer in another, and states no requirement, either the carrier-facing or the internal dial-peer can be the SIPREC anchor.
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 · Configuration Examples for SIPREC-based Recording; Troubleshoot, working scenario
Cite this note
APA
WarmTransfer. (2026, October 1). Setting up SIPREC forking on CUBE for call recording: source note cube-siprec-setup-either-leg-can-anchor. WarmTransfer. https://warmtransfer.net/knowledge/claims/cube-siprec-setup-either-leg-can-anchor
BibTeX
@misc{warmtransfer-claim-cube-siprec-setup-either-leg-can-anchor,
title = {Setting up SIPREC forking on CUBE for call recording: source note cube-siprec-setup-either-leg-can-anchor},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/cube-siprec-setup-either-leg-can-anchor},
note = {Source note cube-siprec-setup-either-leg-can-anchor, checked 2026-10-01}
}