Because dial peer 0 carries only default capabilities, a call that unexpectedly matches it is likely to show symptoms such as DTMF failure, an unexpected codec or missing per-dial-peer SIP settings, so 'Incoming Dial-peer=0' in debugs is a first check for those symptoms.
inferred · Checked 2026-10-02
- Vendor
- Cisco
- Product
- Cisco Unified Border Element
- Subsystem
- default-dial-peer-0
- Deployment
- on-premises
- Region
- not restricted
- Release range
- current as of 2026-10-02
- Status
- inferred
- Checked
- 2026-10-02
Sources
- Understand IOS and IOS XE Call Routing — Cisco Systems · tier 2 current vendor documentation · section 'When No Matches Exist / Default Dial-Peer 0'
Cite this note
APA
WarmTransfer. (2026, October 2). Troubleshooting CUBE calls that match the wrong dial-peer: source note cube-dial-peer-matching-troubleshooting-inf-dp0-symptoms. WarmTransfer. https://warmtransfer.net/knowledge/claims/cube-dial-peer-matching-troubleshooting-inf-dp0-symptoms
BibTeX
@misc{warmtransfer-claim-cube-dial-peer-matching-troubleshooting-inf-dp0-symptoms,
title = {Troubleshooting CUBE calls that match the wrong dial-peer: source note cube-dial-peer-matching-troubleshooting-inf-dp0-symptoms},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/cube-dial-peer-matching-troubleshooting-inf-dp0-symptoms},
note = {Source note cube-dial-peer-matching-troubleshooting-inf-dp0-symptoms, checked 2026-10-02}
}