Buttons Not Changing Name

Hello,

I have FOP2 v 2.26 installed in a few different locations and I've noticed a common thread among them all. When a name is changed on an extension, the appropriate button label does not update. Whether I restart the system, restart fop2, or reload asterisk, the label does not update. When I check in the DB directly, I can confirm this is the case:

mysql

use asterisk;

select exten,label from fop2buttons where exten>0;

The label on a few extensions should be different now, but does not reflect this change.


How can I force FOP2 to update these labels, and how can I make sure it will continue to do so as intended?

Comments

  • Perhaps the autoconfig-buttons-freepbx.sh script is not picking up that you have fop2admin installed , and defaults to the basic button and user setup. If you run

    /usr/local/fop2/autoconfib-buttons-freepbx.sh

    In the output you should see the conferences first, if you see sip extensions first, is because the fop2admin module is not being detected. You can force it by adding a line

    FOP2PLUGIN=1

    in the script, after the mysql query that tries to detect it.
  • Sorry to hijack your thread, but I have noticed the same behaviour on my system also running 2.26.

    I have changed a Conference Name in FPBX (v2.10.0.7) but this has not been reflected in FOP2 which is still showing the old conference name, even following a restart.

    In the autoconfig-buttons-freepbx.sh script I changed the line after "# Verify if the fop2 plugin table exists" to be "FOP2PLUGIN=1" rather than "FOP2PLUGIN=0", however this has not made any diference and the conference button name has not been updated, even following a full restart.
  • ok ok, stop stop.

    I think you are applying and incorrect fix.

    Fop2 labels do not change if you change a freepbx label, UNLESS you click the "refresh labels" buttons in the fop2 buttons page. That is not a bug, that is normal behavior. So, click that button and see if the name changes in the fop2 buttons page.
  • Yes apologies. Was on COMPLETELY the wrong track there. Have done a manual refresh as you suggested and all is well.

    Thank you again.
Sign In or Register to comment.