Source note · Setting up SIPREC forking on CUBE for call recording
Applying the media class to both the carrier-facing and the internal dial-peer of the same call risks two recording sessions for one call, so the media class should sit on one side only.
inferred · Checked 2026-10-01
- Vendor
- Cisco
- Product
- Cisco Unified Border Element
- Subsystem
- SIPREC design
- Deployment
- on-premises
- Region
- not restricted
- Release range
- current as of 2026-10-01
- Status
- inferred
- Checked
- 2026-10-01
Sources
- Cisco CUBE SIPREC configuration — MiaRec · tier 3 vendor-maintained repositories · dial-peer assignment recommendation
Cite this note
APA
WarmTransfer. (2026, October 1). Setting up SIPREC forking on CUBE for call recording: source note cube-siprec-setup-single-anchor-per-call. WarmTransfer. https://warmtransfer.net/knowledge/claims/cube-siprec-setup-single-anchor-per-call
BibTeX
@misc{warmtransfer-claim-cube-siprec-setup-single-anchor-per-call,
title = {Setting up SIPREC forking on CUBE for call recording: source note cube-siprec-setup-single-anchor-per-call},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/cube-siprec-setup-single-anchor-per-call},
note = {Source note cube-siprec-setup-single-anchor-per-call, checked 2026-10-01}
}