Basic call routing question

[zrunner626]

This is a basic question for most of you guys but I need some confirmation of call routing process. I am needing to include a couple new test DIDs into our system for a new circuit. We are receiving 3 digits from the carrier. I already have a dial-peer on the router that will send the calls to the Call Manager as 21111 (for example). On Call Manager I have translation pattern for 21XXX to Called Party Transform Mask of 21XXX for the appropriate partition that the gateway router is in.

dial-peer voice 11131 voip
destination-pattern [0-9]...$
session target ipv4:X.X.X.X
incoming called-number 9T
voice-class codec 1
voice-class h323 1
dtmf-relay h245-signal h245-alphanumeric
ip qos dscp cs3 signaling
no vad

So...

1. I shouldn't need to add any additional translation pattern, correct

2. If I have run a  Route Plan Report for All Patterns and there are no other 21111 then I should be clear to add that 5 digit dial, correct?

Am I missing anything?

Much appreciated.

[Dennis Mink]

Is that same router running SRST?  

If so, I would configure a translation pattern on the INCOMING dial peer on that router, that expand the incoming called number into the full extension number as you have it configured on the phone.

this way you dont need the transforms on cucm either.

so create an additional dialpeer on your router and match it by "incoming called number ."  and apply a translation profile to that dial peer  (can even do it on the voice port if it has an ISDN in it)

[zrunner626]

This one is not running SRST

[Amit Sharawat]

Hi,

I see that you are matching incoming called number starting from 9, but you are using the destination patterns for all starting from 0 to 9. Please be sure that if you want to match all the numbers starting from 0 to 9, use the incoming called number as .T,

Additionally, i see that your destination patter is a 4 digit match ( [0-9]...$), that means you are sending 4 digits to CUCM, but your translation patter is 5-digit.

Considering your dial-peer and the translation pattern on the CUCM, you can add extra digit to make it a 5-digit on the GW itself by using translation profile. For eg.

voice translation-rule 1
 rule 1 /^\(.....$\)/ /2\1/      ----> This is prefix 2 in front of a 4-digit number

voice translation-profile profile1
 translate called 1

dial-peer voice 11131 voip
 translation-profile outgoing profile1

[zrunner626]

Actually, I think the above dial-peer may have been a mistake. I found the below dial-peer that matches 3 digits (which my debug isdn q931 shows I am receiving from the carrier.)  So this dial-peer would indictate it sends the 3 digits to my call manager and if my call manager has a translation pattern in the allowed partition that my gateway is in, 21XXX gets translated to 21XXX and sent to the phone. I'm really just trying to make sure I understand how this is working, yes I need to add two test DIDs but want to make sure it works with all the DIDs as well once we make the cutover.

dial-peer voice 11133 voip
destination-pattern [0-9]..$
session target ipv4:X.X.X.X
incoming called-number 9T
voice-class codec 1
voice-class h323 1
dtmf-relay h245-signal h245-alphanumeric
fax-relay ecm disable
fax rate 14400
ip qos dscp cs3 signaling
no vad

[Amit Sharawat]

Hi,

If you have put the translation on the GW configuration on the call manager for the incoming calls, then i believe this configuration should be fine. Make sure that your "incoming CSS" on the gateway has the partition for all the phones with DN 21XXX.

~Amit

[sansardanish]

HI

As you are using Dial-peer to match all the 3 digit numbers, You don't need any additional patterns for testing new DID's.

[zrunner626]

Thanks. That is what I was thinking since the translation pattern 21XXX on CM is broad enough to cover the new DIDs and I don't see any conflicting line numbers.