Calling party translation in h323 gateway

[vinayjaiswal]

Hi,

I have a setup of main site and remote site,remote site phones register to main site over the WAN. One PRI is terminated on the remote Voice gateway. Remote users should use the local PRI to make outgoing call.The remote site phones have extn range of 8XXX. Telco expects the calling party shoud be 28988XXX. The Route Pattern is 9XXXXXXXXX. I have SRST enabled on the Voice gateway.It is an H323 gateway. I need to do all the translation on the gateway rathe than on the Call Manager. I am unable to do the calling party translation on the VG. Please help me with the config.

Thanks,

Vinay

[gogasca]

Use translation rules under incoming dial peer or voice ports

[sanjeevreddyallala]

I think the following should do.

----------------------

translation rule 1

rule 0   ^8...   28988

voice-port 0/0/0:0

translate called 1

1. When a user enters 4 digit ext 8xxx usually goes via WAN as the voip dial peer is more close match than pots.

2. If WAN down call will be routed via pots dial peer which using voice port 0/0/0:0

3. before call forwarded to PSTN it will be translated according to the rule mentioned above.

about rule  rule 0   ^8...   28988

-------

any 4 digit extension starts with 8 will be prefixed with 2898

[Ayodeji Okanlawon · Accepted solution]

The gateway config you posted is MGCP. I hope this is the correct gateway..

Anyways, this is what you need to do.

voice translation-rule 3
rule 1 /^\(8.../)$ /28988\1/

The create the translation profile....see below

voice translation-profile CLI-OUT
translate calling 3

Next apply the translation profile to your out going dial-peers..This needs to be applied to all your H.323 out going dial-peers

xample below:

dial-peer voice 1000 pots
description International Operator
translation-profile outgoing CLI-OUT
destination-pattern 9100
progress_ind setup enable 3
progress_ind alert enable 8
port 0/0/0:15
forward-digits 3
!

[vinayjaiswal]

thanks, It resolved my issue, the dial-peer was not not Discarding the 9, when the destination-pattern was 9T, I had to create a translation rule to discard that. After that is working fine. Thanks all for your valuable comments and suggestion.