vicidial.org

quick question.

1. What causes the vicidial_auto_calls table to get populated with numbers that do not get dialed. I've had to clear vicidial_auto_calls every couple days because "stale" entries would fudge the dial-level.


asterisk - 1.2.14
vici - 2.0

Same here I have to clear out the vicidial_auto_calls table everyday before that start of the shift and sometimes during the calling period

Did you guys have that exten = h part?

that helps a lot u know. I got that before.

Do you have also have the AST_reset_mysql_vars.pl script in your crontab during off-hours? This script will remove all vicidial_auto_calls records for a server(along with other things).

yes I run that script nightly (after agents close down).

-Art

This is prob. with me also....Sometimes calls are stop coming and when i clear the vicidial_auto_calls it start again. In previous ver. this kind of prob. was not there but in this version it is there wht to do for solving this prob.

Thanks.

What do you have in the "h" ecten in extensions.conf?

Me too is having below entries...

exten => h,1,DeadAGI(call_log.agi,${EXTEN}) ; DeadAGI is new
exten => h,2,DeadAGI(VD_hangup.agi,${EXTEN})

Pls. anybody help to solve this prob.

Have you tried manually dialing those numbers to see if they exist?

can you post the first 4 digits of some of these numbers?

Ya i tried doing this manuly dial it`s working but after some some times i need to flush database...You need first 4 digit of the numbers which are dialed ? I will send u asap........

Hi Matt, and everyone else...


Matt do you think this issue is the same that affects VICIDIAL when doing large outbound broadcasts as we disccussed in a previous thread? If so it should be solved by making the crontab entry of AST_reset_mysql_vars.pl execute a little bit more often. Would you agree on this?

Nope, this is a different issue from the outbound broadcast issue. I have not noticed this kind of problem on any of my 100+ seat call center installations, which is what leads me to believe it is a leads-filtering issue or a configuration issue of some kind.

I see.. I guess i got carried away when i saw the dial level being messed and all that. I'm still trying to figure that one out. Thank a lot!

Still my problem is not solve. Plz. anybody there to solve my prob. this is very serious problem for me.

Pls. help Pls. help Pls. help

please check carefully your dialplan.. as this is happen to me when i upgrade to fastagi.. but now i dont experience it.

Pls. if you can share your mistake which u have made so that i can check that also. Thanks...

just make sure you have a correct dialplan, i letter or comma will end up not hanging the calls.. check your "AGI(agi://127.0.0.1:4577/call_log)" make sure this is in the right place.

Below is my dial plan :


exten => _1XXXXXXXXXX,1,Dial(SIP/${EXTEN}@provider,60,tTo);
exten => _1XXXXXXXXXX,2,Hangup();



exten => h,1,DeadAGI(call_log.agi,${EXTEN}) ; DeadAGI is new
exten => h,2,DeadAGI(VD_hangup.agi,${EXTEN})

Correct me if i am wrong .
Thanks

just as i expected you must put this:

exten => _1XXXXXXXXXX,1,AGI(call_log.agi,${EXTEN})
exten => _1XXXXXXXXXX,2,Dial(SIP/${EXTEN}@provider,60,tTo);
exten => _1XXXXXXXXXX,3,Hangup()

exten => h,1,DeadAGI(call_log.agi,${EXTEN}) ; DeadAGI is new
exten => h,2,DeadAGI(VD_hangup.agi,PRI-----NODEBUG-----${HANGUPCAUSE}-----${DIALSTATUS}-----${DIALEDTIME}-----${ANSWEREDTIME})

you did not follow the scratch install in 2.0.1

Thanks it is solve after putting agi before extensions.

Thanks

please post an example of how you resolve this issue, because I am having the same issue myself.

txs

this thread is 5 years old. the cause, however, was always that the calls got lost and were never deleted. and the solution is already posted by gerski