buttons_custom.cfg not being loaded

[atsak]

It says there is no buttons_custom.cfg

But there is - here's the directory listing. I must be missing something simple.
-rw-r--r-- 1 root root 91 Aug 25 01:07 buttons_custom.cfg

root@pbx:/usr/local/fop2 $

OK I found if I changed the script to use the full path /usr/local/fop2/buttons_custom.cfg, the autoconfig freepbx script will now call the file correctly.

Except it still doesn't show up in the panel.

What's my next step?

[nicolas]

Problem with buttons_custom.cfg is that if you define groups for users, they won't show up as they will not appear in the group definitions.

[atsak]

But I don't have any groups for users . . . that's what I keep saying.

Really! I have never defined a group for users. It's just the default settings. I can't figure out how to post a screenshot of my freepbx fop2 admin screen shot where it shows no groups are configured . . . but I have one to prove it if you want

[nicolas]

Do not look at the fop2admin screen, but at the output from autoconfig-users-freepbx.sh script, that way you know for sure if you have groups assigned or not, look for the user=xxx lines, the 4th parameter is the group.

In any case, if your button config shows when you run autoconfig-buttons-freepbx.sh and you do not see it in the fop2 screen (after reloading fop2, if you change your button config you must reload fop2 server and also relogin to the web client), it is probably there is something missing or incorrect in the button definitions themselves, from what I read about your sample, it is correct, so it should show. It is mandatory to set the type, the type must be valid (type=extension), and you also must put the extension, context and label values. If one of them is missing , the button will not show.

Also, be sure you are using the registered version so you are not bitten by the 15 buttons limit of the free version.

[atsak]

I gave up trying to get this working, but I am upgrading to the new version and thought I'd try again.

Does the AMI manager user and secret need to be the same on the external server for it to work? In other words, how does it query the external server for status?

[nicolas]

Hi,

Passwords can differt, there is no reason to make them the same, you can specify any password, host, user, port, etc.

Making this work is not hard at all, but fop2 restrictions might come into play for displaying the buttons ON THE WEB BROWSER, not so when running the autoconfiguration script as I suggested above.

If you see the buttons when running the autoconfig script, but not on the browser, then your limitation is for buttons groups assigned to users, as custom buttons will not be placed into groups.

The new version will work the same as the old one, just try to catch me on the live help and I will guide you on making it work.

[TRAFSupport]

Hello,

I am having a similar issue.

I have FOP2 registered and set up to monitor two servers and because I am using FreePBX, I have to define buttons for these users manually using the "server=" value.

When I run autoconfig-users-freepbx.sh, it does show that it is parsing the buttons_custom.cfg file, but the custom buttons do not show in FOP. I originally tried with no groups set in FreePBX, then I tried setting up a group ("ALL") and manually joining that button to it using a "group=ALL" value, but it still does not show up. I have ensured that the user I am logging into FOP2 as, is able to see that group.

The test extension in buttons_custom.cfg looks like the following:
[SIP/${XXXX}]
type=extension
extension=${XXXX}
context=from-internal
label=${LABEL}
server=${HOST_IP}

With an optionally added "group=ALL" for after I tried creating a group to see if that would help.

Any information as to why I can't get these buttons to show up would be appreciated.

Thank you,

[nicolas]

Hi,

There are 2 things to check. That the include of the custom button config file has a full path (if you run fop2 from the init script, an #include buttons_custom.cfg will probably fail, while #include /usr/local/fop2/buttons_custom.cfg will work).

The other thing to check is still the groups. If you want to see custom buttons, your fop2 user should not have ANY groups clicked on the fop2 users page in Fop2admin. You have to check that by running:

/usr/local/fop2/autoconfig-users-freepbx.sh

you should have something like

user=100all

if you have

user=100all:somegroup

you will face issues unless somegroup includes the buttons for the custom config file, and as somegroup is autogenerated, it will not contain anything!.

[TRAFSupport]

Thanks,

I got it working now, however how I did it was not what I expected. It looks like when you set FOP2 to connect to multiple servers, if you build the extensions as a mirror on both servers, FOP2 picks up hints from whichever is actually registered/active. There is no need to create any custom buttons using the "server=" value what so ever.

The added advantage is I can also use display groups without it affecting the visibility of the buttons. I don't know if this will work for others, but this might help people who are having issues with the FreePBX admin module and monitoring multiple servers.

Thanks,

[nicolas]

Hi,

FOP2 does not discretely monitor same device name across multiple servers. It was mentioned many times in the forum:

View Post 495

You cannot have a button for SIP/100 on server A and another button for SIP/100 on server B. FOP2 will group activity for SIP/100 no matter the server it is located.

This is why you cannot monitor DAHDI trunks on multiple servers for examples, let alone DAHDI extensions. Well, you can, but you cannot do that discretely.

Best regards,