On 6.x there are less options to were this can be set. On the CUCM you can set it on the GW, but I would recommend you to do it on the H.323 VGW instead. There you have much more control and granularity.
First create two voice translation rules.
voice translation-rule 100
rule 1 /^$/ // type any national plan any isdn
voice translation-rule 110
rule 1 /^0\(.*\)/ /\1/
Then create a voice translation profile
voice translation-profile Set_TYPE_PLAN
translate calling 100
translate called 110
Then create a dial peer that matches the international calls.
dial-peer voice 4 pots
description Outbound to PSTN, international
translation-profile outgoing Set_TYPE_PLAN
destination-pattern 000T
progress_ind alert enable 8
progress_ind progress enable 8
progress_ind connect enable 8
port 0/0/0:15
no digit-strip
In the above DP I made the assumtion that you use 0 as the outbound prefix and that you don't do any DDI on called number in CUCM for calls out on this H.323 VGW. So we need to remove one 0 from the called number with a voice translation rule, in this case rule 110. If you do a DDI in CUCM you can disregard this rule and set the destination pattern on DP 4 to 00T.
Please rate all useful posts.
In the last debug it shows that you have set the type/plan for called number, not calling. In my example I believe that this wasn't the case. Please check your config and try again.
Please rate all useful posts.
Sent from Cisco Technical Support iPhone App
Change the rule for calling number to this,
voice translation-rule 100
rule 1 /.*/ // type any national plan any isdn
Not that it matter but in both your tests you used the called number. Also you should try to use only one of the ways to affect plan and type. Not both my suggestion and aokanlawons. The later will by the way only affect called number, not calling.
Please rate all useful posts.
Sent from Cisco Technical Support iPhone App
Probable reason for why the call is seen two times is that when the first call fails it will go to the next dial peer. Stop this with the hunt stop command under the international dial peer.
Also try to add /\0/ on the replace, aka right, side of the translation rule used for calling number. This will carry over whatever you'll match on the left side, aka the match side.
Please rate all useful posts.
Sent from Cisco Technical Support iPhone App
As I wrote in a previous answer, you should ask the Telco about the format that they want to have the calling number for international calls sent to them.
The plan and type I set in the example might not be the correct one, it was merely used as an example. If you don't ask the Telco you'll need to try a few different types and plan until you find the correct one.
If you also want to set the plan and type for called number you can use the same approach as for calling number, so that you don't have that set with a completely different way at a totally different place in IOS. That makes your config more readable and easier to troubleshoot.
Please rate all useful posts.
Sent from Cisco Technical Support iPhone App
Glad that it worked out for you in the end. Telcos are just wonderful to work with, right Can't tell how many times stuff just magically start to work after a serious talk or email
Thank you for the update and the nice rating.
Please remember to rate helpful responses and identify helpful or correct answers.
