Agi vs DeadAgi and vicidial_auto_calls

[PierreDeux]

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

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.

[williamconley]

Since you have a newer version it is likely that the agi is now being used to replace the deadagi to avoid the warning.

You should see if you can identify the cause of the orphaned entries or Try turning on Enhanced Disconnect Logging which may harvest them immediately for you. Check it out.

Enhanced Disconnect Logging - This setting enables logging of calls that get a CONGESTION signal with a cause code of 1, 19, 21, 34 or 38. We usually do not recommend enabling this in the USA. Default is 0 for disabled.