2.0.5 - problem with useronly callbacks

All installation and configuration problems and questions

Moderators: gerski, enjay, williamconley, Op3r, Staydog, gardo, mflorell, MJCoate, mcargile, Kumba, Michael_N

2.0.5 - problem with useronly callbacks

Postby tukak » Wed Jul 08, 2009 3:41 pm

Hello,
we've upgraded to 2.0.5 this weekend and we are suffering from following problem :
When agent selects the callback from his lists of useronly scheduled callbacks, the fields in the form are filled with data from this lead (let's say it's lead A) and in a split of a second these fields are rewritten with data from another lead (let's say its's lead B, we believe it's anyone callback that is supposed to be called at the moment). Every field is rewritten but the phone_number field stays (we have the alter phone number disabled). Agent can then dial the lead and is conneted with the number from lead B. The callback from lead A is not scheduled anymore.

In the user_stats.php we than see two calls to the same number, but with different lead_ids. One of the call is 0 seconds long, the other one gets normal duration information.

Following error is then produced in the log :
2009-07-08 17:18:13|vdc_db_query|00057|1062|Duplicate entry '1247066268.18142' for key 1|INSERT INTO vicidial_log (uniqueid,lead_id,list_id,campaign_id,call_date,start_epoch,status,phone_code,phone

_number,user,comments,processed,user_group,alt_dial) values('1247066268.18142','987136','568','KAMPAN_1','2009-07-08 17:18:13','1247066293','DONEM','420','xxxxxx098','721','MANUAL','N','','MAIN');|

This doesn't happen everytime :-(

Do you have any idea, what could be wrong or some advice, how to debug, where to look while testing?

Thank you

Lukas
tukak
 
Posts: 34
Joined: Mon Jun 19, 2006 6:22 am

Postby mflorell » Thu Jul 09, 2009 12:13 pm

If it is a random occurance then it will be fairly difficult to fix.

If you want to try fixing it on your own you could try enabling the access_log in apache and see if you notice a double submission or something else at that time that might indicate the problem. You could also try changing the MySQL logging in vdc_db_query.php to 2 which generates a ton of logs of everything going on with the agent screen which also might help you in debugging the problem.
mflorell
Site Admin
 
Posts: 18406
Joined: Wed Jun 07, 2006 2:45 pm
Location: Florida


Return to Support

Who is online

Users browsing this forum: No registered users and 106 guests