FOP2 'Manager Connection Problem'
We recently implemented FOP2 company wide and love it, but we have noticed issues. I noticed that our /etc/asterisk/full file is +4GB, we get error messages "Manager Connection Problem" when trying to log out and log back in, and also "System not Available". We also seem to have started using 2 channels per phone call after implementing FOP2.
I think we are having so many problems because we like it so much!
We are running FOP2 2.24 on PBX in a Flash with asterisk 1.4.
Do you have any ideas of what could be causing these issues or where to look to try to figure it out?
I think we are having so many problems because we like it so much!
We are running FOP2 2.24 on PBX in a Flash with asterisk 1.4.
Do you have any ideas of what could be causing these issues or where to look to try to figure it out?
Comments
Thanks for linking the software! Now to my recommendations, they are NOT fop2 related but asterisk related:
1) Turn off the full log. Edit /etc/asterisk/logger.conf and comment out with a semicolon in front the full line, so it looks somewhat like this:
After that change, reload the logger with the command:
If your system is that busy, you do not want the full log enabled as it will take a lot of resources and put a lot of load in the machine that you want for voice and not for writing a big log file. Just enable the full log whenever you need to troubleshoot.
2) Manager disconnection issues and System not Available:
This is a little bit more complicated if you are using Asterisk 1.4, as it is kind of old and does not have all the features I would like to have. The problem is that most probably you have a busy box, with lots of events going on. When you have a flood of events in the manager, the fop2 server might hicup, and asterisk might also close the connection to AMI.
We do not want that to happen.
One way to reduce the chance for this is to set writetimeout=1000 in the /etc/asterisk/manager.conf file. The problem is that I do not remember exactly in what asterisk version that config parameter was enabled. Also, some Asterisk 1.4 versions have problems dealing with AMI completely, upgrading to the latest version might always help. In more recent asterisk versions we can set event filters, but is not an option in 1.4, but you can uncomment the event_mask line in /usr/local/fop2/fop2.cfg
The ultimate solution is to upgrade to Asterisk 1.8 or 10 and use eventfilters as explained in http://www.fop2.com/blog/make-fop2-snap ... ventfilter
Other ways to reduce events includes some specific settings, for example, in your queue configuration, disable eventmemberstatus if you have it enabled. If you have queues with RINGALL strategy, change that and use RRMEMORY or another strategy, RINGALL is evil.
3) 2 channel per call: no idea what you are talking about. Fop2 does not use channels itself? It does not alter the dialplan either, so I do not see how can installing fop2 might lead to having 2 channels per call.
If you use Local/xxx type channels in your dialplan, that generate more than one channel as the Local channel is a proxy to the real channel/device. But fop2 does not use Local channels UNLESS YOU TOLD IT TO by setting the originatechannel in the button configuration.
FreePBX, on the other side, uses Local channels A LOT. For almost everything : queue members, follow me, ring groups, etc. But that is your dialplan, it is not fop2.
Best regards,
I went into /etc/asterisk/logger_logfiles_custom.conf and commented out the line
Then I restarted the logger from the asterisk command line with
logger restart
Then I restarted fop2 with the following:
service fop2 restart
and we were up again!
It doesn't look like writetimeout is an option with our version and we did not upgrade to 1.8 yet, but we are on a hosted solution and I submitted a ticket, so hopefully that will happen soon.
Thanks again!