We have a dial plan that's growing in complexit as we add sites. We're using tail end hop off so that we can dial to a remote gateway and hit the PSTN without incurring LD charges. This is all fine and good, but the problem is that it's getting insanely complicated to document and configure.
I see the way Cisco documents it in their SRND (with CSSes, leading to partitions, leading to RLs, leading to RGs, leading to gateways. That's lovely, if you have like 10 route patterns. However, multiply that by about 10, and it quickly becomes almost impossible to document it all out (lines going everywhere etc.).
Anyone have an suggesions on how you can draw it out in an elegant way so that you could actually follow it? Utilities would be great if there was one. There's the old standby of Visio, but I'm just looking for a good way to tame this beast.
Any suggestions? What are people doing with REALLY complicated DPs?
In this example, we will be creating a national dial plan that corresponds to the Australian national numbering system. It should be a simple matter to apply these principles to any other country, provided they use a consistent numbering scheme for local and long distance calls.
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 ...