by scopor » Tue Jul 08, 2014 4:51 pm
As suggested by William I have attempted an upgrade of vicibox 5 to the latest svn trunk. This did not solve the data discrepancy I reported earlier. I have downloaded and installed vicibox 6 standard iso on a 64bit intel Pentium 3.10GHz Dual Core CPU as a test install. No additional hardware/software is installed.
My version is as follows.
Version: 2.10b0.5
SVN Version: 2148
DB Schema Version: 1384
DB Schema Update Date: 2014-07-06 03:49:47
I am still having the same issue. Let me try to explain the issue in as much details as possible. I am placing inbound test calls to the server and logged in as an agent. I logged in at 17:28pm the following entry is made in the vicidial_agent_log.
65, 7425, 172.16.50.43, 2014-07-08 17:28:06, , TEST, 1404854886, 0, 1404854886, 0, , 0, , 0, , ADMIN, , LOGIN, , 0, N, , AGENT
I placed an inbound test call to the queue and took that call as the logged in agent. Look at the same entry above with additional information being written to it. Note that it did not create a new entry but added data to the first entry.
65, 7425, 172.16.50.43, 2014-07-08 17:28:06, 21, TEST, 1404854886, 61, 1404854947, 74, 1404855021, 21, 1404855042, 6, XFER, ADMIN, , LOGIN, , 0, N, 1404855021.60, AGENT
I then ended and dispositioned the call. Look at the new entry created in the vicidial agent_log file (66). Note that there is no repeat of the uniqueid to indicate that the call had ended.
66, 7425, 172.16.50.43, 2014-07-08 17:30:48, , TEST, 1404855048, 0, 1404855048, 0, , 0, , 0, , ADMIN, , , , 0, N, , AGENT
In the line above note that the uniqueid is missing. The time stamp of 17:30 is when the call ended and the call lasted 21 seconds which is reflected in the modified line 65. The interesting thing is this, if I place a new call as you would see from the entry below, the time stamp of 17:30 is retained and a new uniqueid is added with additional data representing this new call. So it would appear that this new call has started at 17:30 when in fact the call started at 17:44 as indicated in the new entry on line 67.
66, 7425, 172.16.50.43, 2014-07-08 17:30:48, 22, TEST, 1404855048, 0, 1404855048, 826, 1404855874, 13, 1404855887, 3, INQ, ADMIN, , , , 0, N, 1404855873.65, AGENT
67, 7425, 172.16.50.43, 2014-07-08 17:44:50, , TEST, 1404855890, 0, 1404855890, 0, , 0, , 0, , ADMIN, , , , 0, N, , AGENT
Line 67 shows the start of the new call without the uniqueid, while line 66 which has the time the previous call ended and the the uniqueid of this new call that started at 17:44.
Is this a bug in the way the system logs these calls? Any expert opinion here would be helpful as we are trying to generate our own reporting from the raw data but we can't do that if the raw data is skewed.
I will appreciate any assistance or guidance. I hope I have provided enough information and that it was clear and concise.
Cheers.
Last edited by
scopor on Tue Jul 08, 2014 5:26 pm, edited 1 time in total.