Call routing with specific dial-peer or translation rule.

[UsmanAkram1525]

voice translation-rule 1
rule 1 /^8251/ /406999/
!
voice translation-rule 90
rule 1 /.*/ /406900/

Voice translation-profile SIP-OUT
translate calling 1

Voice translation-profile OUTFAX
translate calling 90

____________________________________________

dial-peer voice 1 voip
description ***Outgoing Calls to ITSP***
translation-profile outgoing SIP-OUT
destination-pattern .T
session protocol sipv2
session target ipv4:192.168.2.1:5060
session transport udp
incoming called-number 406...$
voice-class sip early-offer forced
dtmf-relay sip-kpml sip-notify rtp-nte
codec g711alaw
no fax-relay sg3-to-g3
!

dial-peer voice 213 voip
description ***FAX***
translation-profile outgoing OUTFAX
destination-pattern .T
session protocol sipv2
session target ipv4:192.168.2.1:5060
session transport udp
incoming called-number 40690.$
dtmf-relay rtp-nte sip-notify
codec g711alaw
no fax-relay sg3-to-g3
fax rate disable
fax protocol pass-through g711alaw

Dear Experts,
we have this above new scenerio to make the call happen.
the problem is sometime call is going through dial-peer voice 1 and sometime from dial-peer 213. but we want that calling number 251 should use only dial-peer voice 1 so the source number can be translated to 406999.

Please need the assistance to resolve this.

NOTE: the CUCM is sending the proper call and match the proper dial-peer and facing the issue only with outgoing and it's understood that due to any translation rule.

[Nithin Eluvathingal]

To match the dial-peer using the calling number, you need to use “answer-address”. However, since there is no “answer-address” configured on the dial-peer, the behavior you mentioned is expected. Both your dial-peer  have a destination pattern of .T, and the calls will be matched based on this destination pattern, as it is used for matching the dial-peer.

Instead of using the same dial-peer for both incoming and outgoing calls, I would suggest using one for outbound and two for inbound in your case.

Apply the translations on the inbound dial-peer and use a single dial-peer to route calls externally. The setup mentioned below is an example of this. Please note that I haven’t tested the below setup, so I recommend testing it and confirming if it meets your requirements.

dial-peer voice 1 voip
description ***Inbound calls for 8251***
translation-profile inbound SIP-OUT
session protocol sipv2
session transport udp
answer-address ^8251$
voice-class sip early-offer forced
dtmf-relay sip-kpml sip-notify rtp-nte
codec g711alaw
no fax-relay sg3-to-g3
!

dial-peer voice 213 voip
description ***FAX***
translation-profile inbound OUTFAX
session protocol sipv2
session transport udp
answer-address T
dtmf-relay rtp-nte sip-notify
codec g711alaw
no fax-relay sg3-to-g3
fax rate disable
fax protocol pass-through g711alaw

dial-peer voice 2 voip
description ***Outgoing Calls to ITSP***
destination-pattern .T
session protocol sipv2
session target ipv4:192.168.2.1:5060
session transport udp
voice-class sip early-offer forced
dtmf-relay sip-kpml sip-notify rtp-nte
codec g711alaw
no fax-relay sg3-to-g3

[Roger Kallberg]

If you want to apply the translation inbound on the dial peer you’ll need to use translation-profile inbound. Also if you’re doing that there shouldn’t be a need to also have an outbound translation on the outbound dial peer. Other than that I think you’re spot on. The OP needs to use a matching operator for calling numbers on the inbound dial peers and as you I’m advocating to use different dial peers for inbound and outbound as it makes for a much clearer configuration.

If for any reason the OP wants to have different outbound dial peers I would recommend using DPGs on the inbound dial peer to set which outbound dial peer to use. For more information about how call routing works in  a router see this document. Explain Cisco IOS and IOS XE Call Routing