Inbound calls marked as DROP in vicidial_log table

[richa.chandna]

Hi Team,

We are facing issues in inbound calls, calls are answered but it's added in vicidial_log with DROP status from Autodial script (AST_VDauto_dial.pl - it's updating on the basis of condition "vicidial_auto_calls table records exist with status LIVE and not updated from last 10 seconds", it's not happening in every call.

Length in vicidial_log - 111 or 99 or 91 in each call's

Length in vicidial_closer_log - It's different in each call
vicidial_closer_log, queue_seconds - It's different in each call

Build - 2.4b0.5
Asterisk - 1.4

I have seen below logs in agiout log file

CHANNEL SIP/gateway-00010123   DOWN 0 3600|18 CHECKING AGAIN
WWWWW VDAD XFER BALANCE WAIT: |2|INBOUND_GROUP|SIP/gateway-00010123  |CALLER_ID  |UNIQUE_ID|0|
WAIT OPTION PRIORITY, HOLD NO RUN: |186|WAIT|  |1|  |CALLER_ID|

Please suggest if anyone is aware of the issue/solution.

[martinch]

Hey guys,

I appreciate the build is old and the Asterisk version is also old but has anybody seen anything like this?

These are inbound calls (dropping into vicidial_closer_log) which are also stamping vicidial_log (the outbound log) as a dropped call causing a reporting nightmare.

Appreciate any responses.

Thanks,
Martin.

[williamconley]

Full Vicicial Version With Build is required. Note that there is a "build" listed, but that's the Vicidial version, not build. Then there's an asterisk version, but once again just the major without the full version. Please always list full versions any time you list them. And we may find the installation method (with version) useful as well. Goautodial vs Vicibox 1.0RC2 could have very different (ancient) problems when scanning the historical files.

Next up: Did this just start happening? What changed? Did you route your calls in a different way than previously? Is there a call menu in the path? Are these calls "dropping" from one ingroup to another before being answered?