FOP2 Community Forum

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.

The best way to look for possible events is to start fop2_server in debug mode 15, and look for lines like this one for commands sent to flash clients: 127.0.0.1 => { "btn": "5@GENERAL", "cmd": "state", "data": "DOWN", "slot": "0" } You can edit jcallback.js and add a method to JCallBack to handle the "state" command. If the data is DOWN, the call is finished for the first line appearance (slot 0). Regarding the DID, that is probably set as a variable in the dialplan, things gets more complicated there as you should put hook on the server/ami side via FOP2Callbacks.pm, etc. The easiest way to handle this is to set the callerid name to be the did number inside the dialplan, so you will see it in regular ami events. Best regards,