Dialing 60 seconds delay.

Added by Augusto Paolo Mari over 9 years ago

Hi there,
i installed the goautodial 3.0 and then upgraded to 3.3. I'm using a dahdi pri card.
The sistem isn't still in production, i'm testing the softwate to evaluate an evetually usage.
My issue is that every dialing request issued from the vicidial, is forwarded to asterisk after a delay at maximum of one minute.
Also when an agent logs on, the systems call him back at maximum after one minute.
At the moment i set up an OUTBOUND MANUAL DIAL campaign, and the operator fill the field of the telephone number.
The system dials, with a maximum of one delay of 60 seconds before asterisk dials the required number.
Is possible to reduce this time?
Regs,
apm

[Sep 3 18:05:01] Manager 'sendcron' logged on from 127.0.0.1
[Sep 3 18:05:01] Manager 'sendcron' logged on from 127.0.0.1
[Sep 3 18:05:01] Manager 'sendcron' logged off from 127.0.0.1
[Sep 3 18:05:03] Manager 'sendcron' logged off from 127.0.0.1
[Sep 3 18:05:03] Manager 'listencron' logged on from 127.0.0.1
[Sep 3 18:05:03] Manager 'updatecron' logged on from 127.0.0.1
[Sep 3 18:05:07] Manager 'sendcron' logged on from 127.0.0.1
[Sep 3 18:05:07] Manager 'sendcron' logged off from 127.0.0.1
[Sep 3 18:06:02] Manager 'sendcron' logged on from 127.0.0.1
[Sep 3 18:06:02] Manager 'sendcron' logged on from 127.0.0.1
[Sep 3 18:06:02] Manager 'sendcron' logged off from 127.0.0.1
[Sep 3 18:06:03] Manager 'sendcron' logged off from 127.0.0.1
[Sep 3 18:06:03] Manager 'listencron' logged on from 127.0.0.1
[Sep 3 18:06:03] Manager 'updatecron' logged on from 127.0.0.1
[Sep 3 18:06:07] Manager 'sendcron' logged on from 127.0.0.1
[Sep 3 18:06:07] Manager 'sendcron' logged off from 127.0.0.1

Replies (6)

RE: Dialing 60 seconds delay. - Added by striker 247 over 9 years ago

check the below fields in campaign

1. minimum hopper level ( if u give 1 then every one minute the hopper script will run and update the hopppe with 1 lead)
change it to 500 or 1000

2. wrapup time = set to 0

br
striker
www.striker24x7.blogspot.com

RE: Dialing 60 seconds delay. - Added by Augusto Paolo Mari over 9 years ago

Ciao Striker,
i set Minimum Hopper Level at 1000, (tryed also with 2000).
Also i checked the Wrap Up Seconds parameter, and it already was set to 0.
So no lucky.
Is the a way to invoke the VDhopper script in a different way?
Regs,
apm

RE: Dialing 60 seconds delay. - Added by Demian Biscocho over 9 years ago

We can't seem to understand what the issue is. Can you elaborate more? Where are you getting the 60 second delay?

RE: Dialing 60 seconds delay. - Added by Augusto Paolo Mari over 9 years ago

Hi there,
i created an outbound campaign, in manual dialing.
The agent logs in, and after a while (maximum one minute) the asterisk calls the sip phone to put in the conference room.
Later, when the agent fills the dialing number and click the dial link, again after a minute the vicidial send the dialing command to the asterisk. I remember that only added this to the extension.conf file to dial using the pri board:

exten => _9XXXXX.,1,AGI
exten => _9XXXXX.,2,Dial(DAHDI/g0/${EXTEN:1},,TtoR)
exten => _9XXXXX.,3,Hangup

I remember that at the beginning, it was working quickly.
When an agent star to log in, immediatly the sip phone received the call to got joined in the conference room.
I don't know why now is acting in this way, i just see that asterisk receive the dialing instruction after this events are logged:

Please help.
Regs,
apm

RE: Dialing 60 seconds delay. - Added by Demian Biscocho over 9 years ago

Can you run this command and post the output here:

screen -ls

Sounds like some of the Vicidial perl scripts are not running.

RE: Dialing 60 seconds delay. - Added by Augusto Paolo Mari over 9 years ago

Hi there,
our installation has been violated.
So i will reinstall it.
I will let you know if i'll incurr in the same issue.
Thanks,
apm

(1-6/6) Go to top

Project

General

Profile

GOautodial Open Source Omni-channel Contact Center Suite