Accepted Solutions
It was me that misread your information. You were really clear. I’m sorry for the misunderstanding. It’s clear that you had two different issues. The issue with different number formats could have been solved by a voice translation rule/profile in your router to strip down the called number to four digits, but using full +E.164 format in CM on the directory numbers is a much better option.
Change the inbound match to use VIA header information instead of incoming called-number .. For more information on how to do this please have a look at this fantastic document that goes deep in on how call routing operates in IOS. Explain Cisco IOS and IOS XE Call Routing
Very likely what is happening is that the wrong inbound dial peer is matched as you have identical match statements on them.
Based on your shared configuration this would likely be what you'd need.
voice class uri PSTN sip
host ipv4:123.456.123.456
voice class uri CUCM sip
host ipv4:10.1.1.1
host ipv4:10.1.1.2
dial-peer voice 4001 voip
no incoming called-number .
incoming uri via CUCM
dial-peer voice 5001 voip
no incoming called-number .
incoming uri via PSTN
The IP from the ITSP you might want to check in an inbound Invite to see what they send in the VIA field. For CM it should be correct based on your shared information.
The match on VIA that I provided is needed to diffrenciate the match of the two inbound dial peers. Without that you'd not match the correct inbound dial peer and then the DPG config that send the calls to the applicable outbound dial peer would not be using the correct/intended outbound dial peer for the two call scenarios.
@Manual404 wrote:
Hello Roger,
I did configure the URIs but it didn't solve the issue at first (it's working now).
The main issue was on CUCM. I had the directory number set to 4-digits and added the other digits as external mask. It was all fine when calls were going out because the external mask would add the digits to make a full number but when calls were coming in - it would not find the full number. Issue got resolved when I changed the directory number from 4-digits to a full one (and removed the external mask).
Also, not sure if the URIs were needed but my dial-peers are now configured with URIs instead of "incoming called-number ." and it's all working.
FWIW What you describe here has nothing to do with what you originally asked for. This pertains to inbound calls and what you asked for initially was outbound calls.
It was me that misread your information. You were really clear. I’m sorry for the misunderstanding. It’s clear that you had two different issues. The issue with different number formats could have been solved by a voice translation rule/profile in your router to strip down the called number to four digits, but using full +E.164 format in CM on the directory numbers is a much better option.
