Source note · Setting up SIPREC forking on CUBE for call recording

Cisco lists an incorrect inbound dial-peer match, where the selected inbound dial-peer has no media-class, as a common SIPREC failure in new deployments.

Checked 2026-10-01

the selected inbound dial peer does not have media-class associated with it

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, first bullet

Cite this note

APA

WarmTransfer. (2026, October 1). Setting up SIPREC forking on CUBE for call recording: source note cube-siprec-setup-inbound-match-issue. WarmTransfer. https://warmtransfer.net/knowledge/claims/cube-siprec-setup-inbound-match-issue

BibTeX

@misc{warmtransfer-claim-cube-siprec-setup-inbound-match-issue,
  title  = {Setting up SIPREC forking on CUBE for call recording: source note cube-siprec-setup-inbound-match-issue},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/claims/cube-siprec-setup-inbound-match-issue},
  note   = {Source note cube-siprec-setup-inbound-match-issue, checked 2026-10-01}
}

Read in context