Can a translation-profile applied on an incoming DP influence the match of an outgoing DP?
My use case is a CUCM sending SIP INVITEs with 8 digits in the To field, but I would like to configure the outgoing POTS dial-peers using an E164 destination-pattern. The idea is to expand the incoming DNIS to E164 then use this to match the outgoing POTS dial-peer.
Unfortunately this doesn't work and i think outgoing DP is getting matched before the incoming translation-profile is applied.
! Intended call flow: CUCM SIP -> DialPeer1 -> Translation TP-ToE164 -> DialPeer200
dial-peer voice 1 voip
description IN/OUT: CUCM
incoming uri via 1
destination-pattern .T
translation-profile incoming TP-ToE164
session protocol sipv2
session server-group 1
voice-class codec 1
voice-class sip options-keepalive profile 1
voice-class sip bind control source-interface Loopback1
voice-class sip bind media source-interface Loopback1
dtmf-relay rtp-nte
no vad
exit
!
dial-peer voice 200 pots
description To Fax Machine
destination-pattern +4412345678
port 0/1/0
exit
!
voice translation-profile TP-ToE164
translate calling 1
translate called 1 <- Should translate DNIS up to E164
exit
voice translation-rule 1
rule 1 /^\(123456..\)$/ /+44\1/
exit