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?

[alex.mejia]

Hello guys, sorry to wake an old post but I'm having the same issue here, but causing problems on PAUSED agents.

Sometimes a paused agent gets an inbound call without apparent reason, and when we look for the call information we end up with a DROP call.
Agent showing as QUEUE on the realtime dashboard, and call marked as a DROP on the closer_log.

Did you got a chance to fix this by any chance?

Version: 2.14-842a
Build: 220127-2915
Asterisk: 13.38.2-vici

[williamconley]

Hello guys, sorry to wake an old post but I'm having the same issue here, but causing problems on PAUSED agents.

Sometimes a paused agent gets an inbound call without apparent reason, and when we look for the call information we end up with a DROP call.
Agent showing as QUEUE on the realtime dashboard, and call marked as a DROP on the closer_log.

Did you got a chance to fix this by any chance?

Version: 2.14-842a
Build: 220127-2915
Asterisk: 13.38.2-vici

What are the DROP settings for the ingroup in question?

Was this a stock install with Vicibox, or a custom install?

How long had the agent(s) been paused when they get these inbound calls? (eg: Immediately after pause? after sitting on pause for a long time? mixture?)

Does this affect ONE ingroup? (Do you have multiple Ingroups?) Does this affect ONE agent? (Do you have multiple live agents when this occurs?)

Does this happen during heavy load? Specific time of day? Do these calls have anything in common with one another? Is this occurrence predictable in any fashion?

Start a Log.

[rafaelcm]

Hi William,

The drop settings is default (campaign and ingroup)

is a vicidial custom

after sitting on pause for a long

its a multiple Ingroups

don't have anything in common with one another

[williamconley]

drop call settings do not have one named "default" and there are multiple settings. Your installation being custom, it would be useful if you provided the actual settings.

That being said: If your installation was not with Vicibox's ISO installer, please provide your installation method. Link to the instructions, ISO image used, any exceptions to the installation or steps taken after installation.

It's entirely possible you just have a mismatch configuration file or cron setting or something similar.

[rafaelcm]

Hi Williams,

Mi drop settings is:
Campaing:
Drop Call Seconds 5
Drop Action: AUDIO

Ingroup:
Drop Call Seconds:360
Drop Action: Message

A have a installed with a vicibox ISO but is an expert install in cluster (my apologies for not being clearer the first comment I spoke)