Calls that use an E.164 number rather than a URI use the dial-peer matching rules that existed before IOS 15.1(2)T.
Checked 2026-10-02
Calls using an E.164 number, rather than a URI, use the dial-peer matching rules that existed prior to Cisco IOS Release 15.1(2)T.
- Vendor
- Cisco
- Product
- Cisco Unified Border Element
- Subsystem
- inbound-dial-peer-matching
- Deployment
- on-premises
- Region
- not restricted
- Release range
- current as of 2026-10-02
- Checked
- 2026-10-02
Sources
- Cisco IOS Voice Command Reference - D through I - icpif through irq global-request — Cisco Systems · tier 2 current vendor documentation · command entry 'incoming uri', Usage Guidelines note
Cite this note
APA
WarmTransfer. (2026, October 2). Troubleshooting CUBE calls that match the wrong dial-peer: source note cube-dial-peer-matching-troubleshooting-e164-pre-1512t-rules. WarmTransfer. https://warmtransfer.net/knowledge/claims/cube-dial-peer-matching-troubleshooting-e164-pre-1512t-rules
BibTeX
@misc{warmtransfer-claim-cube-dial-peer-matching-troubleshooting-e164-pre-1512t-rules,
title = {Troubleshooting CUBE calls that match the wrong dial-peer: source note cube-dial-peer-matching-troubleshooting-e164-pre-1512t-rules},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/cube-dial-peer-matching-troubleshooting-e164-pre-1512t-rules},
note = {Source note cube-dial-peer-matching-troubleshooting-e164-pre-1512t-rules, checked 2026-10-02}
}