Source note · Setting up SIPREC forking on CUBE for call recording
Because recording follows the matched dial-peer that carries the media class, a call is forked only if a dial-peer it actually matches on the chosen side has the media class, so every inbound and outbound dial-peer on that side that recorded calls can match needs it.
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 · Troubleshoot, common issues, first bullet; 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-cover-every-matched-peer. WarmTransfer. https://warmtransfer.net/knowledge/claims/cube-siprec-setup-cover-every-matched-peer
BibTeX
@misc{warmtransfer-claim-cube-siprec-setup-cover-every-matched-peer,
title = {Setting up SIPREC forking on CUBE for call recording: source note cube-siprec-setup-cover-every-matched-peer},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/cube-siprec-setup-cover-every-matched-peer},
note = {Source note cube-siprec-setup-cover-every-matched-peer, checked 2026-10-01}
}