Source note · Setting up SIPREC forking on CUBE for call recording
Cisco lists a regular-expression destination-pattern on the recording dial-peer, instead of a simple directory number, as a common cause of SIPREC failure in new deployments.
Checked 2026-10-01
a regular expression pattern instead of a simple directory number (1… instead of 1234)
- Vendor
- Cisco
- Product
- Cisco Unified Border Element
- Subsystem
- SIPREC troubleshooting
- Deployment
- on-premises
- Region
- not restricted
- Release range
- IOS XE 17.6 onwards
- 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, second bullet
Cite this note
APA
WarmTransfer. (2026, October 1). Setting up SIPREC forking on CUBE for call recording: source note cube-siprec-setup-recorder-pattern-not-regex. WarmTransfer. https://warmtransfer.net/knowledge/claims/cube-siprec-setup-recorder-pattern-not-regex
BibTeX
@misc{warmtransfer-claim-cube-siprec-setup-recorder-pattern-not-regex,
title = {Setting up SIPREC forking on CUBE for call recording: source note cube-siprec-setup-recorder-pattern-not-regex},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/cube-siprec-setup-recorder-pattern-not-regex},
note = {Source note cube-siprec-setup-recorder-pattern-not-regex, checked 2026-10-01}
}