FOP2 Community Forum

FOP2 by default does not hide unregistered extensions. Does not hide invalid queue member names. If you tweak styles to hide/change presentation, then using some client/presentation features might bring them back to view, as those feature set/unset css properties like display:none; etc. So, what you see is actually expected, you hide something via css but using filters, that set/unset css properties, they are displayed back. As for the label names, I have no idea. I told you when and why fop2 renames labels, but it seems it is not your case. You use your own autoconfiguration scripts, I do not know those scripts nor I know your configuration as a whole. A FOP2 button is NOT renamed in any other case, only when a Local queue member is added that matches the extension/queuecontext of the buttons.cfg definition. It is not clear either WHEN does the change happen. Is it in runtime? or whenever you restart fop2 in different ways? Perhaps you have TWO set of configurations you are not aware of, one when starting fop2 as a service, and another when starting from command line. This is a wild guess as your configuration is yours and there is not much info about it.

Hi, With version 2.28 there is no need to create tables, as the fop2 manager will create them for you. You only need to create the database and have a user created for mysql with the power of creating tables configured in fop2.cfg When using the manager in vanilla asterisk, some things will need to be modified in the .php code, mainly functions-astdb.php , to try to match your environment. There is no way to guess what is an extension vs. a trunk, etc, on any potential asterisk setup out there. There are many assumptions being made in there that can be tweaked or modified for your particular environment/setup. Whenever you log into the buttons page, some functions will be run in order to get your extensions/queues/trunks/conferences configuration, and update tables based on that (if there are new extensions, you want them incorporated into fop2 tables). However, your users table should not be changed. that seems more like a bug, not sure if I will be able to try to reproduce the issue locally: to try to understand, you create a user, then go to "fop2 buttons" and when going back to "fop2 users" that user is gone ? Best regards,