Secondly are you using any 3rd party software that uses this data to do reporting or logging? If so then whats probably happening is that the 3rd party application is taking the data and then wiping it from the SQL DB on the Cisco box.
Cisco pre-requisites for any 3rd party vendors when they extract data from the CDR SQL DB is to wipe it immediately from the Cisco Box. This is one of Ciscos constraints and although im not sure why they do this I can only imagine they do this to stop any discrepanices between 3rd party reporting tools and their on DB archives to elimate duplication or spurious data.
I am not certain why the records are not being written to the CDR database but you can check two things. First, on the publisher go to:
Then open the SQL MMC tree. When you get to databases open the CDR database and click once on tables in the left panel. Right click on the CDR table in the left and open table and return all rows. All of the rows in the CDR table should be displayed. If no records are displayed, you are not writing to the CDR database. CDR records are written to the primary CallManager then copied to the publisher (after a default period of 60 seconds).
CAR uses its own database extracted from the CDR database. That is the CAR database. Open it from the SQL enterprise manager MMC tree in the same manner as you did for the CDR database. You should see records in the CAR database.
Take care that you change no data when looking at records! This is a read and write screen.
From the error message you copied it seems to indicate that data is there but not for the range you specified in the report. In the past when I have done this I just did not see data in the report if none was recorded for that period. Sorry I dont know what the error message specifically means.
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...