03-02-2010 04:39 AM - edited 03-15-2019 09:35 PM
Hi, All!
Now I have the next problem: on my voice gateway AS5350 I have SIP trunk and PRI. This channels point to the same destination .T
Outgoing calls camming from CUCM 7.1.
I need to make the outgoing call routing based on incoming calling number, for example:
calling numeber 11111 must make outgoing calls throught SIP trunk
calling number 22222 must make outgoing calls throught PRI connection.
I can't use translation patterns for prefix called number and after that strip digits on pots dial-peer, because this translation is visible for subscribers.
Thank you for help )
Solved! Go to Solution.
03-02-2010 04:47 AM
http://www.cisco.com/en/US/tech/tk652/tk90/technologies_configuration_example09186a00801c0a88.shtml
Otherwise you can do COR based configuratio, still using answer-address as discriminator.
03-02-2010 06:51 AM
Actually, in regards to:
"I can't use translation patterns for prefix called number and after that strip digits on pots dial-peer, because this translation is visible for subscribers."
I know what you ran into and you can accomodate this on the dial-peers. I had a similar requirement a while back and I handled it by prefixing a 3-digit access code (my own convention) on the called party number before handing it off to the gateway. Then I used a combination of forward-digits and called-party translations to give the PSTN what they wanted and also mask the pattern on the IP phone display. My scenario isn't exactly the same as yours, but maybe it will give you some ideas.
voice translation-rule 30
rule 1 /^101/ //
rule 2 /^102/ //
!
voice translation-profile normal-called-translate
translate called 30
!
dial-peer voice 91010 pots
destination-pattern 101.T !the 101 will get stripped
translation-profile outgoing normal-called-translate !this will "hide" the 101 from your IP phone display
!
dial-peer voice 91020 pots
destination-pattern 102.T
translation-profile outgoing normal-called-translate !this will "hide" the 101 from your IP phone display
!
The only problem is that none of the above triggers on "called party" information and you would have to do something on the CUCM. I suppose you could do something on the ingress side of the call signal received by the gateway. With the CUCM one approach would be to use a Standard Local Route Group (SLRG) config. But this is only viable if the 1111 and 2222 in your example are on two separate phones. If both lines are on the same phone then SLRG won't help and you would have to use line level CSS and translation/route patterns to have the same destination pattern do different called party transforms. Not incredibly scalable.
Anyway, some additional food for thought.
HTH.
Regards,
Bill
Please remember to rate helpful responses and identify
03-02-2010 04:47 AM
http://www.cisco.com/en/US/tech/tk652/tk90/technologies_configuration_example09186a00801c0a88.shtml
Otherwise you can do COR based configuratio, still using answer-address as discriminator.
03-02-2010 06:51 AM
Actually, in regards to:
"I can't use translation patterns for prefix called number and after that strip digits on pots dial-peer, because this translation is visible for subscribers."
I know what you ran into and you can accomodate this on the dial-peers. I had a similar requirement a while back and I handled it by prefixing a 3-digit access code (my own convention) on the called party number before handing it off to the gateway. Then I used a combination of forward-digits and called-party translations to give the PSTN what they wanted and also mask the pattern on the IP phone display. My scenario isn't exactly the same as yours, but maybe it will give you some ideas.
voice translation-rule 30
rule 1 /^101/ //
rule 2 /^102/ //
!
voice translation-profile normal-called-translate
translate called 30
!
dial-peer voice 91010 pots
destination-pattern 101.T !the 101 will get stripped
translation-profile outgoing normal-called-translate !this will "hide" the 101 from your IP phone display
!
dial-peer voice 91020 pots
destination-pattern 102.T
translation-profile outgoing normal-called-translate !this will "hide" the 101 from your IP phone display
!
The only problem is that none of the above triggers on "called party" information and you would have to do something on the CUCM. I suppose you could do something on the ingress side of the call signal received by the gateway. With the CUCM one approach would be to use a Standard Local Route Group (SLRG) config. But this is only viable if the 1111 and 2222 in your example are on two separate phones. If both lines are on the same phone then SLRG won't help and you would have to use line level CSS and translation/route patterns to have the same destination pattern do different called party transforms. Not incredibly scalable.
Anyway, some additional food for thought.
HTH.
Regards,
Bill
Please remember to rate helpful responses and identify
03-04-2010 01:31 AM
Thank you all very mach! Your solutions were good and helpful!
I applied the COR list, and all working fine.
But after reading the next post from William, I understood where I need implement translations to remove unwonted digits )
03-04-2010 01:58 AM
Very good.
Please remember to rate useful posts clicking on the stars below,
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide