I’d kindly ask for your help - we have an asterisk 13 installation with approximately 100 queues and 30 agents. When a call comes into any of the queues and asterisk cycles through available agents, we get an error:
Same thing happens when agents login/logoff. I’ve first noticed this problem with asterisk version 13.19, but it’s also present in 13.20 and 13.21. Last working version was therefore 13.18.
I can easily reproduce this with test system without any load. If this matters, we are using freepbx 13.0.195 and dynamic queue members - it might be related to amount of AMI messages (QueueMemberStatus), but we need those due to a third party application that reads AMI events (CRM).
Could anyone point me into the right direction? Is there a way of increasing the watermark limits, task queue depth, anything like that?
It affects the 3rd party app (CRM) that reads AMI events - things that should happen when the call is answered are delayed for approximately 30 seconds (pop up window with greeting text, customer data).
So it seems that relevant info reaches AMI with delay or something.
We ended up changing the way our CRM application works so it wasn’t depending on QueueMemberStatus events anymore. We’ve filtered them using eventfilters in manager_custom.conf.
That made a huge difference but didn’t remedy the problem entirely. Problem was solved by declining QueueMemberStatus event messages in stasis.conf.