RE: Translation-rule problem

From: Ryan West <rwest_at_zyedge.com>
Date: Fri, 6 Apr 2012 03:16:05 +0000

If you cut and pasted what I wrote, then you're matching your incoming-called
number . on dial-peer voice 1 voip. That's why the profile is matched there.
It's a little difficult to read at first, but 'debug voip ccapi inout' will
you show you the matched inbound dial-peer when you receive the call on router
2.

-ryan

From: Iam Here [mailto:go_soon2010_at_hotmail.com]
Sent: Thursday, April 05, 2012 11:12 PM
To: Ryan West; ccielab_at_groupstudy.com
Subject: RE: Translation-rule problem

Yes but it works only when i put the command translation-profile incoming
inbound_from_r1
under dial-peer voice 1 voip not dial-peer voice 3334 voip
________________________________
From: rwest_at_zyedge.com<mailto:rwest_at_zyedge.com>
To: go_soon2010_at_hotmail.com<mailto:go_soon2010_at_hotmail.com>;
ccielab_at_groupstudy.com<mailto:ccielab_at_groupstudy.com>
Subject: RE: Translation-rule problem
Date: Fri, 6 Apr 2012 03:03:43 +0000
As I was mentioning before, those profiles are outbound only and apply to the
voice-port directly to achieve what you wanted. You need to translate inbound
numbers on the receiving dial-peer. Give this a read:

http://www.cisco.com/en/US/tech/tk652/tk90/technologies_configuration_example
09186a00803f818a.shtml#con16

-ryan

From: Iam Here
[mailto:go_soon2010_at_hotmail.com]<mailto:[mailto:go_soon2010_at_hotmail.com]>
Sent: Thursday, April 05, 2012 10:51 PM
To: Ryan West; ccielab_at_groupstudy.com<mailto:ccielab_at_groupstudy.com>
Subject: RE: Translation-rule problem

Hi ryan,
Sorry, it works only with your solution (translation-profile) not with the old
translation-rule 3334
I don't really know the reason
________________________________
From: go_soon2010_at_hotmail.com<mailto:go_soon2010_at_hotmail.com>
To: rwest_at_zyedge.com<mailto:rwest_at_zyedge.com>;
ccielab_at_groupstudy.com<mailto:ccielab_at_groupstudy.com>
Subject: RE: Translation-rule problem
Date: Fri, 6 Apr 2012 05:44:34 +0300
Hi Ryan,
It works now when I put the command translate-outgoing called 3334 under
dial-peer voice 1 voip
I don't know why .
Thank you very much
________________________________
From: rwest_at_zyedge.com<mailto:rwest_at_zyedge.com>
To: go_soon2010_at_hotmail.com<mailto:go_soon2010_at_hotmail.com>;
ccielab_at_groupstudy.com<mailto:ccielab_at_groupstudy.com>
Subject: RE: Translation-rule problem
Date: Fri, 6 Apr 2012 02:18:13 +0000
Did you try applying the voice translation-profile to your dial-peer on R2?

From: Iam Here
[mailto:go_soon2010_at_hotmail.com]<mailto:[mailto:go_soon2010_at_hotmail.com]>
Sent: Thursday, April 05, 2012 10:16 PM
To: Ryan West; ccielab_at_groupstudy.com<mailto:ccielab_at_groupstudy.com>
Subject: RE: Translation-rule problem

Thanks Ryan , I used test translation-rule command too and it works fine but
when I try to call from Phone_1111 it gives busy tone I think there's
something wrong in my config
You are right , I am trying to simulate the example but I don't have FXO and i
will apply that config at the Customer later
> From: rwest_at_zyedge.com<mailto:rwest_at_zyedge.com>
> To: go_soon2010_at_hotmail.com<mailto:go_soon2010_at_hotmail.com>;
ccielab_at_groupstudy.com<mailto:ccielab_at_groupstudy.com>
> Subject: RE: Translation-rule problem
> Date: Fri, 6 Apr 2012 01:59:56 +0000
>
> Hello,
>
> I think you're working off examples that are designed for POTS failover, but
you're attempting to get it working for VoIP only.
>
> http://www.cisco.com/en/US/docs/ios/12_3/vvf_c/dial_peer/dp_app_a.html
>
> You'll have much more flexibility using voice translation-rules and
profiles. They can be applied inbound and outbound. I'm not very fluent with
num-exp, but I think you could accomplish your goal using that as well. Using
the logic you have below, here's what I would use on R2. You can apply similar
logic to R1.
>
> voice translation-rule 3334
> rule 1 /^55553/ /3/
> voice translation-profile inbound_from_r1
> translate called 3334
> dial-peer voice 1 voip
> destination-pattern 1...
> translation-profile incoming inbound_from_r1
> session target ipv4:172.16.200.1
> incoming called-number .
>
> test voice translation-rule 3334 55553334
> Matched with rule 1
> Original number: 55553334 Translated number: 3334
> Original number type: none Translated number type: none
> Original number plan: none Translated number plan: none
>
> -ryan
>
> -----Original Message-----
> From: nobody_at_groupstudy.com<mailto:nobody_at_groupstudy.com>
[mailto:nobody_at_groupstudy.com]<mailto:[mailto:nobody_at_groupstudy.com]> On
Behalf Of Iam Here
> Sent: Thursday, April 05, 2012 9:33 PM
> To: ccielab_at_groupstudy.com<mailto:ccielab_at_groupstudy.com>
> Subject: Translation-rule problem
>
> I have the Following topology for 2 CUCME
>
> phone_1111 Phone_3333
> | ---R1 ------------------------------R2 ---|
> Phone_1112 Phone_3334
>
>
> I configured R1 so that when Phone_1111 dials 3333 or 3334 numbers the a
translation rule converts it to 55553333 or 55553334 and send it to R2 then
the translation rule on R2 convert the 55553333 or 55553334 to 3333 or 3334
but it always gives me busy
>
> I think there is something wrong in the config below , (Sorry I am not
expert in the voice )
>
> R1
> ==
> translation-rule 1
> Rule 1 ^3 55553
>
> dial-peer voice 2 voip
> destination-pattern 3...
> translate-outgoing called 1
> session target ipv4:172.16.200.2
> !
> dial-peer voice 5555 voip
> destination-pattern 55553...
> session target ipv4:172.16.200.2
>
> R2
> ===
> translation-rule 3334
> Rule 1 ^55553 3
>
> dial-peer voice 1 voip
> destination-pattern 1...
> session target ipv4:172.16.200.1
> !
> dial-peer voice 3334 voip
> destination-pattern 3...
> translate-outgoing called 3334
> incoming called-number .
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html

Blogs and organic groups at http://www.ccie.net
Received on Fri Apr 06 2012 - 03:16:05 ART

This archive was generated by hypermail 2.2.0 : Tue May 01 2012 - 08:20:45 ART