If I am rude it is because I like things to work. When they don't I am unhappy.

Tell me your name, email and activation code and I will give you a refund.

admin,
An idea until the next version is final...

Not final, but nearly completion. The beta is available for all platforms, also fop2admin is updated to take advantage of the new custom permissions. More information [url=http://www.fop2.com/forum/View Post 922:17shrxzy]here[/url:17shrxzy]

admin,
An idea until the next version is final...

Not final, but nearly completion. The beta is available for all platforms, also fop2admin is updated to take advantage of the new custom permissions. More information [url=http://www.fop2.com/forum/View Post 922:1adj8tfw]here[/url:1adj8tfw]

Thanks for the 64bit beta. FYI, your mention of the API delay as a possible cause of my problem got me thinking. There is an Elastix install procedure which describes the creation of a new manager API for FOP2 rather than using the default [admin] which is used by FreePBX.

Your instructions don't mention that. So perhaps by using the default api it was causing a delay and causing fop2 to stop responding. By creating a new api I don't seem to be having the problem except when I restart asterisk which I guess is a different problem that your new beta fixes.

I think there is no difference on the manager user you use. As long as it has the correct permissions you can use "admin" or create a new one. I prefer to use "admin" myself, as it is easier. Some FreePBX version do not have the option to add all permission keywords to the api user, and that might be also a problem.

On the installs I made on FreePBX systems, I always used the admin user with no issues. If using a new user works better for your that is great! Please test with the new beta and let me know how it goes.

Best regards,