07-03-2007 08:31 AM - edited 03-14-2019 10:23 PM
Hello,
I'm trying to route the calls made by the extension 18 to a determinated port. For example if the extension 18 dial 0977xxxxx the call have to go to the port 3/1 and the if the extesions 1x dial 0977xxxx have to go to the port 3/0
Based on the cisco document
I made this config:
voice translation-rule 6
rule 1 /^0/ /77/
voice translation-profile prova2
translate called 6
dial-peer voice 5 pots
description Trucades Exterior
translation-profile outgoing 5
destination-pattern 0T
direct-inward-dial
port 3/0
!
dial-peer voice 6 pots
description Trucades Exterior
destination-pattern 77T
direct-inward-dial
port 3/1
dial-peer voice 567 voip
translation-profile incoming prova2
answer-address 18
when the extension 18 dial 0977xxx, the call goes out to the port 3/0.
As you can see on this document:
http://cisco.com/en/US/tech/tk652/tk90/technologies_tech_note09186a008010fed1.shtml
answer-address have more priority than destination-pattern.
I tried to apply the translation-profile direct to the ephone-dn without success.
Gerard
07-03-2007 10:30 AM
Hi Gerard,
In fact you may have problems with translation-profile applied to ephone-dn, sometime these don't work.
And, DP voip with answer-address will never work, because the actual incoming DP is one automatically created by ephone-dn.
So, to associate an FXO port to an extension, use the command "trunk" in ephone-dn mode.
It is in the CCME command reference.
Hope this helps, please rate post if it does!
07-03-2007 11:23 PM
Hi,
The DP pots are over basic digital lines, seems that the "trunk" command on the ephone-dn its only for FXO ports.
Is it correct?
regards
07-04-2007 07:20 AM
I'm afraid it is, you could try anyway.
On the other hand, which IOS are you using? The translation-profile method should work as well modulo any bug.
07-04-2007 07:43 AM
The IOS version is 12.4(11)T. I will try the trunk command tomorrow and let you know.
Regards
07-04-2007 07:50 AM
Once you are there, please try also 12.4(11)XJ3 for translation-profile under ephone-dn. This release fixes many many bugs in telephony.
07-04-2007 04:45 PM
Not too sure if this might help but i configured something like this for private lines on a T1. basically i did the same as above but in the route pattern i inserted the prefix as well.
therefore, when extension X dials a number it hits the route pattern with say 28 as the prefix and then matches the relevant DP with 28T (in my case) and then goes through that port. i also restricted it for that extension alone to use that port by using CSS and Partition to associate only with that extension
07-04-2007 04:50 PM
Hi A.
This is about CME, not CCM.
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