Source note · Setting up SIPREC forking on CUBE for call recording
MiaRec's CUBE SIPREC integration guide recommends assigning the recorder to the incoming dial-peer rather than the outgoing one.
Checked 2026-10-01
It is recommended to assign the recorder to the incoming dial-peer rather than to the outgoing peer.
- Vendor
- MiaRec
- Product
- MiaRec
- Subsystem
- CUBE SIPREC integration
- Deployment
- on-premises
- Region
- not restricted
- Release range
- current as of 2026-10-01
- Checked
- 2026-10-01
Sources
- Cisco CUBE SIPREC configuration — MiaRec · tier 3 vendor-maintained repositories · Dial-peer configuration section
Cite this note
APA
WarmTransfer. (2026, October 1). Setting up SIPREC forking on CUBE for call recording: source note cube-siprec-setup-miarec-incoming-peer. WarmTransfer. https://warmtransfer.net/knowledge/claims/cube-siprec-setup-miarec-incoming-peer
BibTeX
@misc{warmtransfer-claim-cube-siprec-setup-miarec-incoming-peer,
title = {Setting up SIPREC forking on CUBE for call recording: source note cube-siprec-setup-miarec-incoming-peer},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/cube-siprec-setup-miarec-incoming-peer},
note = {Source note cube-siprec-setup-miarec-incoming-peer, checked 2026-10-01}
}