If several dial peers match an incoming call on URI, the longest matching dial peer is chosen, as with called-number matching.
Checked 2026-10-02
For incoming dial-peer match based on URI, if there are multiple dial-peers matches, then the longest matching dial-peer is chosen
- Vendor
- Cisco
- Product
- Cisco Unified Border Element
- Subsystem
- voice-class-uri
- Deployment
- on-premises
- Region
- not restricted
- Release range
- Cisco IOS XE 17.6 onwards
- Checked
- 2026-10-02
Sources
- Cisco Unified Border Element Configuration Guide - Cisco IOS XE 17.6 Onwards - Matching Inbound Dial Peers by URI of Incoming SIP Calls — Cisco Systems · tier 2 current vendor documentation · chapter 'Matching Inbound Dial Peers by URI of Incoming SIP Calls', matching notes
Cite this note
APA
WarmTransfer. (2026, October 2). Troubleshooting CUBE calls that match the wrong dial-peer: source note cube-dial-peer-matching-troubleshooting-uri-longest-match. WarmTransfer. https://warmtransfer.net/knowledge/claims/cube-dial-peer-matching-troubleshooting-uri-longest-match
BibTeX
@misc{warmtransfer-claim-cube-dial-peer-matching-troubleshooting-uri-longest-match,
title = {Troubleshooting CUBE calls that match the wrong dial-peer: source note cube-dial-peer-matching-troubleshooting-uri-longest-match},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/cube-dial-peer-matching-troubleshooting-uri-longest-match},
note = {Source note cube-dial-peer-matching-troubleshooting-uri-longest-match, checked 2026-10-02}
}