If I recall correctly, it's easy in CVP 3.1. Stop the CVP VXML Service. Start CVP VXML from the command line (in Tomcat bin use startup.bat) and look at the window - it will say how many ports you own. Stop it with shutdown.bat then go back to your service. You can probably see this info in Tomcat\logs\stdout logs.
Call Server licence files are readable.
In CVP 4.0 it's a little harder as Cisco decided that they don't want you starting Audium Call Services from the command line, mainly because of the Ops Console. If you try startup.bat it will complain about your Java environment variables. You can fix this, but you need to know your business.
But Tomcat is probably writing the info somewhere. Just a second ... mmm, the stdout files in C:\Cisco\CVP\VXMLServer\Tomcat\logs do show the startup stuff, but the port count is not there. Sometimes I wonder why they change things.
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...