We have been fighting this for a while. I haven’t reported this yet, lack of time, but for us we have a customer with 13 phones in a queue. Those phones are part of a company with 20 phones with BLF’s all watching one another. Whenever they get an inbound call that rings their queue it throws:
[2018-07-27 23:17:20] WARNING[28680][C-00000000]: taskprocessor.c:895 taskprocessor_push: The ‘subm:manager_topic-00000007’ task processor queue reached 3000 scheduled tasks.
Without fail. 13 phones in a queue plus all those BLF updates seem to overwhelm the ‘subm:manager_topic-00000007’. Do you have a similar setup when this happens?
Asterisk mentioned that you can do:
- If the task processor name happens to be of the ‘subm:<topic>’ form where the topic is your stasis application name then that task processor is servicing the stasis message bus communication with your application. One thing you can try is to register multiple copies of your stasis application and randomly spread calls to the different copies of the application. e.g., my_stasis_app1, my_stasis_app2,…
But I don’t know if its a configuration option or a Freepbx change.