Autodial places next call before agent dispositions previous
Posted: Fri Apr 04, 2008 3:28 amVicidial 2.03
CentOS 4.6
Asterisk 1.2.26
Tested with only one agent logged in. Current dial method is "ratio", autodial level is 1.
When using autodial mode, the first call is routed to the agent properly. When the customer hangs up the phone, the VD_hangup extension is called properly and the "hang up sound" is played to the agent, but there is a long delay before the agent screen goes to the "customer hung up, do you want to disposition or go back screen". Immediately after the first call was hungup, vicidial starts burning through leads, attempting to transfer them to 8365, then dropping the calls with hangup. This problem is consistently repeatable. Manual mode works fine.
After significant troubleshooting, we see that the vicidial_live_agents still shows the agent "INCALL" until the agent actually dispositions the call. It seems that as soon as the vicidial_auto_calls entryfor this call is deleted, new calls are placed regardless of the status of the available agent. It's unclear which vicidial component is supposed to update vicidial_live_agents, or what is supposed to happen to that record (update, delete, ??). My guess is the agent should be updated to "ready" status.
We have two servers that are nearly identical, the other works fine. We've confirmed that call_log and the correct "hangup" extensions are being called in the correct places, and in the Asterisk logs. The only other difference is the SIP provider. Asterisk seems to detect and report the correct dial status.
What vicidial component should be policing the vicidial_live_agents table, and why is AST_VDauto_dial.pl is placing calls when there are no agents marked READY in vicidial_live_agents?
Chris
CentOS 4.6
Asterisk 1.2.26
Tested with only one agent logged in. Current dial method is "ratio", autodial level is 1.
When using autodial mode, the first call is routed to the agent properly. When the customer hangs up the phone, the VD_hangup extension is called properly and the "hang up sound" is played to the agent, but there is a long delay before the agent screen goes to the "customer hung up, do you want to disposition or go back screen". Immediately after the first call was hungup, vicidial starts burning through leads, attempting to transfer them to 8365, then dropping the calls with hangup. This problem is consistently repeatable. Manual mode works fine.
After significant troubleshooting, we see that the vicidial_live_agents still shows the agent "INCALL" until the agent actually dispositions the call. It seems that as soon as the vicidial_auto_calls entryfor this call is deleted, new calls are placed regardless of the status of the available agent. It's unclear which vicidial component is supposed to update vicidial_live_agents, or what is supposed to happen to that record (update, delete, ??). My guess is the agent should be updated to "ready" status.
We have two servers that are nearly identical, the other works fine. We've confirmed that call_log and the correct "hangup" extensions are being called in the correct places, and in the Asterisk logs. The only other difference is the SIP provider. Asterisk seems to detect and report the correct dial status.
What vicidial component should be policing the vicidial_live_agents table, and why is AST_VDauto_dial.pl is placing calls when there are no agents marked READY in vicidial_live_agents?
Chris