Hi everyone
I've successfully installed FOP2 and it was working fine until something happened. I'm not sure what exactly it was, maybe regular CentOS update, maybe something else I'm not aware about, but my extensions suddenly were unable to login with their passwords set in FreePBX gui under Fop2 Users. It just kept refreshing the login prompt.
After taking out some experiments I found out that I'm able to log in with voicemail password (if it's set), however all extension permissions, set in Fop2 Users gui were just ignored and I got a very basic number of features: park slots, trunks and filter/dial/available inputs on top. Nothing more.
So my question is: what should I do to make my FOP2 listen to what's set in it's config and permissions?
-
12 years ago
-
It seems the fop2admin module is not being detected by the autoconfiguration scripts, look at autoconfig-users-freepbx.sh and autoconfig-buttons-freepbx.sh, those scripts have a little detection query to find out if you have fop2admin installed or not, if not it will default to a basic setup, with voicemail passwords and button set. It seems that check is failing in your install.
The check depends on a number of things.. the database name is extracted from /etc/amportal.conf file AMPDBNAME setting, if that file has DOS new lines, that might be the issue. Then a mysql query is performed to see if the fop2users table is created in the AMPDBNAME database, if so, then it uses the fop2admin settings, if not, the default asterisk setttings.
