Agi vs DeadAgi and vicidial_auto_calls
Posted: Wed Nov 27, 2013 7:16 am
Hi everyone
I recently noticed that there are some old records in my vicidial_auto_calls, that are not getting deleted until AST_reset_mysql_vars.pl. This is a pretty often discussed issue here and most threads end up with checking extensions-vicidial.conf, that have wrong h,1 records. I've checked mine too and it seems that instead of
I have:
The difference between Agi and DeadAgi can possibly cause such issues, but as Agi can't be executed on hang up channel I should have much more those old auto_calls records. So I wonder if it's okay that it has agi instead of deadagi?
My vicidial version is 2.8-417a BUILD: 131019-0849, asterisk 1.8.23.0-vici. Installed using Vicibox 5.0.3, no extra hard or software used.
I recently noticed that there are some old records in my vicidial_auto_calls, that are not getting deleted until AST_reset_mysql_vars.pl. This is a pretty often discussed issue here and most threads end up with checking extensions-vicidial.conf, that have wrong h,1 records. I've checked mine too and it seems that instead of
- Code: Select all
exten => h,1,DeadAGI(agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----${HANGUPCAUSE}-----${DIALSTATUS}-----${DIALEDTIME}-----${ANSWEREDTIME})
I have:
- Code: Select all
exten => h,1,AGI(agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----${HANGUPCAUSE}-----${DIALSTATUS}-----${DIALEDTIME}-----${ANSWEREDTIME})
The difference between Agi and DeadAgi can possibly cause such issues, but as Agi can't be executed on hang up channel I should have much more those old auto_calls records. So I wonder if it's okay that it has agi instead of deadagi?
My vicidial version is 2.8-417a BUILD: 131019-0849, asterisk 1.8.23.0-vici. Installed using Vicibox 5.0.3, no extra hard or software used.