XFER with the value of nullstucked in vicidial_auto_calls

All installation and configuration problems and questions

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

XFER with the value of nullstucked in vicidial_auto_calls

Postby Op3r » Thu Aug 21, 2008 3:54 am

I observed that a lot of data with XFER status in the vicidial_auto_calls with the value of null are being stucked. This affects the transfers of calls to the agents waiting. so as a work around I usually issue this command to the mysql

Code: Select all

delete from vicidial_auto_calls where isnull(channel) and status='XFER';




I think this is very much prevalent when using manual dial on VICIDIAL agent interface.

Any clues on how to resolve this?
Get paid for US outbound Toll Free calls. PM me. visit https://stopmanualdial.com for vicidial services.
Op3r
 
Posts: 1432
Joined: Wed Jun 07, 2006 7:53 pm
Location: Manila

Postby mflorell » Thu Aug 21, 2008 7:44 am

There must be another reason other than just MANUAL dialing, we have a client with about 100 manual dial agents and this is not a problem at all.
mflorell
Site Admin
 
Posts: 18406
Joined: Wed Jun 07, 2006 2:45 pm
Location: Florida

Postby Op3r » Thu Sep 18, 2008 6:42 pm

for posterity sake here's what fixed it.

we should always double check this line

exten => h,1,DeadAGI(agi://127.0.0.1:4577/call_log--HVcauses ... UG-----....

It should be one line not like this

exten =>
h,1,DeadAGI(agi://127.0.0.1:4577/call_log--HVcauses ... EBUG-----${HAN ...
Get paid for US outbound Toll Free calls. PM me. visit https://stopmanualdial.com for vicidial services.
Op3r
 
Posts: 1432
Joined: Wed Jun 07, 2006 7:53 pm
Location: Manila


Return to Support

Who is online

Users browsing this forum: Google [Bot] and 63 guests