SOLVED: Nothing changed in the fop2 extension. For some, unknown to me, reason the script failed, resulting in an internal server error when called by the fop2 extension. Restoring a backup versions of the script solved the problem.
Hi,
Thanks for the reply, I changed the ownership of the fop2 admin folder contents to asterisk. I upgraded with the webinterface last month so it could have happened the way you suggest.
regards,
Tom
