I am trying to setup a translation-rule for all international calls (011) so that the type is changed to unknown. I need this to interface properly with my telco.
I've created the translation-rule fine as verified by the test command, but getting it to work when a call is actually made seems to not work.
I have a pre-existing translation-rule and profile in place to re-write the outbound DID for the calling number, and this is applied at the voice-port level (for simplicity on my part). I 'm not sure if this is causing the problem or it's something else.
Here is the config sections:
# convert extension # to DID for calling number
voice translation-rule 1
rule 1 /\(^33..\)/ /407745\1/
rule 2 /\(^35..\)/ /407745\1/
rule 3 /\(^43..\)/ /407284\1/
# match any calls beginning with 011 and change the call type
voice translation-rule 4
rule 1 /^011/ /011/ type any unknown plan any unknown
voice translation-profile OutboundCLIDasDID
translate calling 1
translate called 4
translation-profile outgoing OutboundCLIDasDID
dial-peer voice 200 pots
This setup isn't working. The 011 calls are still going out as the default of International.
I also tried applying a translation-profile on the the dial-peer 200 as such:
Hi! You've mentioned that calls go out through the wrong peer but we don't see a complete set of peers to tell what's wrong. But an outbound translation profile on an outbound peer cannot affect the peer selection. The problem is in matching patterns. Check your dial-peer dest patterns and also run "debug voip dialpeer ino" to determine what peer is selected and why. If you do translation on inbound peers you can run "deb voice translation". I also don't suggest to use translation on ports in general.
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: firstname.lastname@example.org Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...