For SIP calls the inbound dial-peer preference order is incoming uri via, incoming uri request, incoming uri to, incoming uri from, then called number, calling number, destination-pattern (ANI) and finally carrier-id.
Checked 2026-10-02
- 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
- Understand IOS and IOS XE Call Routing — Cisco Systems · tier 2 current vendor documentation · section 'Inbound Dial-Peer Matching', SIP preference table (Table 1)
Cite this note
APA
WarmTransfer. (2026, October 2). Troubleshooting CUBE calls that match the wrong dial-peer: source note cube-dial-peer-matching-troubleshooting-sip-in-uri-first. WarmTransfer. https://warmtransfer.net/knowledge/claims/cube-dial-peer-matching-troubleshooting-sip-in-uri-first
BibTeX
@misc{warmtransfer-claim-cube-dial-peer-matching-troubleshooting-sip-in-uri-first,
title = {Troubleshooting CUBE calls that match the wrong dial-peer: source note cube-dial-peer-matching-troubleshooting-sip-in-uri-first},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/cube-dial-peer-matching-troubleshooting-sip-in-uri-first},
note = {Source note cube-dial-peer-matching-troubleshooting-sip-in-uri-first, checked 2026-10-02}
}