More than one Extensions section?

[Jeremy]

Is there a way to have more than one Extensions section, each with its own set of Extension buttons?
In my setups, all users are SIP and there is essentially one group of callers (representing different physical locations) and one group of agents who receive calls.
Ideally, I would like the FOP2 page to have one section of Extension buttons for callers and another, separated section of Extension buttons for agents (and then the usual separate sections for Queue buttons, etc.)
That would give my users a very simple at-a-glance view of which locations are calling at any given time in addition to agent availability.

[Geph]

I'm having the same issue, need to create Sales groups / sections.
Anybody solve this yet? - Am I just missing something?

Thanks

[nicolas]

Log into the FOP2 Manager, select the Buttons tab and fill the Group field for your extensions to whatever you want them to be.

[Jeremy]

What about by editing the buttons.cfg file directly? Is there a way?
The buttons tab doesn't show in the admin panel doesn't show me anything. Not sure why. Maybe because I am not using mysql?

[Geph]

Thank you Admin, this solved my issue.

[nicolas]

If you have a manual buttons.cfg file, then just specify a group header, like:

[SIP/100]
type=extension
extension=100
context=ext-local
label=John
group=Supervisors

[Jeremy]

That's exactly what I was looking for. Works like a charm.
Thank you.

[Jeremy]

Is similar functionality available for Queue buttons? I tried specifying a group for them, but no luck.

[nicolas]

There is no group function for queues. Queues are show all in their own group. I might change that in a future release as with 2.30 we are not tied to the column layout we had before.

[Jeremy]

I see the following in the 2.21.02 release notes...

Fri Jun 10 20:19:55 2016 -0300 
Add support for grouping queues in FOP2 server, client and manager

So does this mean 2.31.02 can now group Queues buttons like it can for Extension buttons?

[nicolas]

yes, exactly that.

[Jeremy]

This is a really nice feature. Thanks again.