Stasis/m:devicestate

Hello,
I am using asterisk 16.18.0

40 queues in each queue, 30 operators for whom there is a simultaneous call.

In the console, asterisks often convey a message during a queue call:

[2021-07-11 11:23:24] WARNING[1146]: taskprocessor.c:1160 taskprocessor_push: The ‘stasis/m:devicestate:all-00000043’ task processor queue reached 500 scheduled tasks again.
[2021-07-11 11:23:25] WARNING[1146]: taskprocessor.c:1160 taskprocessor_push: The ‘stasis/m:devicestate:all-00000043’ task processor queue reached 500 scheduled tasks again.
[2021-07-11 11:25:13] WARNING[1146]: taskprocessor.c:1160 taskprocessor_push: The ‘stasis/m:devicestate:all-00000043’ task processor queue reached 500 scheduled tasks again.
[2021-07-11 11:25:21] WARNING[1146]: taskprocessor.c:1160 taskprocessor_push: The ‘stasis/m:devicestate:all-00000043’ task processor queue reached 500 scheduled tasks again.
[2021-07-11 11:25:21] WARNING[1146]: taskprocessor.c:1160 taskprocessor_push: The ‘stasis/m:devicestate:all-00000043’ task processor queue reached 500 scheduled tasks again.
[2021-07-11 11:25:21] WARNING[1146]: taskprocessor.c:1160 taskprocessor_push: The ‘stasis/m:devicestate:all-00000043’ task processor queue reached 500 scheduled tasks again.
[2021-07-11 11:35:35] WARNING[1146]: taskprocessor.c:1160 taskprocessor_push: The ‘stasis/m:devicestate:all-00000043’ task processor queue reached 500 scheduled tasks again.

There is enough processor and RAM.

The question is, what can this affect?
How to raise the process queuing threshold?

There is no ability to control this threshold, and it can affect PJSIP if the “taskprocessor_overload_trigger” option is not set to “pjsip_only”.

1 Like

i am using chan_sip instead of pjsip

I understand that these warnings do not affect anything?

They wouldn’t inherently cause other things to stop working as a result of them. It does mean that there were a lot of things in the queue to be worked and processed.

1 Like