In the past, I have used a product called Variphy. It does a great job of auditing CUCM and Unity. But if you were to do it manually, Id start with:
- voice infrastructure High Level.
- voice infrastructure low level (detailed down to which switchport each component is plugged into and IP addresses
- move into a low level type document as if you were designing.
- Server names and naming convention
- Use the CUCM Admin page as your guide for the document (System, Route Plan, Devices, etc)
- The gatekeepers and gateways, you will need to break out. I typically copy and paste the running config to the document and then create RED next each line WHY it is configured this way. For Gatekeepers, you need to spell out each zone, naming convention used, route plan and end points, etc.
- Document the versions of the software used, etc.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...