Run the query against the CCM03xx database, where xx is the highest-numbered database on the CallManager. There are two databases on the CallManager publisher: CCM03xx and CDR. The former is the configuration database, and the latter contains the CDR and CMR.
When you first install CallManager, the first database will be called CCM0300. Each time you upgrade the CallManager, the last two digits of the database number increase by 1; so the first time you upgrade your current configuration database will be CCM0301. CallManager keeps the previous configuration database around, so you will generally have two configuration databases there.
Just choose the most recent configuration database and run the query, which in your case looks like it might be CCM0301, but if there is a CCM0302 then use that one!
Try a query such as:
select softwareComponent, version
where softwareComponent = 'Cisco CallManager'
That should return the version in the version column for each process node (that is running CallManager, so the publisher and any subscribers).
You could also try something like this, if you are interested:
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...