Has anyone experienced an issue in UCCE 7.2, where the calls answered does not seem to be reporting correctly? In this case we are seeing that the calls answered figure, is less than the call handled. The Handled figure seems to be correct when you take into consideration the calls offered, error calls, abandoned calls etc. Webview historic call type reports are reporting what is in the Call Type Half hour tables so not an issue with webview. We have tried to replicate various scenarios but cannot replicate the instance where the answered call is not counted. We have also reviewed the ICM scripts but have drawn a blank.
I have attached a copy webview report that shows the disparity we seem to be having. Any ideas would be much appreciated.
- Calls Answered value increments when the call has been answered (the moment the agent picks up the phone).
- Calls Handled value increments when the call has been handled, in Cisco terminology, the wrapup state has ended.
If you take into consideration a simple fact, that a call may be answered within one reporting interval (in UCCE 7.2.x it's 30 minutes), and "handled" in the next interval, you can easily see two different numbers.
For instance, six customers call between 10:00 and 10:30. All calls are answered by an agent the moment they arrived. Five calls end before 10:30. But one of them is a demanding customer, and the call ends at 10:40. What you'll see is 6 for CallsAnswered but only 5 for CallsHandled.
Of course, CallsAnswered may be less than CallsHandled, too, it simply means there were calls that were answered within the previous reporting interval but handled in this interval.
We are looking at entire day. Would expect a small disparity over the midnight period, but that is not the case here. The logic is that a call will appear as answered first, before it is handled. We are seeing the call correctly counted as handled but not counted as answered.
No. The figures telly with what in the Call Typ Half Hour table. So not a Webview issue. We have no Outbound or EM or EIM. The call type report is reporting at a call type just before it quues to skill so no IVR involved either
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...