Digit Translation at CUCM or IOS or both?

[DrVoIP]

Given: an MGCP Gateway supporting a PRI with a range of four digits DIDnumbers.

Problem: Serveral of the four digit DID numbers conflict with existing DID numbers.

Solution: Number Translation"

Assume an incoming 7600 conflicts with an existing 7600.  So we want to change that inbound 7600 (partition?) to some other number that is not a conflict in the enterprise, say 8600.   Do you create the Transaltion rule as IOS command in the Gateway or as a Transaltion rule in the CUCM? or Both?

Peter Buswell (aka DrVoIP)
http://blog.drvoip.com       

[Ayodeji Okanlawon]

Peter,

First thing to note is that you cant use any form of tranlsation with MGCP gateway on the IOS itself. You only have this functionality with either a h323 or SIP.

With that mentioned you only have one option which is CUCM for any form og digit manipulation on MGCP gateways. Now depending on what digits your provider is passing to you...If the last 6 digits are been passed, then you can configure translation pattern on cucm to achieve this..If the last 4 digits alone are passed and they are the same with the conlicting DDIs, then this will create overlapping patterns and big trouble

Please rate all useful posts

"opportunity is a haughty goddess who waste no time with those who are unprepared"

[Anas Abueideh · Accepted solution]

Hi Peter,

If you have an overlapping patterns you need to create translation pattern with a different partition other than internal partition. let us create to partition, Translation-P and Internal-P. create incoming calling search space, this calling search space contains Translation-P as a first option then the internal-P. when the incoming calling number matches an overlapping TP and DN, it will match translation pattern.

HTH

Anas

Please Rate if it is helpful

[DrVoIP]

Clearly as L3 in MGCP is trucked back to the CUCM, you cant do it in the IOS.   So, back at the Call Mangler,  I created a new partition for the DN with the conflict (e.g. 7600),  I also created a new CCS that looks in both the Translation_P and Internal_P partitions.  Simple enought.  The 7600 in the Translation-P has a Translation rule that points to a DN that is in the Internal_P that is clearly a unique number.  What I am not understanding is when 7600 comes over the PRI and its CCS contains 7600 in both partitions, which one gets dialed? Is it a prioritized list in the CCS that dictates first come first called?

[Ayodeji Okanlawon]

I dont know how you want this to work, but its not going to work. The rule is that the when a CSS matches same pattern, the first partition will be matched. So its priotized based on first matched partition. What that means is that call will never go to the second partiton for this pattern 7600. Your only option is this..if your telco sends more than 4 digit eg one is 547600 and the other 557600, then you can use this to create your xlation...As it is now, calls will only match the DN xlation pattern whose partition comes first

Please rate all useful posts

"opportunity is a haughty goddess who waste no time with those who are unprepared"

[DrVoIP]

So we seem to have a small disagreement between Aokaniawon and AAbueideh? 

My thinkin is, since the only pattern that will be in the Transaltion_P is 7600 (though it also appears in Internal_P)  I am thinking that it is an ordered list of Partitions.  The incoming 7600 will match with the Translation_P first, find that 7600 and complete the call. All other four digit numbers will be found in the Interal_P and calls completed.

Peter Buswell (aka DrVoIP)
http://blog.drvoip.com

[Ayodeji Okanlawon · Accepted solution]

Peter, I am going to disagree with your version

When the CSS of the gateway points to same pattern on different expentions..eg

CSS_GW

Translation_P

Internal_P

If you have xlation pattern 7600 in Translation_P and 7600 in Internal_P

All calls through the gateway will macth the first partition in the list unless you change the order of the partition. T

The digit analysis process looks through every partition in a calling search space for the best match. The order of the partitions that are listed in the calling search space serves only to break ties when equally good matches occur in two different partitions
 

Read document below:

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/7_1_2/ccmsys/a03ptcss.html

Please rate all useful posts

"opportunity is a haughty goddess who waste no time with those who are unprepared"

[DrVoIP]

No problem with disagreement, that is one of the reasons we have this community I hope.  Clearly, I am exploring options and that is why I asked the question.   I guess we are just going to have to try it and report back.  Let me read through the reference.

I am wondering if it would be better to make this an H323 Gateway and just do a pattern match on the dial-peer to send 7600 through an IOS translation rule before it hits the CCS and not mess around with the above configuration?

I thank all who have commented and others who may. 

Peter Buswell (aka DrVoIP)
http://blog.drvoip.com

[DrVoIP]

As it turns out the order of partitions is only an issue if there is a tie.  In the above example I have two different partitions both containing 7600.  One points to a transaltion table that transaltes 7600 to 3600; and the other points to a extension number 7600.   The calling search space for this gateway points to both partitions.   (Remember my problem is that I have four digit DID's and we have two different NXX-7600, so I am trying to use a translation table to take the one Gateway and have it use the transaltion table).   So after testing, aokanalawon is correct.

Peter Buswell (aka DrVoIP)
http://blog.drvoip.com