My understanding of the Cisco dial plan is that when using the 9.@ numbering plan and the gateway settings are set to callmanager. The ccm tries to set the calling number type correct but when using explicit matches such as 9.1xxxxxxxxxx the ccm does not know what to mark it so it marks it unknown or you can mark it whatever you want on the gateway page but it will apply to all calls. This does not seem like a good setup to me so I hope I am missing something. It seems there should be a way to mark the calling number type in the route pattern or something. So your international calls will be marked correct etc.
If this is not the case I am trying to come up with other work arounds. I was thinking of making a voice translation rule that would correctly mark the calls and apply it directly to the voice port but I am not sure how that would work in MGCP mode since the q931 is backhualed to the CCM.
Try using different partitions and assign the route patterns to the partitions (local, LD, Int'l, blocked, toll-free, etc.) When the route pattern is a best match the call will be categorized as such in the RTMT and CDR logs.
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: email@example.com 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 ...