Check your call type reports for a more accurate count on those numbers.
Set a "queuing call type" just before the queue to skill group nodes - by definition, a "queuing call type" will be the last in the series of call types (after you have peeled off holidays, after-hours etc. calls). No "flow out" from this call type.
if one call is queued to multiple skill groups, the number for the CallsQueued will be incremented for all of the skill groups. Same applies to the Calls
AbandonedInQueue column as well. It's quite logical - the system queues one call to two or more skill groups, and if the customer decides to hang up while in the queue, the call will be abandoned for all of the skill groups. Similar logic applies to the CallsOffered column, which is basically the number of calls that touched that skill group.
It's quite different, however, when it comes to AbandonRing or RONA - this is already past the queue, when the system already knows where to route the call to: to the agent.
Back to those numbers:
214 calls were queued (to all skill groups);
27 calls were abandoned (for all skill groups);
981 calls offered (~ touched the skill group).
Might be a bit confusing, but one needs to see this from the point of view of skill group, not calls.
I can only agree with Geoff, if you need to count calls as such, you need to insert call types into your ICM scripts, before sending calls to skill groups, or at any place where you want to measure the number of calls. The way I always explain this to a customer is: calltypes are basically turnstiles with a security officer standing next to them, keeping an eye on everyone going through the gate.
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...