We have a pretty straigh forward dial plan in place for our client but as of late have ran into a little snag that affect one user in particularly, which just so happens to be the VP of the organization.
8.@ pattern for outside access, provide outside dial-tone. Certain users (including VP) are configured with two DN's on their phones. The phone is configured for forward busy call the second DN, and forward no answer go to unity voicemail.
VP's DN : 800
VP's DN2 : 400
Problem is when VP's DN is dialed from both internally and externally (DID) we roll straight to HIS voicemail without rolling to the 400 DN and then to voicemail. Not ringing the 800 extension on the phone at all.
Unfortunately the client has an extremely deranged dial plan in place and would not budge from it since they had ordered DID blocks prior to the telephony system.
I am almost certain that the 8.@ pattern and the 800 DN are in conflict someway and we currently have a P2 TAC case open on this right now.
Here is the snippet from the trace, and as you will see CCM is forcing a Long-Distance Operator Tag when matching for some reason. There are no route filters configured for the 8.@ pattern either.
In this case, CallManager is operating properly. "00" is an escape to the long distance operator, and it is matching the 8.@ Route Pattern instead of the 800 DN belonging to the VP.
As a workaround, if you never need to escape to the long distance operator through the "00" code then you can configure a Route Filter for your 8.@ Route Pattern (or if you already have a filter applied, add another parameter to it) and say where LONG-DISTANCE-OPERATOR DOES-NOT-EXIST, and if this is a new route filter, then apply it to your 8.@ pattern.
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 ...