FOP2 and several Asterisks

[avayax]

I have an internal server where I am hosting my FOP2 server on. Now I also have a hosted instance where all my remote clients connect to. In FOP2 manager and panel I would like to be able to see and manage all of my extensions, regardless what server they are on.
How would I do that?

[avayax]

According to the documentation I have found, I have to add the remote extensions on the second Asterisk server manually, which would look like this:

[SIP/100]
type=extension
extension=100
context=some-context
label=John Doe
server=192.168.0.1

Is that correct and to what file do I have to add this entry?

[nicolas]

That is correct, but then you have groups that you might have assigned, and if those groups do not include a remote server button, then you won't be able to see it. As for what file, it depends. The default configuration uses scripts to do automatic discovery of everything, that won't work. So you have to go totally manual for configuraitons (adding user=xxx lines in fop2.cfg, buttonfile=buttons.cfg and then add all your buttons either local or remote to buttons.cfg). Or you can tweak the auto config scripts to incorporate remote buttons somehow.

[avayax]

Thanks.
What is a remote server button in a group?

So do you mean, that I would have to go manual for both my local and remote extensions?

[nicolas]

When using the fop2 manager, you can create groups and then assign groups to a user to limit what he can view. As those created groups contain only local buttons, if you select groups for any given user, then any remote or custom/manual buttons you might have added won't appear. So, if you add remote buttons while manteining the fop2 manager autoconfiguration, you must not select any groups for any user, as it will be limiting those custom buttons from view.

You can add custom buttons while still using manager configuration by adding things to:

/usr/local/fop2/buttons_custom.cfg

But remember NOT to use groups (do not select any groups on the user tab in the manager).