FOP2 Community Forum

Things are getting muddy here. If the problem is that in the FOP2 Manager Dashboard you see that the service is not running, but the service IS running, then most probably there are security settings in the server (like selinux), preventing PHP from performing socket connections, thus the monitor server check routine fails. It is nothing to worry about, as fop2, and the manager, will still work happily, just the service check in the fop2 manager dashboard might fail. You can disable selinux, or create rules in selinux to allow php socket connections, and you will be fine. Check the FAQ where it says how to allow socket connections for PHP.

If that is truly the user you have, then it seems correct, but again, your problem description points to bad/incomplete manager events. FOP2 won't work if the manager is not sending the information it needs. You can start fop2 in debug mode level 15 to capture information and the AMI/fop2 dialog, something like: service fop2 stop cd /usr/local/fop2 script capture.log ./fop2_server -X 15 (log into fop2, make a call, verify the incorrect status) ctrl-C exit service fop2 start Now you have the capture.log file to analyse. A few weeks ago a user reported a similar issue,and it ended up being an asterisk version 1.6 (old! do not use 1.6!) that was MODIFIED to suppress lots of manager events. Obviosuly, do not expect FOP2 to work over modified asterisk versions with a tweaked manager interface. Best regards,

You can use extensions with any number of digits, there is no limitation whatsoever about extension length. You might experience issues if you have extensions starting with zero, there is a new autoconfig users script that fixes that, that will be available i the next release.