Translation Rule Multiple Destinations

[armin.wagenfuehr]

Hi, may be somebody have an Idee! No Huntgroup and Pickup Group I wouldlike to use.

I would like to create a Translation Rule with one matching pattern and multiple replacemts. For example:

I got an incoming call with the called Number 4969299010. The last 0 is the main number of the E1 trunk. When somebody call the 299010 should distribute to multipe Destinationslike 299014444, 299015555 and 299016666.

Rule 1 /4969299010/ /299014444/

But in this kind of rule only the IP Phone 299014444 will ring. I would like to have a rule that also the 299015555 and 299016666 will ring. Soomething like this :

Rule 1 /299010/ --> /299014444/ /299015555/ /299016666/

How should work that?

Thanks in advanced!!!

[Chris Deren]

Use "alias" instead under telephony-service.

HTH,

Chris

[armin.wagenfuehr]

Hi Chris, we use IOS 15xx and this are srst GW, so we have no license to start telephony-service.

Thanks Armin

[Roger Kallberg]

You should be able to use the alias command in SRST.

Please remember to rate all useful posts.

Sent from Cisco Technical Support iPhone App

[armin.wagenfuehr]

Hi Roger, I remember me I could use for one matching alias only one destination and not several. This work also when the GW is "not" in SRST Modus, because the destinations is a voip dial-peer to the CUCM?

Regarding my numbers in the top you could provide me an example?

Thanks Armin

[Roger Kallberg · Accepted solution]

Hi Armin,

Take a look at this post, https://supportforums.cisco.com/message/3763932#3763932

I believe that it's the answer you search for.

Btw this would not work in none SRST mode. For that I recomend you to use a hunt group in CUCM and the alias in SRST.

Please remember to rate helpful responses and identify helpful or correct answers.

[armin.wagenfuehr]

Hi Roger, OK, I should take the way of Huntgroups and alias in SRST. No other chance.

THX

Armin

[Roger Kallberg]

I had a crazy idea for how to do it in CUCM, it involved a TP in a PT that is seen only by the VGWs incoming CSS, this TP matches the main number. I guess that would be 299010000? The TP send it's out on a CSS that contains a number of PTs, one per destination you would like the call to reach, in your case 3. These PTs hold one TP each, the TP has an empty match, just as you would do for PLAR. On each of these TPs you set the called transform to the destination you would like to reach. In your example set it to 299014444, 299015555 and 299016666. Then send each of these TPs out a CSS that can see the PT that holds the DNs.

I have not tested this, so I can’t really say if it will work or not. Please try it out if you like and report back the result.

Please remember to rate helpful responses and identify helpful or correct answers.

[armin.wagenfuehr]

Hi, i guess it is more complicated as use a hunt group. The customer should administrate this config. So i take the decision using hunt groups. First idee was to distribute it at the VGW to multiple destinations, but seems it not working. No transrule is available for that solution.

For SRST we use this solution.

voice translation-rule 3
rule 1 /^01431293\(..\)/  /99075011\1/
!
voice  translation-rule 4
rule 1 /\(^[1-9].*\)/ /00\1/ type  national national plan isdn isdn
rule 2 /\(^[1-9].*\)/  /000\1/ type international international plan isdn isdn
!
voice translation-rule 5
rule 1 /99075011\(..\)/ /01431293\1/ type any national plan any  isdn
!
voice translation-profile  SRST_IN
translate called 3
translate calling 4
!
voice translation-profile SRST_OUT
translate  calling 5

call-manager-fallback

alias 1 299010 to  99075011XX
alias 2 299010 to  99075011XX
alias 3 299010 to  99075011XX
translation-profile incoming SRST_IN
translation-profile outgoing SRST_OUT

THX Armin