on 01-24-2014 03:21 PM
Thats what I thought about TAPI/JTAPI, and there is no way I can/will go that routeYou can use CTI (TAPI/JTAPI) to monitor the phones in real time and keep your own statistics (usually a pretty heavy solution) or use the CDRs.
I was going to try the get_file_list operation in that service with one hour interval which was sufficient in my scenario. But only after we resolve the self signed SSL issue complicated by the 1024 bit CSR limit by CUCM OS Admin.The CDRonDemand service can only receive single CDR files and there is a throttle limit, so it's usually impractical for anything but spot checking very specific time frames - e.g. examing when a 911 or malicious call was made.
That sounds the best option. I just need to research more on the CDR fields - what they mean - before I dump them to a SQL DB.If you want to keep large scale statistics, you will likely want to set up your app as a CDR FTP target, so that you receive all CDRs as they are generated (once a minute, default.) You can then import then into a database and query as needed.
The phone interprets a special URI like 'Application:Cisco/MissedCalls' as an instruction to use the built-in Missed Calls feature for providing the service. Missed/Placed/Received calls are recorded on the phone itself, and those display services are provided by an onboard phone routine.
But am I not doing the same thing via CDR reporting?Not possible. Historically this was for privacy/security reasons.
But am I not doing the same thing via CDR reporting?Not possible. Historically this was for privacy/security reasons.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: