Accepted Solutions
Sure, that would work as well. Or create additional dial peers that has a different match from the two you have now.
For example this.
dial-peer voice 160 voip
description New range dialing to CUCM Cluster
destination-pattern 404757….$
session target ipv4:10.10.10.10
voice-class codec 9999
voice-class h323 8888
dtmf-relay h245-alphanumeric
fax protocol t38 version 0 ls-redundancy 5 hs-redundancy 2 fallback pass-through g711ulaw
no vad
!
dial-peer voice 161 voip
description New range dialing to CUCM Cluster
preference 1
destination-pattern 404757….$
session target ipv4: 10.10.10.11
voice-class codec 9999
voice-class h323 8888
dtmf-relay h245-alphanumeric
fax protocol t38 version 0 ls-redundancy 5 hs-redundancy 2 fallback pass-through g711ulaw
no vad
However the best and cleanest would be to create a translation on your gateway so that you don't need to create additional dial peers. Something like this should work.
voice translation-rule 20
rule 1 /^404757\(….\)$/ /\1/
!
voice translation-profile PSTN-IN
translate called 20
!
dial-peer voice 1 pots
translation-profile incoming PSTN-IN
This would keep the last 4 digits, also known as a number slice that is indicated by the use of parentheses on the left hand side and the \1 on the right hand side. Left hand is the match side and the right hand is the replace side. For more information on how to use translations see the before linked to document or this for even more details on how translations works. https://www.cisco.com/c/en/us/support/docs/voice/call-routing-dial-plans/64020-number-voice-translation-profiles.html
There are also options as previously mentioned to put the translation profile incoming command on the voice port or on the trunk group. This is often preferred as compared to using it on a dial peer, as that could be wrongly configured so that it doesn't match with the one that you think it does.
Please share your dial peer and if in existence voice translation configuration. Based on this “032489: *Jul 21 17:21:48.881: %VOICE_IEC-3-GW: C SCRIPTS: Internal Error (No dialpeer match): IEC=1.1.128.11.5.0 on callID 758 GUID=F7204E98087111ED81B56400F122D900” you don’t have a match on a dial peer pointing towards CM, so the call never leaves you’re gateway.
Both of your dial peers that points towards CM has a match of four digits. From what I can see your service provider sends you the called number as this “Called Party Number i = 0xA1, '4047575555'”. With this there is no dial peer that matches. You would need to translate the called number on ingress into the gateway, either on the inbound dial peer, voice port or trunk group if you use that, down to the last four digits so that it matches the dial peers towards CM.
On a side note neither of these trunk group lines are needed on this dial peer.
dial-peer voice 1 pots
trunkgroup LD-SIP
trunkgroup Local-SIP
These are configuration that is used for outbound dial peers, as this is an inbound dial peer they are not relevant.
Have a look at these two documents for details on how to configure call routing in IOS.
Sure, that would work as well. Or create additional dial peers that has a different match from the two you have now.
For example this.
dial-peer voice 160 voip
description New range dialing to CUCM Cluster
destination-pattern 404757….$
session target ipv4:10.10.10.10
voice-class codec 9999
voice-class h323 8888
dtmf-relay h245-alphanumeric
fax protocol t38 version 0 ls-redundancy 5 hs-redundancy 2 fallback pass-through g711ulaw
no vad
!
dial-peer voice 161 voip
description New range dialing to CUCM Cluster
preference 1
destination-pattern 404757….$
session target ipv4: 10.10.10.11
voice-class codec 9999
voice-class h323 8888
dtmf-relay h245-alphanumeric
fax protocol t38 version 0 ls-redundancy 5 hs-redundancy 2 fallback pass-through g711ulaw
no vad
However the best and cleanest would be to create a translation on your gateway so that you don't need to create additional dial peers. Something like this should work.
voice translation-rule 20
rule 1 /^404757\(….\)$/ /\1/
!
voice translation-profile PSTN-IN
translate called 20
!
dial-peer voice 1 pots
translation-profile incoming PSTN-IN
This would keep the last 4 digits, also known as a number slice that is indicated by the use of parentheses on the left hand side and the \1 on the right hand side. Left hand is the match side and the right hand is the replace side. For more information on how to use translations see the before linked to document or this for even more details on how translations works. https://www.cisco.com/c/en/us/support/docs/voice/call-routing-dial-plans/64020-number-voice-translation-profiles.html
There are also options as previously mentioned to put the translation profile incoming command on the voice port or on the trunk group. This is often preferred as compared to using it on a dial peer, as that could be wrongly configured so that it doesn't match with the one that you think it does.
