Leads in Hopper automatically reseting to 0

[saqibali]

Hi all

i am having problem with the leads in the Hopper. e.g if i set the hopper level to 500 then the filed leads in hopper will be displayed as 500 leads to be dialed but after some secs it again set to 0 .

i am using vicidial 2.0.2
my dial level is 2
asterisk 1.2.18
zaptel 1.2.21

i have two asterisk/vicidial and one DB server.

[eliasferreyra]

please upgrade to 2.0.4 and all your problems will be solved

[saqibali]

this is the only way to solve this problem ????/

[eliasferreyra]

thats that i recommend to you


check the calltimes

and check the status put the new

and verify the dial prefix

[saqibali]

The VD_hopper script is running but it will not add leads to the current lead set. like below it shows 1897 leads in the hopper and suddenly it shows 0 leads in hopper and after five or ten secs again the hopper is filled with leads. thats what i am facing right now ...

DIAL LEVEL: 3
TRUNK SHORT/FILL: 12 / 0
FILTER: 1234 TIME: 2008-05-21 12:20:45
DIALABLE LEADS: 174445
CALLS TODAY: 26844
AVG AGENTS: 88.2
DIAL METHOD: ADAPT_AVERAGE
HOPPER LEVEL: 2000
DROPPED / ANSWERED: 52 / 7597
DL DIFF: 17.5
STATUSES: NEW, A, NA, N, DROP
LEADS IN HOPPER: 1897
DROPPED PERCENT: 0.68%
DIFF: 19.84%
ORDER: DOWN COUNT

[eliasferreyra]

letme know the cron file

and letme see the mutt logs

[saqibali]

thats the cron file of the primary server

### recording mixing for Asterisk run every 5 minutes
1,6,11,16,21,26,31,36,41,46,51,56 * * * 1,2,3,4,5,6 /usr/share/astguiclient/AST_CRON_mix_recordings_BASIC.pl

### keepalive script for astguiclient processes
* * * * * /usr/share/astguiclient/ADMIN_keepalive_ALL.pl

### kill Hangup script for Asterisk updaters
* * * * * /usr/share/astguiclient/AST_manager_kill_hung_congested.pl

### updater for voicemail
* * * * * /usr/share/astguiclient/AST_vm_update.pl

### updater for conference validator
* * * * * /usr/share/astguiclient/AST_conf_update.pl

### flush queue DB table every hour for entries older than 1 hour
11 * * * * /usr/share/astguiclient/AST_flush_DBqueue.pl -q

### fix the vicidial_agent_log once every hour
33 * * * * /usr/share/astguiclient/AST_cleanup_agent_log.pl

### updater for VICIDIAL hopper
* * * * * /usr/share/astguiclient/AST_VDhopper.pl -q

### adjust the GMT offset for the leads in the vicidial_list table
1 1 * * * /usr/share/astguiclient/ADMIN_adjust_GMTnow_on_leads.pl --debug --postal-code-gmt

### reset several temporary-info tables in the database
2 1 * * * /usr/share/astguiclient/AST_reset_mysql_vars.pl

### optimize the database tables within the asterisk database
3 1 * * * /usr/share/astguiclient/AST_DB_optimize.pl

## adjust time on the server with ntp
30 * * * * /usr/local/bin/ntpdate -u 18.145.0.30 2>/dev/null 1>&2


### VICIDIAL agent time log weekly summary report generation
2 0 * * 0 /usr/share/astguiclient/AST_agent_week.pl



second server cron file is

### recording mixing for Asterisk run every 5 minutes
1,6,11,16,21,26,31,36,41,46,51,56 * * * 1,2,3,4,5,6 /usr/share/astguiclient/AST_CRON_mix_recordings_BASIC.pl

### keepalive script for astguiclient processes
* * * * * /usr/share/astguiclient/ADMIN_keepalive_ALL.pl

### kill Hangup script for Asterisk updaters
* * * * * /usr/share/astguiclient/AST_manager_kill_hung_congested.pl

### updater for voicemail
* * * * * /usr/share/astguiclient/AST_vm_update.pl

### updater for conference validator
* * * * * /usr/share/astguiclient/AST_conf_update.pl

### flush queue DB table every hour for entries older than 1 hour
11 * * * * /usr/share/astguiclient/AST_flush_DBqueue.pl -q

### reset several temporary-info tables in the database
2 1 * * * /usr/share/astguiclient/AST_reset_mysql_vars.pl

## adjust time on the server with ntp
30 * * * * /usr/local/bin/ntpdate -u 18.145.0.30 2>/dev/null 1>&2

### VICIDIAL agent time log weekly summary report generation
2 0 * * 0 /usr/share/astguiclient/AST_agent_week.pl

[saqibali]

solved .. by putting the time server script in crontab in DB server solved this problem .. thanks for the help.

[pylinuxian]

Most problems come from not reading the basic documentation.