vicidial.org

Hello,

We've noticed that the CRON job for loading the hopper is running at 5 minute intervals. The comments in the AST_VDhopper.pl file indicate that this script should be run every minute.

# SUMMARY:
# For VICIDIAL outbound dialing, this program must be in the crontab on only one
# server, running every minute during operating hours. For manual dialing
# campaigns, there is a campaign option for no-hopper-dialing that can operate
# without this script running, but the list size will be limited under that.
#

A few questions about this:

1) Why does the installer set it to run at 5 minute intervals?

2) What is the consequence of setting it to run at a 1 minute interval? Can we do this safely?

Any light you can shed on this topic would be appreciated.

Regards,

Peter Manley

Here are the specifics of our installation:

VICI version: 2.14-708a Build: 190414_0924
Linux Distro/Kernal version: SUSE Linux 4.4.176-06-default
PERL version: v5.18.2
Asterisk version: 13.21.1-vici
MySQL version: 10.2.23-MariaDB-log OpenSUSE package

cron entry should be like this * * * * * /usr/share/astguiclient/AST_VDhopper.pl the load of leads on the hopper will be faster and you will see a difference a huge difference on the amount of auto dial calls 4 time I would say faster, of course setting of the campaing also affect this

This is more of a design question. I'm wondering why the code and documentation indicate that the script is run every minute, but the installer sets it up to run every five minutes? Was this changed at some point in the past? And why?

The problem we are seeing is that if we reset the hopper, it is not re-loaded again until this CRON job executes. So, the hopper may be dry for up to 5 minutes (which means agents are waiting), depending on the timing of resetting the hopper. I think this is a flaw in the implementation. We can speed this up by increasing the frequency with which AST_VDhopper.pl script runs. Are there any potential side effects from doing this?