FOP2 Community Forum

The reason why that kept happening is because the amportal.conf file was be regenerated. If I made changes directly to amportal.conf they would be discarded the next time the file was recreated. I believe I solved my problem by uninstalling FOP (not disabling) from Module Admin and rebooting the server. I did a fop2 restart and everything seems to be working now.

Hello, I had FOP2 setup on my clients PBX for about a month now and everything was working fine. I was called today and told that they were unable to connect. The first thing I tried was: service fop2 restart. When I entered that command I got: root@pbx:~ $ service fop2 restart Shutting down Flash Operator Panel 2: [FAILED] Starting Flash Operator Panel 2: XSLoader.pm did not return a true value at -e line 344. [FAILED] I am not sure what is causing this. The client has no access to root and only knows how to use FOP2. Do you know how to resolve this? Thanks, -Alonzo

Sounds as an asterisk chanspy feature/bug/misconfiguration. You will have to look at the asterisk full log with debug enabled in order to see more information. IN fop2 there is one setting that can drop your session, but it only does that if the spied on channel hangs up. To prevent that from happening, you can turn it off, in /usr/local/fop2/fop2.cfg persistent_spy=1 (This setting will be no longer available in FOP 2.27, as the option to drop the session when the spied on channel ends is already implemented in recent asterisk versions). Best regards,