04-05-2012 06:32 PM - edited 03-16-2019 10:30 AM
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 .
04-05-2012 07:57 PM
Rules are wrong, I recommend you to start by reviewing the configuration guides which you can find on CCO just by searching translation rules.
http://www.cisco.com/en/US/partner/tech/tk652/tk90/technologies_tech_note09186a0080325e8e.shtml
There are plenty of examples in the first link.
HTH
java
if this helps, please rate
www.cisco.com/go/pdihelpdesk
04-06-2012 02:30 AM
Hi,
You need to match the incoming pattern on CME-R2
Try adding this to CME-R2
!
telephony-service
dialplan-pattern 1 55553... extension-length 4 extension-pattern 3...
!
Now when a call with 55553333 comes in to R2 it should find and match DN 3333
Regards
Alex
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