ACDC Call Queues operations

[Arne van Balgoijen]

In version Kazoo 3.18 we are experiencing more issues with ACDC than we had before, especially Kazoo not detecting an agent is logged in and not delivering calls to the agent.

As you know ACDC is still an unsupported feature of Kazoo, but just like many others we sometimes need to use it to satisfy certain customers.

The only command I have at hand for now to restore functionality seems to be:
> sup whapps_controller restart_app acdc

Does anyone know any additional commands that can be used to control the operation of ACDC or have any any additional information/tips at hand to make the 3.18 version of ACDC work as expected?

FYI I have found these commands are under development, see: https://2600hz.atlassian.net/browse/KAZOO-1344

sup acdc_maintenance agent_login AccountId AgentId 

sup acdc_maintenance agent_logout AccountId AgentId 

sup acdc_maintenance agent_pause AccountId AgentId PauseTime (in seconds) 

sup acdc_maintenance agent_resume AccountId AgentId 

sup acdc_maintenance agent_queue_login AccountId AgentId QueueId 

sup acdc_maintenance agent_queue_logout AccountId AgentId QueueId

sup commands acdc_maintenance queues_restart AccountId 

sup commands acdc_maintenance queue_restart AccountId QueueId

[Dayton Turner]

Do you have any reproducible circumstances? I'm about to deploy 3.18 and would love to test them on my install as well.

[Arne van Balgoijen]

The issue that we experienced the most often was an agent logging in (confirmed by Kazoo, you are now logged in the quue) but not receiving any calls. In the dashboard it looks ok, but it actually is not. 

Restarting ACDC solves it, but you also loose any current calls in queue for all accounts and there is no way I know ho to detect this situation (other than a customer calling us).

[Lucas Bueno]

I had the same problem, as mentioned in this question: https://groups.google.com/forum/#!topic/2600hz-dev/Fp2-j6ORBMY .

Do you now if it was working in previous Kazoo versions? I've only tested in 3.18 .

[Arne van Balgoijen]

3.16-latest seemed to suffer less from the login issue.

I indeed also noticed that for new queues the restart was necessary. But unfortunately also during normal operations this happens, so an agent that logs out, logs in again and does not receive any calls.

[Dayton Turner]

Interestingly, I dont have that problem, but I have come across two others:

1: Agents are showing as unavailable (as though they're on the phone) when they've hung up already and should be available.

2: Calls to users with cell phone devices get hijacked instantly by the cell phone leg and ringing is passed through to the caller, regardless of 'require keypress' being enabled.