The problem is because of MIN_DATE and MAX_DATE values are not getting updated according to the processed CDR and CMR files. So whenever the report was tried to be generated, it used to throw the error "Data is not available in the Database".
The workaround is to update the MIN_DATE and MAX_DATE values manually in tbl_system_preferences table. Update the values of CDR_MIN_DATE and CDR_MAX_DATE for MIN_DATE and MAX_DATE respectively. Use the following queries to update the values
Update tbl_system_preferences set param_value = '
Update tbl_system_preferences set param_value='' where param_name='MAX_DATE'
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...