Dialing slows down when dialed lead is NA

[CHP]

Hello all,
Some of our agents using the VICIDIAL System have told us, that their Wait time between the calls is often very high, and so we took a closer look and setted up a outbound-dialing test campaign, calling us itself with following settings:

RATIO=1
AutoDialLevel=1
DialTimeout=22 sec.

If the called Lead is available and picks up the phone, talks, hung-up, and then finishing the call, then VICIDIAL immediately calls the next Lead.
(Monitored by CLI).

The problem is, if the called Lead is not available and doesn't pick up the phone (NA-Autodial), then it takes nearly exactly 100 sec. (meashured 5 times consecutively) until VICIDIAL diales the next lead and so produces a very high wait time.

Our Vicidialsystem: Multiserver (Ast/Vici+DB/Web)
Slackware 12.1+scratch install+astguiclient 2.4.0.1RC2 updated to
astguiclient 2.4.0.1RC3

The rest of the system is all working very well.

So does anybody have an idea what kind of misconfiguration that could be?

Thanks in advance

[mflorell]

Do you have the proper 'h' exten in all contexts in your dialplan?

[CHP]

We're just using one context, the "default".

That's what about extens h in the extensions.conf:

; FastAGI for VICIDIAL/astGUIclient call logging
exten => h,1,DeadAGI(agi://127.0.0.1:4577/call_log--HVcauses ... EBUG-----${HANGUPCAUSE}-----${DIALSTATUS}-----${DIALEDTIME}-----${ANSWEREDTIME})

Does it help if I post the CLI output from the procedere dial->ringing->hangup->wait 1:40min->dial->...

[mflorell]

CLI output might help.

What kind of trunks are you using?

will a call remain in the vicidial_auto_calls table even 10 seconds after it is hung up?

[CHP]

I'll post CLI Output when I'm the only one one the machine...

We're using IAX2 Trunks Codec ULAW (trunking mode on)

vicidial_auto_calls table:
I have monitored both cases (the working and the not working)

working case:
starting campaing, Lead with lead_id was putted into the vicidial_auto_calls table wth status SENT, -> called lead picks up the phone -> status is changed from SENT to XFER -> hangup after call->lead is beeing deleted from table, call is finished throug callagent -> a new lead was putted in the table immediately with status SENT -> and the phone is ringing again...

not working case:
if the called lead does not pick up the phone, after hangup the called lead stayed still in the table with status sent. I takes the 100 sec. then the lead is beeing deleted and then an new lead with the next lead_id appears in the table.

[mflorell]

Are these non-working phone numbers going through the proper dialplan?

Are they real numbers?

Do they go through the call_log process before they are placede as calls?

[CHP]

It does not depend on the called numbers, the problem occurs on all numbers, at test campaign we tried out fixed and mobile numbers, which are defenitly working.

The calls are in the call_log and also are in cdr log with "NO ANSWER".

Before the Dial Command in the CLI appears the message for call_log completed appears. (real calledNr has been replaced with 00123456789)

-- Executing AGI("Local/00123456789@default-b98f,2", "agi://127.0.0.1:4577/call_log") in new stack
-- AGI Script agi://127.0.0.1:4577/call_log completed, returning 0
-- Executing Dial("Local/00123456789@default-b98f,2", "IAX2/userid:password@111.222.333.444/00123456789|55|o") in new stack
-- Called userid:password@111.222.333.444/00123456789
-- Call accepted by 111.222.333.444 (format ulaw)
-- Format for call is ulaw
-- IAX2/userid-16 is ringing
-- IAX2/userid-16 is making progress passing it to Local/00123456789@default-b98f,2
-- Hungup 'IAX2/userid-16'
== Spawn extension (default, 00123456789, 5) exited non-zero on 'Local/00123456789@default-b98f,2'
-- Executing DeadAGI("Local/00123456789@default-b98f,2", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----0-----CANCEL----------") in new stack
== Manager 'sendcron' logged off from 127.0.0.1
-- AGI Script agi://127.0.0.1:4577/call_log--HVcauses ... ---------- completed, returning 0

[CHP]

Seems to be the problem, that the leads in the vicidial_auto_calls table are not beeing deleted when the ring-timout is reached.
When I manually delete the records in the table, then the next call will immediately be dialed.

I tried set the Timeout of the Dial Command (dialplan) under the level of the vicidial timeout ->same result, only that the reached timeout is shown in the CLI

What's responsable for refreshing / deleting the records after a channel hungup in the vicidial_auto_calls table?

The Realtime Screen also shows this Calls as ringing and beeing placed until I delete them from the table, it seems that that the source of this is also the same table?

[mflorell]

Asterisk version?

VICIDIAL version?

[CHP]

Our Vicidialsystem: Multiserver (Ast/Vici+DB/Web)
Slackware 12.1+scratch install+astguiclient 2.4.0.1RC2 updated to
astguiclient 2.4.0.1RC3

Asterisk 1.2.24

vicidial/agc
latest file updates from /svn/agc_2-X/branches/agc_2.0.4/www

[mflorell]

This is related to your other current issue. Let's continue the discussion on that thread:
http://www.eflo.net/VICIDIALforum/viewtopic.php?t=5980