Question

A CUBE running IOS XE receives an inbound INVITE from an ITSP. Two inbound dial-peers are configured: dial-peer 100 has 'incoming uri via 10.1.1.1' matching the provider's source IP, and dial-peer 200 has 'incoming called-number 5551234...'. The INVITE arrives from the ITSP source IP 10.1.1.1 with a called number of 5551234567. Both dial-peers appear to be valid candidates. Which dial-peer will CUBE select to process this inbound call leg, and why?

Accepted Answer

Dial-peer 100, because 'incoming uri via' has a higher match priority than 'incoming called-number' in the inbound dial-peer selection order

Answer

Dial-peer 200, because 'incoming called-number' with an explicit digit string is always the most specific match

Answer

Dial-peer 100, because it has the lower dial-peer tag number and lower tags are always preferred

Answer

Dial-peer 200, because inbound matching evaluates 'incoming called-number' before any 'incoming uri' commands