Hello,

This is the google translation from your message:

Hello, sorry for my english.
I want to buy your software, is interested in creating a different set of buttons for different operators.

Below is quote part of the file fop2.conf

user = 373: passs: all: queues: spy: queuemanager
buttonfile = buttons_373_.cfg
;
user = 106: passs: all: queues: spy: queuemanager
buttonfile = buttons_106.cfg

How can this be implemented?
I after restarting the daemon works buttons_106.cfg

If you want to display some buttons for a user, and another set for another, you can create groups. If using just the general context in fop2, you can only have one button file. Groups are described in the documentation and there is also a sample in the buttons.cfg.sample file provided, they are simpler to setup than panel contexts:

group=sales:SIP/100,SIP/200
group=support:SIP/300,SIP/400
user = 106:pass:all:sales
user = 373:pass:all:support
buttonfile=allbuttons.cfg

In allbuttons.cfg you put all the buttons, just on one file. But when 106 logs in it will see the "sales" group only, and 373 the support group. If there are no groups assigned to users, they will see all buttons.

Panel context are perhaps more suited for multi tenant systems, where in fop2.cfg you can have:

[tenant_one]
user=100:pass1:all
user=101:pass1:all
buttonfile=buttons_one.cfg

[tenant_two]
user=100:pass2:all
user=101:pass2:dial,transfer,pickup
buttonfile=buttons_two.cfg

As you can see, you can have same extension users on different context, with different passwords and permissions. For this to work you must login to fop2 specifying the context via url get: http://your.server/fop2/?context=tenant_one

Everything is documented in the web site documentation, except for some new usage features on fop 2.20.