You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Currently we use the operating system Debian 10, FusionPBX 4.4, Postgresql12, Freeswitch v1.10.9, and the resource is 12vCPU-12GB RAM. We are facing the following problems:
When sending a command through the Event_Socket API to execute a call to a mobile device, and then routing the call back to the mod_callcenter queue, the load average is when execution reaches around 200 concurrent calls per second (ccu), of which 20 calls per second (cps) Start increasing) arrive).
Many calls get stuck in the Freeswitch database and Freeswitch channels.
Sometimes, many call center agents get stuck not answering calls.
After that, we upgraded to 32vCPU-32GB RAM, but the overloaded situation still persists.
backtrace from core file
If applicable, provide the full backtrace from the core file. backtrace.log
The text was updated successfully, but these errors were encountered:
Describe the bug
Currently we use the operating system Debian 10, FusionPBX 4.4, Postgresql12, Freeswitch v1.10.9, and the resource is 12vCPU-12GB RAM. We are facing the following problems:
When sending a command through the Event_Socket API to execute a call to a mobile device, and then routing the call back to the mod_callcenter queue, the load average is when execution reaches around 200 concurrent calls per second (ccu), of which 20 calls per second (cps) Start increasing) arrive).
Many calls get stuck in the Freeswitch database and Freeswitch channels.
Sometimes, many call center agents get stuck not answering calls.
After that, we upgraded to 32vCPU-32GB RAM, but the overloaded situation still persists.
backtrace from core file
If applicable, provide the full backtrace from the core file.
backtrace.log
The text was updated successfully, but these errors were encountered: