Number differences between ccp_statserver and datamart db number for VQs

Hi Adam. CCP numbers are a lot better after reconfiguring stats using DCID as formula in ccp options, and using a time profile set as “00:00” too. Since a couple days ccp n_entered equals datamart (n_entered+n_abb_ring); ccp seems to add abandoned in ring calls to n_entered even if the stat uses only CallEntered as main mask (relative mask is empty, as for DMA stat); ccp process ver. 7.1.

A difference (~2%) remains on certain VQs used to transfer call back to IVR, and I still studying to figure how to use PEG for those VQs, 'cause I never did it before, so I’m trying to understand how to use KVP created with PEG in CCP. (client ver. 7.5).

Regards.

If connid changes then attach data would be lost also probably.
You sure ISCC is well configured and being used on all your transfers?

Enviado de meu E6633 usando Tapatalk

cav has a point - if you are losing the ConnID, you are probably losing all of the attached data - so a configured KVP “PEG” for reporting purposes might be useless in this scenario…

Good point, indeed; by the way, in this case, during the process in wich those VQs work, ConnID does not changes and attach datas remain on the interaction. The only difference between “regular” VQs usage and VQs usage in those strategies, consists in the fact that I use this VQs as “dummy counters”, placing two funct. blocks, one to count the event (SelectDN[‘VQ001’,0,‘’,StatSelectAny,‘’,‘’,‘’,‘’,‘’,‘’,‘’,‘’,‘’,‘’]), and the other to clear the target (ClearTargets[‘VQ001’]).

I think I understand - are you saying “regular” for those VQ’s which keep the ConnID - and non-“regular” VQ’s for where it loses the ConnID? Are you able to determine if it keeps the attached data, even if it loses the ConnID?

In truth, this now sounds more like a routing/ERS/URS/ORS issue than it does a reporting issue. I think, once you have cleared up the mystery of losing the ConnID, your stats will probably fall into line…

Regular is a selectdn over groags+vq that routes call on a destination target (agent in agent group, event counted on vq).

“Non regular” is a selectdn over a vq to count n_entered calls in a strategy that sends the call in another strategy, instead of a groag/ag target.

In both scenarios ConnID usually does not changes, it changes rarely, after a play block I regularly use to play agent id. By the way, the ConnID change seems not to affect numbers.

??? ??? ???
but you said DCID did changed numbers, meaning, you had repetitive interactions going on…
Changing ConnID does affect as said, would be counted as 2 instead of 1…that shouldn’t happen and you should focus on the WHY. Isolate the scenario and fix it

Actually… it makes sense :-[

I’ll try to isolate duplicated instances.