That's what I was trying to say.

I have tracked the problem down by manually running the autoconfig-buttons-freepbx.sh and piping it into buttons-auto.cfg.

See my fop2.cfg file above. There are no #exec functions in the fop2.cfg. You'll notice that I have a group set up to only show 8 buttons out of the 100 in the buttons-auto.cfg file.

When I log in as user 1101, there are no buttons displayed.

If I edit buttons-auto.cfg and remove some extensions (it doesn't seem to matter what extensions) so that there are a total of 104 button definitions, only then are the 8 buttons from the group displayed.

I have FOP v2.11 Lite installed, with the FOP2Admin FreePBX module. If I use the autoconfig scripts, then I don't have any buttons. But if I use manual fop2 and buttons cfg files, then I'm ok if I make sure the extensions are lower than 105 or something.

Here's my test settings in fop2.cfg:

group=Support:SIP/1111,SIP/1112,SIP/1113,SIP/1114,QUEUE/101,QUEUE/102,QUEUE/103,QUEUE/104


user=1101:12345:all:Support
buttonfile=buttons-auto.cfg

I run "./autoconfig-buttons-freepbx.sh > buttons-auto.cfg" to create the buttons-auto.cfg file. I don't get any buttons unless I edit the buttons.cfg file and remove enough entries that I'm below 104 (or something, it's getting late)

I noticed another post that said I needed to edit the autoconfig-buttons-freepbx.sh script to change -ENB to -EB. I did that, but I don't think that is affecting what seems to be a limit.

Is it a limit of the Lite version to only allow a certain amount of button definitions, in addition to only showing 15?