mismatch in userstats report in vicidial

[maninutech]

Hi, Matt
We are facing serious issue in reports, below are my observations

We have compared the value with User stats report,we are getting extra value in agent activity report(PAUSE+WAIT+TALK+DISPO) compared to user stat
Total login/logout duration. We are getting 50% users reports accurate and inbound_manual and auto dialer both dial method we are facing this issue.

we are unable to find the extra value .kindly help us to resolve the issue.

URL:
http://ipaddress/vicidial/user_stats.php?user=

Example :
AGENT LOGIN/LOGOUT duration = 07:32:11
AGENT ACTIVITY FOR THIS TIME PERIOD(PAUSE+WAIT+TALK+DISPO) =07:33:16


Below find the screenshot for your reference
Screenshot (AGENT LOGIN/LOGOUT):


Screenshot(AGENT ACTIVITY FOR THIS TIME PERIOD)


AGENT ACTIVITY FOR THIS TIME PERIOD download

https://drive.google.com/file/d/0B-xVlz1tqNLeVXJDSUFiU01iX1U/view?usp=sharing



Multi-server system
1 DB
2 Web server/ Dialer server

VERSION: 2.12-549a |BUILD: 160404-0940 | ViciBox Redux v.6.0.4 | Asterisk 1.8.32.3-vici |

Regards,
K.manikandan

[mflorell]

Are these reports being run on the same day or the day after the activity?

[maninutech]

day after the activity.

[williamconley]

Your images are missing.

Also I'm unclear on your question: Do you expect the login/logout time difference to mesh perfectly with the detailed items on another report?

We need the precise sections and totals you're trying to match to help (start with URL and copy past the headline and subtotal as text for each section in a "code" block if you can not post the images).

Do note that different reports come from different logs with different points of view, and they will never match if they are from different logs. User Stats timeclock will never match Agent Detail logs, for instance.

[maninutech]

URL: (Both the report on the same URL)
http://ipaddress/vicidial/user_stats.php?user=

User has done proper login and logout but still in the agent activity report total duration is not matching with Agent login and logout report duration.
and we are not using time clock login

AGENT LOGIN/LOGOUT TIME

----------------------------------------------------------
EVENT |DATE |HOURS:MM:SS|
-------------------------------------------------------------
LOGIN |2017-01-23 11:51:56" | |
----------------------------------------------|----------------
LOGOUT |23-01-2017 14:16 |02:24:14 |
------------------------------------------- ---------------- |
LOGIN |2017-01-23 14:16:19" | |
----------------------------------------------|----------------
LOGOUT |23-01-2017 17:26 |03:10:22 |
--------------------------------------------------------------|
LOGIN |2017-01-23 17:26:53" |
-----------------------------------------------|---------------
LOGOUT |23-01-2017 19:24 |01:57:35
--------|--------------------------|-----------|--------------
TOTAL | | 07:32:11 |
----------------------------------------------------------------


AGENT ACTIVITY FOR THIS TIME PERIOD:
----------------------------------------------------------------
PAUSE |WAIT | TALK| DISPO | Total
--------------------------------------------------|-------------
04:11:15| 01:00:47| 01:10:22| 01:10:52 | 7:33:16
--------------------------------------------------|--------------


in the above example login/logout total duration is 07:32:11 and agent activity report login duration 7:33:16 value is not matching. around 00:01:05 extra we are getting in the agent activity report.

[santhuarnold]

Any finding??
we are also facing the same issue. login-logout is proper and more 2-3 minutes difference in total value.

[maninutech]

not yet.........

Can any one please help me on this

[williamconley]

Do note that different reports come from different logs with different points of view, and they will never match if they are from different logs. User Stats timeclock will never match Agent Detail logs, for instance.

These will never match. They are from different logs. The only way you'll ever get a match is to pull two reports looking at the same data. At the end of a call and during switching these values are updated with the information available at the time of the update. Sometimes they have been rounded, sometimes there has been a 1-2 second delay in switching a call from A to B, which isn't logged. This happens more often in a heavy-use system. Even logging in can take a second or two before the "pause" meter kicks in. It's like trying to get the odometer on your car to agree with the distance Google says you drove. Both highly accurate and arguably correct, but never match because they approach from different angles.