As CRS runs, it stores call activity data in databases on the CRS server or the Historical Reports Database Server, if one is set up. The Cisco Historical Reports client is used to create historical reports based on this data.
To schedule a historical report means the Cisco CRS Historical Reports client needs to be instructed to automatically generate the report in the future.
I don't have a problem pulling the reports. What I need to know is: for reporting purposes, we do not want calls that are less than 15 seconds in length counted as a dropped call. Is there any way to change the dropped call threshold from 3-5 seconds to 15 seconds?
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...