I noticed a problem with the operation of Callcenter in issabel version:
Released / Issabel 4 / issabel4-USB-DVD-x86_64-20200102.iso
from asterisk 16.7.0-1.el7.
When I do tests at my desk and run 1 callcenter agent and make calls, it seems that everything is OK.
However, the attempt to start the callcenter system (even one agent) in real conditions (incoming, outgoing connections, FOP2) ends in complete suspension of the AMI interface.
I am sure that this is not a hardware issue because in the end I manage to cause this problem on a desk on a completely different server.
Although it is not easy, I just have to simulate several calls, perform actions on the issabel callcenter panel, answer calls, pause etc.
At some point, the www callcenter interface stops working, you cannot log out, you cannot run anything in the issabel tabs.
When I close the browser and restart, surprisingly I can connect to Issabel and log in but the PBX / PBX configuration tab does not respond, the same applies to the My extension tab.
Not much is happening in the logs or I just can't read it.
The only thing I've noticed and clearly linked to this problem is the information that appears in var / log / asterisk / issabelpbx.log:
[2020-Mar-06 11:10:07] [CRITICAL] (admin / bootstrap.php: 134) - Connection attmempt to AMI failed.
Restarting from the "reload manager" asterisk console does not help.
Sometimes, as long as it waits, everything returns to normal, but usually you need to do the "core restart now" in the console.
An attempt to connect to AMI directly from ssh on port 5038 fails, AMI does not respond, there is no Asterisk Call Manager / 5.0.1.
The same applies when trying to connect via telnet to localhost, AMI does not respond.
When this issabel interface hangs, it seems that FOP2 is still running on the session it established.
However, attempting to log out and log in again gives you information that there are problems connecting to AMI.
It is not easy to reproduce this problem on my desk but in the end I succeeded, it seems that it is closely related to traffic on the PBX.
If it generates one connection, I'm alone, nobody calls, launching the callcenter panel doesn't cause a problem.
But when the company is working normally and I start the callcenter console, it is a matter of 5 minutes and AMI stops responding
