Length of Outbound calls sometimes shows 10digits.

[glen20web]

Hi Guys,

Can anyone explain to me why, some call length are showing 10digits instead of seconds?
When we check call dispo like "N" - No Answer for any agents. sometimes the lenght shows like this:

Code: Select all

OUTBOUND CALLS FOR THIS TIME PERIOD: (10000 record limit)     [DOWNLOAD]
#   DATE/TIME   LENGTH   STATUS   PHONE   CAMPAIGN   GROUP   LIST   LEAD   HANGUP REASON
1   2017-07-31 11:07:34   18   N   6029783565   MED3   med3   532104000   46343557   CALLER
2   2017-07-31 10:50:45   1501511676   N   5408548662   MED3   med3   532148000   49251520   CALLER
3   2017-07-31 10:32:52   48   N   3158942028   MED3   med3   632236000   51039519   AGENT
4   2017-07-31 09:57:15   1501507539   N   8436658291   MED3   med3   632243000   51405165   AGENT
5   2017-07-31 09:55:59   30   N   9184566051   MED3   med3   632238000   51151922   AGENT
6   2017-07-31 09:47:48   14   N   3193452500   MED3   med3   632114000   49930322   AGENT


For agent activity and recording time period it shows properly the seconds.

agent activity:

Code: Select all

AGENT ACTIVITY FOR THIS TIME PERIOD: (10000 record limit)     [DOWNLOAD]
    these fields are in seconds   
#   DATE/TIME   PAUSE   WAIT   TALK   DISPO   DEAD   CUSTOMER   STATUS   LEAD   TYPE   CAMPAIGN   PAUSE CODE
1   2017-07-31 11:07:31   0   3   18   3   0   18   N   46343557   A   MED3   
2   2017-07-31 10:50:45   0   2   18   19   0   18   N   49251520   A   MED3   
3   2017-07-31 10:32:53   0   1   47   27   0   47   N   51039519   A   MED3   
4   2017-07-31 09:57:15   0   1   19   2   0   19   N   51405165   A   MED3   
5   2017-07-31 09:55:35   0   25   29   3   0   29   N   51151922   A   MED3   
6   2017-07-31 09:47:44   0   4   15   4   0   15   N   49930322   A   MED3   
TOTALS   0   36   146   58   0   146   

recording:

Code: Select all

RECORDINGS FOR THIS TIME PERIOD: (10000 record limit)     [DOWNLOAD]
#   LEAD   DATE/TIME   SECONDS     RECID   FILENAME   LOCATION 
1   46343557   2017-07-31 11:07:35   17   3145342   20170731-090734_6029783565   http://192.168.2.236/RECOR... 
2   49251520   2017-07-31 10:50:47   18   3140701   20170731-085046_5408548662   http://192.168.2.236/RECOR... 
3   51039519   2017-07-31 10:32:55   45   3135869   20170731-083254_3158942028   http://192.168.2.236/RECOR... 
4   51405165   2017-07-31 09:57:17   18   3126393   20170731-075716_8436658291   http://192.168.2.236/RECOR... 
5   51151922   2017-07-31 09:56:01   28   3126050   20170731-075559_9184566051   http://192.168.2.236/RECOR... 
6   49930322   2017-07-31 09:47:49   13   3124262   20170731-074748_3193452500   http://192.168.2.236/RECOR... 


Is there a way to fix this?
thanks

[mflorell]

Something is getting missed int he logging process.

What is the version and build of your vicidial.php?

What kind of campaign is this?

[glen20web]

hi mflorell,

its an outbound campaign.

We are using this version and build on a cluster 1x DB and 5xdialers.
Vicibox 7.0 from Vicibox_v7.x86-64-7.0.4.iso | Vicidial 2.14-616a Build 1705527-0041

[mflorell]

Try upgrading to the latest svn/trunk. There is a logging bug that was fixed a month after the version you are using that may fix this issue for you.

[glen20web]

Hi mflorell,

We are using svn revision: 2761. Is this not the latest svn?

Just need to confirm also if rev.2761 is not the latest, I will just use vicibox-upgrade on the database server first prior to the rest of the servers right?
Is this the only step to do for upgrading after doing a backup on asterisk?

[mflorell]

Nope, we are on svn revision 2798 at the moment.

To upgrade, you should just need to follow the UPGRADE document instructions that are in the main source directory.

[glen20web]

Hi mflorell,

Sorry, just got back. I've been tuning our mysql mariadb10.1.20 to reduced memory usage.

where exactly do i check the UPGRADE docs?
Are you referring in this location

Code: Select all

/usr/src/astguiclient/trunk

because i check there and nothing is relevant to svn upgrade.

Can i just do this then do the same thing after the database got updated.

Code: Select all

cd /usr/src/astguiclient/trunk
svn up

[mflorell]

Yes, run an "svn up" then look at the UPGRADE document