Normally this information is stored within the corresponding call.
So in your case there are to attributes, that can be pulled from the database:
ca_call.ca_is_clock_stopped (Boolean) and ca_call.ca_clock_stopped (Datetime value)
There is one thing you need to remeber:
Everytime the clock is stopped and started again these value are overwritten. So you will only get the latest stop time or a null calue if the clock was started again.
I appreciate the values in the main module tables get overwritten which is why we use the audit table as start and stop clock are auditable functions, but my BI team claim these are not 100% accurate and we need a full history of the call in terms of clock running. Any other ideas gratefully received
Did your BI Team tell you, why they think the values are not 100% accurate?
I'd echo Fabian and ask your BI guys to double check. The audit trail is the definitive list of clock starts and stops.
Hi both, yes, I was already confident LANDesk is accurate and I've not yet looked too deeply into this, it was mainly to get the discussion rolling. They have today found an issue with their coding (I'm awaiting confirmation if this is what is causing the issue). Will post as soon as I know, and if the issue hasn't been resolved I will dig deeper as I believe its more to do with their understanding than LANDesk.