In Historical Reporting, if we look up a queue's average wait duration for the day we are given 5:34.
At the same time, if I pull up avgWaitDuration in RtCSQsSummary, I am given 190505. What number is this? Seconds? if in seconds, and the total calls answered for that queue is 248, then I should be able to divide 190505 by 248. When I do that, I get 768 seconds. 768 (12:48) is a far cry different from 334 (5:34). Where am I going wrong?
Ok, I determined that the number is not actual ASA, but apparently "avg queue time". I assume this to mean the clock starts when the caller is placed in the queue, after completing the call tree.
I figured out how to calculate the time provided, and it matches the time in History Reporting for the "avg queue time". But the time we ACTUALLY want is the "avg speed to answer", as found in History Reporting for each queue.
What table would I find the ASA from the time the caller enters the call tree?
The 2021 IT Blog Awards, hosted by Cisco, is now open for submissions. Submit your blog, vlog or podcast by Friday, December 3.
To learn what's new in this year's competition or to gain insights into the judging considerations, check out t...
Greetings, Wanted to share a few lessons learned while migrating from a distributed to centralized IMP deployment. Our current setup included many CUCM/IMP distributed clusters with centralized Expressway server for MRA login. We did not wish to perf...
Parsec's Cisco UCCE/PCCE CC Connector application for CRM works as a bridge between the CRM and Cisco UCCE/PCCE CC solution.The CRM can be any cloud based CRM like Salesforce (SFDC), ServiceNow ,MS Dynamics or a 3rd party CRM.The CRM user/Agent will have ...
It’s a feature which allows CUCM to determine whether the phone is in its home location or a roaming station.By enabling this feature users can roam from one site to another site and acquire the site-specific settings such as Codecs, MRGL, Call rout...