vicidial outbound autodial problem

[nekder]

i have a problem with the autodial feature...

it never starts the dialing and the CLI shows nothing when the agent is waiting for calls... the leads and everything are ok, in manual dial everything works fine... but on autodial mode vicidial never starts dialing, and the real time screen says that there is no active calls wating...


the campaign configuration is the following

Adapt Average
autodial level= 3
drop porcentage = 3
hopper level = 5

any idea?
thanks .

[mflorell]

Thank you for starting a new thread, but please do not post on the end of other threads.

astguiclient version?

output of 'screen -r'?

[nekder]

thanks matt

astguiclient version 2.0.4

and this is the output

There are several suitable screens on:
2970.ASTlisten (Detached)
2976.ASTVDadapt (Detached)
2968.ASTsend (Detached)
2972.ASTVDauto (Detached)
2966.ASTupdate (Detached)

[mflorell]

do you have any records in your vicidial_live_agents table?

can you attach to your ASTVDauto screen and post some output from when you are trying to auto-dial?

[nekder]

from vicidial_live_agents i got this:

live_agent_id user server_ip conf_exten extension status lead_id campaign_id uniqueid
129 6666 192.168.0.14 8600051 SIP/agente01 CLOSER 0 CI01_I 0.000000

and from AST_VDautodial i got this:


loop counter: |5759948|
TIME DEBUG: -4.00|-4.00|0| GMT: 21:33
2008-05-13 17:33:37|LIVE AGENTS LOGGED IN: 0 ACTIVE CALLS: 181|
2008-05-13 17:33:37|OLD TRUNK SHORTS CLEARED: 2 |''||
2008-05-13 17:33:37| : agents: dial_level: 0|
2008-05-13 17:33:37| : Calls to place: -85 (0 - 0) 181 MVT override: 96 |-85 0| OTHER LIMIT override: 96|
2008-05-13 17:33:37|CAMPAIGN DIFFERENTIAL: 0 0 (0 - 0)|
2008-05-13 17:33:37|LOCAL TRUNK SHORTAGE: 0|0 (96 - 96)|
2008-05-13 17:33:37| : CALLING|
TIME DEBUG: -4.00|-4.00|0| GMT: 21:33
2008-05-13 17:33:37|| lagged call vla agent PAUSED 0E0|20080513173307|20080513173327|20080513173337||
2008-05-13 17:33:37|| lagged call vac agent DELETED 0E0|2008-05-13 17:31:37||

i hope this can help..

[mflorell]

Looks like the agent is logged in as a CLOSER(receives inbound calls only) and not blended. Make sure the agent clicks on the blended checkbox in the green screen after logging in. If an agent is logged in as blended or outbound only then you wil see their status as READY.

[nekder]

sorry i made a mistake

this is the output for outbound autodial

live_agent_id user server_ip conf_exten extension status lead_id campaign_id uniqueid

131 6666 192.168.0.14 8600051 SIP/agente01 READY 0 TEST_MYE 0.0000000


and from AST_VDautodial i got this:

loop counter: |5759986|
TIME DEBUG: -4.00|-4.00|0| GMT: 16:05
2008-05-14 12:05:32|LIVE AGENTS LOGGED IN: 1 ACTIVE CALLS: 181|
2008-05-14 12:05:32|OLD TRUNK SHORTS CLEARED: 1 |'','TEST_MYE'||
2008-05-14 12:05:32|TEST_MYE 192.168.0.14: agents: 1 dial_level: 3.0|
2008-05-14 12:05:32|TEST_MYE 192.168.0.14: Calls to place: -177 (3 - 180) 181 |
2008-05-14 12:05:32|CAMPAIGN DIFFERENTIAL: 1 1 (1 - 0)|
2008-05-14 12:05:32|LOCAL TRUNK SHORTAGE: 0|0 (4 - 96)|
2008-05-14 12:05:32|TEST_MYE 192.168.0.14: CALLING|
TIME DEBUG: -4.00|-4.00|0| GMT: 16:05
2008-05-14 12:05:32|| lagged call vla agent PAUSED 0E0|20080514120502|20080514120522|20080514120532||
2008-05-14 12:05:32|| lagged call vac agent DELETED 0E0|2008-05-14 12:03:32||
2008-05-14 12:05:32|| logindate UPDATED 1|'TEST_MYE'||


PS: by the way, i was having problems with inbound calls too... that the reason why idid post the wrong output.

[mflorell]

Looks like you might have a lot of calls stuck in your vicidial_auto_calls table.

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

[nekder]

yes indeed
there are several calls stucked on vicidial_auto_calls

but i dont have any h exten on my dialplan

i only have the templates from the installation

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

[mflorell]

You need to have those h exten lines in every context of your dialplan that a VICIDIAL call might go through.

[nekder]

im working only with the default context

i think i dont complete understand what is the purpose of that lines...

[mflorell]

Their purpose is to finish logging on VICIDIAL calls when they get hungup in any way other than within the agent interface. They are very important.

[nekder]

thanks matt

i drop the stucked calls on vicidial_auto_calls, and now the agent is taking call...

but now there is another issue...

when the client answer de call, it is inmediatly hanged up by the system...

i though that it might be solved with the sip-silence extensión, but it was not...

is this extensión all right¿?

;; VICIDIAL_auto_dialer transfer script:
exten => 8365,1,Playback(sip-silence)
exten => 8365,2,AGI(agi://127.0.0.1:4577/call_log)
;exten => 8365,2,AGI(call_log.agi,${EXTEN})
exten => 8365,3,AGI(agi-VDADtransfer.agi,${EXTEN})
exten => 8365,4,AGI(agi-VDADtransfer.agi,${EXTEN})
exten => 8365,5,Hangup


i got this from the CLI output when the calls are made...

-- Executing Dial("Local/0990801392@default-6275,2", "iax2/tec:tecnisys@192.168.0.10/0990801392|60|tTo") in new stack
-- Called tec:tecnisys@192.168.0.10/0990801392
-- Call accepted by 192.168.0.10 (format gsm)
-- Format for call is gsm
-- IAX2/vicidialnow-2 is proceeding passing it to Local/0990801392@default-6275,2
== Parsing '/etc/asterisk/manager.conf': Found
== Manager 'sendcron' logged on from 127.0.0.1
== Manager 'sendcron' logged off from 127.0.0.1
== Parsing '/etc/asterisk/manager.conf': Found
== Manager 'sendcron' logged on from 127.0.0.1
== Manager 'sendcron' logged off from 127.0.0.1
-- IAX2/vicidialnow-2 is ringing
-- IAX2/vicidialnow-2 stopped sounds
-- IAX2/vicidialnow-2 answered Local/0990801392@default-6275,2
== Manager 'sendcron' logged off from 127.0.0.1
-- Executing Playback("Local/0990801392@default-6275,1", "sip-silence") in new stack
-- Playing 'sip-silence' (language 'en')
== Spawn extension (default, 0990801392, 1) exited non-zero on 'Local/0990801392@default-6275,2'
-- Executing DeadAGI("Local/0990801392@default-6275,2", "agi://127.0.0.1:4577/call_log") in new stack
May 15 10:28:08 WARNING[9359]: res_agi.c:210 launch_netscript: Connect to 'agi://127.0.0.1:4577/call_log' failed: Connection refused
== Spawn extension (default, h, 1) exited non-zero on 'Local/0990801392@default-6275,2'
-- Executing AGI("IAX2/vicidialnow-2", "agi://127.0.0.1:4577/call_log") in new stack
May 15 10:28:08 WARNING[9409]: res_agi.c:210 launch_netscript: Connect to 'agi://127.0.0.1:4577/call_log' failed: Connection refused
== Spawn extension (default, 8365, 2) exited non-zero on 'IAX2/vicidialnow-2'
-- Executing DeadAGI("IAX2/vicidialnow-2", "agi://127.0.0.1:4577/call_log") in new stack
May 15 10:28:08 WARNING[9409]: res_agi.c:210 launch_netscript: Connect to 'agi://127.0.0.1:4577/call_log' failed: Connection refused
== Spawn extension (default, h, 1) exited non-zero on 'IAX2/vicidialnow-2'
-- Hungup 'IAX2/vicidialnow-2'


PS: another doubt that i have is why the vicidial_auto_calls table got stucked... now it work all right, but i dont know if this problem could happen again in the future...

[mflorell]

Please post the output of 'screen -r'

[nekder]

it`s the same tha before...

[root@arrayan ~]# screen -r
There are several suitable screens on:
2946.ASTVDadapt (Detached)
2940.ASTlisten (Detached)
2936.ASTupdate (Detached)
2942.ASTVDauto (Detached)
2938.ASTsend (Detached)
Type "screen [-d] -r [pid.]tty.host" to resume one of them.

[mflorell]

ASTfastlog is not running, try running it manually and see what output you get:
/usr/share/astguiclient/FastAGI_log.pl --debug

[nekder]

thanks matt

you were right, it wasn`t running

i have to reinstall some perl modules

Net::Sserver and Net::Telnet

i will check how things works now and ill report back for news...