How AutoDial Works
Posted: Sun Jul 30, 2017 6:26 amHello,
This is what I understand:
1. /usr/share/astguiclient/AST_VDhopper.pl - is used to add leads to Hopper so that call-back can happen.
2. the select query in AST_VDhopper.pl uses: ...SELECT count(*) FROM vicidial_list FORCE INDEX(list_id) where called_since_last_reset='N' and status IN('DROP','NCE','NCR','NEW') ... this checks status as set in the campaigns.
3. However, auto-calls also have status such as NA, AFAX, ADC, ADCT etc.
4. How are these status' and leads filled back into the hopper for auto-calling? That is what script / configuration can help add these to the hopper?
Here is what I want to achieve:
1. Auto statuses such as NA, AFAX, ADC, ADCT etc. need to be called to a maximum limit and with a pre-defined interval between calls.
My version:
Scratch Install | Vicidial 2.14-617a Build 170529-2320 | Asterisk 1.8.23.0-vici | Dual Server | No Digium/Sangoma Hardware | No Extra Software After Installation | x86_64 | Intel Xeon CPU E3-1225 3.30GHz
This is what I understand:
1. /usr/share/astguiclient/AST_VDhopper.pl - is used to add leads to Hopper so that call-back can happen.
2. the select query in AST_VDhopper.pl uses: ...SELECT count(*) FROM vicidial_list FORCE INDEX(list_id) where called_since_last_reset='N' and status IN('DROP','NCE','NCR','NEW') ... this checks status as set in the campaigns.
3. However, auto-calls also have status such as NA, AFAX, ADC, ADCT etc.
4. How are these status' and leads filled back into the hopper for auto-calling? That is what script / configuration can help add these to the hopper?
Here is what I want to achieve:
1. Auto statuses such as NA, AFAX, ADC, ADCT etc. need to be called to a maximum limit and with a pre-defined interval between calls.
My version:
Scratch Install | Vicidial 2.14-617a Build 170529-2320 | Asterisk 1.8.23.0-vici | Dual Server | No Digium/Sangoma Hardware | No Extra Software After Installation | x86_64 | Intel Xeon CPU E3-1225 3.30GHz