Thanks Dez,

My site router has translation rules to allow users to seamlessly dial other 4 digit sites normally access over the WAN.

How do I call a translation-profile 2 when translation-profile 1 is already used for incoming translation?

Will fallback automatically call the translation-profile outgoing XXXXX under the voice-port as part of SRST?

Thanks for your response.

Kim

Kim,

Wat exactly do you want. If you are more explicit, I am sure we can help

Ok,

I currently have MGCP routers configured as SRST reference points on CUCM. The routers have the appropriate ccm-manager fallback-mgcp

config.

They also have

voice translation-rule 1

rule 1 /^4\(...\)/ /901546604\1/

rule 2 /^52/ /90158655&\1/

rule 3 /^8[7-9]/ /&/

rule 4 /^8[3-6]/ /90136970&/

rule 5 /^[27][19]/ /90163156&\1/

rule 6 /^55/ /90154660&\1/

rule 7 /^3\(...\)/ /901496303\1/

rule 8 /^999/ /999/

rule 9 /^100/ /100/

rule 10 /^907\(........\)/ /91667707\1/

rule 11 /^22\(..\)/ /9015865590\1/

rule 12 /^73/ /90170050&\1/

rule 13 /^74\(..\)/ /9015865590\1/

For all normally internally dialed sites i.e. 4 digits.

I can see how this works as the translation profile activates on fallback and a dial-peer is used;

dial-peer voice 20 pots

translation-profile outgoing ABC_Translation_Profile

With H323 the config is different I think.

Do I now configure a dial-peer voice XX pots;

dial-peer voice 20 pots

translation-profile outgoing ABC_Translation_Profile

destination-pattern .T

incoming called-number .

direct-inward-dial

port 0/0/0:15

forward-digits all

and if so will this automatically be used during fallback?

Thanks so much

Kim

Kim,

Your xlation rule in both cases have to be applied to a POTS dial-peer, regardless of whether its mgcp or h.323. The only difference is that in normal operation of mgcp, your xlation pattern will be ignored until srst is invoked.

As for H.323 your xlation rule can be used at anytime either during srst or suring normal operation.

So in summary, your xlation rule is not automattically applied to a dial-peer, you must manually apply it. With MGCP your xlation-rule is ignored until srst is invoked.

HTH

Hi HTH,

interesting. This is the first site out of 7 that we have resorted to H323, forced by fractional PRI 8 channels out of the 30 E1 possible.

I take it all calls are handled by callmanager despite duplication, I have route patterns on callmanager for users on the site behind this H323 gateway as I have route patterns for all other MGCP sites.

If callmanager is lost, I assume the dial-peers will be used and the translation-profile appending internally dialed calls (4 digits) with the national dial code.

On my MGCP controlled gateways I only needed the one dial-peer which has;

dial-peer voice 20 pots

translation-profile outgoing ABC_Translation_Profile

destination-pattern .T

incoming called-number .

direct-inward-dial

port 0/0/0:15

forward-digits all

But on my H323 gateway I have dial-peers that more or less correspond to the route patterns configured on callmanager using this H323 gateway in the route-list.

Hope the above makes some sort of sense.

Kim

Kim,

With H.323, you will need to define all your dial-plans both on the gateway and on callmanager. I.e in Call manager you will need to define route patterns to route calls to the gateway and then dial-peers to route calls from the gateway to the PSTN. You also need to define dial-peers ro route calls from the PSTN to Callmanager

With MGCP, you only need to define route patterns. This is beacuse MGCP gateways are under the control of CCM.

However for srst in MGCP gateways, you will need to define all your dial-peers just as you do for a h.323 gateway, where as you dont need to have any additional dial-peers define for srst in an h.323 gateway.

The dial-peer voice 20 pots you have above will only be used when your MGCP gateway is in SRST mode. Hence the xlation pattern will only work in this mode.

Attached for you are my working MGCP configs with and without srst and then h.323 config without srst.

HTH

technically you can still use MGCP with fractional PRI either remote the ccm-manager config commend or just add enough DSP for the number of channels

Hi HTH,

yes what you say about dial-peers matching the route patterns on CallManager is what I discovered getting this first H323 site router active.

What I want to configure is a translation-rulee that enables users to continue dialing remote site by 4 digit extensions. The translation-rule recognizes the first digit and appends the national dialing code. This already works on my MGCP/SRST gateways.

I currently have a translation-rule for incoming calls whereby the carrier presents 6 digits, I strip off the leading 2 and push 4 via a voip dial-peer to callmanager. This is translation rule 1

I reckon that I now need a translation rule 2 like this;

voice translation-rule 2

rule 1 /^4\(...\)/ /901546604\1/

rule 2 /^52/ /90158655&\1/

rule 3 /^8[7-9]/ /&/

rule 4 /^8[3-6]/ /90136970&/

rule 5 /^[27][19]/ /90163156&\1/

rule 6 /^55/ /90154660&\1/

rule 7 /^3\(...\)/ /901496303\1/

rule 8 /^907\(........\)/ /91667707\1/

rule 9 /^22\(..\)/ /9015865590\1/

rule 10 /^73/ /90170050&\1/

rule 11 /^74\(..\)/ /9015865590\1/

But I am unsure where I configure the translation-profile, is it under a dial-peer, you said that this is under an MGCP configured gateway. Where do I configure it on an H323 Gateway router?

Regards Kim

Kim,

Yes you will need to configure the dial-peer for the 4 digit pattern and then apply the translation profile under that dial-peer.

Ex below is illustrates this. In SRST users dial the 4 digit extension 12.. or 63.. which is then xlated to a full PSTN number over the PSTN.

dial-peer voice 10 pots

destination-pattern 63..

forward-digits 11

translation-profile outgoing KSH

progress_ind setup enable 3

port 0/2/0:15

dial-peer voice 9 pots

destination-pattern 12..

translation-profile outgoing KSH

progress_ind setup enable 3

forward-digits 11

port 0/2/0:15

voice translation-rule 1263

rule 1 /^\(12..\)$/ /90507701\1/

rule 2 /^\(63..\)$/ /90407808\1/

voice translation-profile KSH

translate called 1263

Hi,

okay so the following dial-peers;

dial-peer voice 30 pots

translation-profile outgoing ABC_SRST

destination-pattern [2-5]...

direct-inward-dial

port 0/0/0:15

!

dial-peer voice 31 pots

translation-profile outgoing ABC_SRST

destination-pattern 7[1-2]..

direct-inward-dial

port 0/0/0:15

!

dial-peer voice 32 pots

translation-profile outgoing ABC_SRST

destination-pattern 7[4-9]..

direct-inward-dial

port 0/0/0:15

Should work for

voice translation-profile ABC_SRST

translate called 2

voice translation-rule 2

rule 1 /^4\(...\)/ /901546604\1/

rule 2 /^52/ /90158655&\1/

rule 3 /^73/ /&/

rule 4 /^8[3-6]/ /90136970&/

rule 5 /^[27][19]/ /90163156&\1/

rule 6 /^55/ /90154660&\1/

rule 7 /^3\(...\)/ /901496303\1/

rule 8 /^999/ /999/

rule 9 /^100/ /100/

rule 10 /^907\(........\)/ /91667707\1/

rule 11 /^22\(..\)/ /9015865590\1/

rule 12 /^8[7-9]/ /90143665&\1/

rule 13 /^74\(..\)/ /9015865590\1/

And these dial-peers will only be used in the event that CallManager goes down, CallManager normally handles all internally dialled 4 digit extensions.

Thanks

Kim

Kim,

The asnwer is YES! Remember that the 4 digit dialling will only come into effect on the gateway when the phones are registerd under srst mode. Under normal operations, the phones will be registerd with callmanager..so you dont have anything to worry about

Thanks aokanlawon,

Really helpful

Kim