Funny thing is I can logon to the machine as root and start the server. If you come up with a solution, please share it here and if anyone else has a suggestion then I am ALL ears well eyes really. I have everything working including FOP, I just get this message in the system status window.
So I assume its a bogus message, it just annoying to have it keep poping up. I did some checking and when looking into the amportal. Last I checked the FOP does not work with any version of asterisk 1. Is your system build from a distro?
Also I installed all freepbx moduels available. If not please report it to them as they might have a minor install issue. Once you buy a license, you will receive an automated email with an activation code. Save that code somewhere safe as you will be required it to enter it whenever you want to perform license actions. To activate the license you need to know the activation code, and you have to chose a registration name.
White label versions won't display any footer. Note If you manage several boxes and licenses, it is wise to use a name that will help find or keep track of the activation codes in the future. It will prompt for the activation code and then the registration name. If you want to pass that information in one pass, then you can try:. Otherwise FOP2 will fail to start. Some times you need to upgrade your hardware, change your network configuration, or move your virtual server.
In those cases, your license will most probably break after the change. So, before doing anything to your installation, you must revoke your license with the command:. You will be prompted for your activation code. To verify you have a valid license you can run:. As mentioned before, FOP2 has two components: a server daemon and a web application.
Files are placed in specific locations for both components. It is not the standard location for applications in the diverse distro universe, but for the sake of simplicity we decided to settle with that location. So, if you installed from tarball using the make you will find the daemon and its configuration files under that directory.
On the other hand, if you installed from tarball but copying files by hand, you might have placed the daemon files somewhere else. Also, to keep things simple, all server config files will be placed under the same directory as the server binary itself, including the fop2. If you want to place config files somewhere else, you can always specify the directory for config files using the -c command line option.
The web client files are located under your web server web root, that changes depending your Linux distribution. The most important and required parameters for this file are the Asterisk Manager credentials. Below you will see the two files side by side so you can check how a correct configuration should look for both files. Please be sure not to remove nor modify existing users or settings in the manager. You will also need to check that enabled is set to yes.
If you are installing Asterisk by hand, then you must be sure that manager. FOP2 configuration files are very similar in format to regular asterisk. The Asterisk Manager must be enabled, and the manager user needs to have sufficient permissions. The above example shows the manager bind to the loopback interface on the Asterisk machine on port , with access control defined to only allow connections from the same interface There are also a set of write and read permissions.
As you can see, fop2. If you change only the user, secret or ACL, an asterisk reload is enough. If you access your server using https, you must configure FOP2 to use the same SSL key and certificate files as your web server. Otherwise you will experience very slow login times as FOP2 will fail to establish a websocket connection due to browsers security policies , and it will end up fallling back to Flash XML Sockets, something that could take 10 or more connections attempts.
The default fop2. After doing that, restart FOP2 with the command:. Besides enabling the manager that is mandatory there are other parameters in different asterisk. For older versions of such backends 2. The above setting will send events related to queues and agents. In Issabel and most configuration backends you can set the parameter in the queue configuration page. The default FOP2 configuration uses the exec directive to configure users and buttons based on information stored in a database managed by the FOP2Manager module.
Static users added in fop2. If you want to do manual configuration as described below, then you have to comment the exec line by adding a semi colon in front so it becomes ; exec.
In order to load the panel, a login is mandatory. You login as an extension, and that extension will become the origin extension for actions like dial, transfer and spy sessions. Permissions and Groups can be comma separated lists. The group is optional and it will only work if you define some groups as explained in the next section. The group feature was introduced in version 2. Since FOP 2. You can later assign groups to users to limit the extensions a user is allowed to view.
Those groups can be assigned to a user definition. If you do that, the user will be only allowed to see devices listed on that group. If you need to have more than one view showing different groups of extensions or buttons for multi tenant setups, call center groups, etc you can use contexts.
You define a context by naming it between brackets. This is a complete example:. You will have to configure each buttonfile with the appropiate group of extensions you want for each context. To view the context you have to specify its name while loading the web page inside the GET request. In big setups or hosted environments you might have more than one asterisk machine that you need to monitor. You can run a separate fop2 instance in each server, or you can run fop2 in just one server monitoring several asterisk machines.
If you do not specify the server in the button definition the action you perform will be broadcasted to all servers, also, queue buttons on others servers than the 1st won't work if the server definition is lacking. Besides the server configuration, it is important to configure the buttons you want to display, either for the default or general context, or for any other panel context you define.
If you use a suppoerted backend like Issabel, Thirdlane, Ombutel, etc, and you have the FOP2 Manager installed you do not need to configure buttons via configuration files at all.
They will be created for you, and you can configure them using the FOP2 Manager, so you can skip this chapter. Button configuration is done on separate config files so they are easier to maintain and organize.
For example:. This kind of buttons will represent a phone or extension. It will display two lines for each button and some specific information, like presence, pause state, etc. Queue buttons do not accept mailbox or extenvoicemail parameters, as they only apply to extension buttons. Ring Group buttons are not capable of tracking Ring Group status, they are only used as a transfer target, so you can transfer calls to a RingGroup.
Ring Group buttons do not accept mailbox or extenvoicemail parameters, as they only apply to extension buttons. For trunks there are very little parameters to set. A trunk cannot be dialed, for that reason you do not need to specify extension nor context. Only the type "trunk" must be specified, together with the button label. The trunk button is fairly straightforward to setup: you must be sure to set the extension to your parking extension number, and if you do not use parking name spaces Asterisk 1.
The exec directive lets you specify a script to be run when FOP2 is started or reloaded and that outputs valid config data. Please do not remove the , it is not a comment, in order for this directive to work the line must start with exec. This way you can write a script that extracts configuration from a database, for example, and writes the appropriate config parameters from there.
Any output that is generated from a script will be interpreted, including other exec directives. This is pretty powerful but also dangerous. You will have to be careful not to produce loops, and also that the output contains only valid configuration data.
Included in the distribution there are a couple of scripts to configure users and buttons automagically. To use them, just configure fop2 as follows:. Instead of setting up each user for FOP2, by using this script it will read asterisk's voicemail.
Finally, the button configuration will be read from your backend MySQL tables and populated for you. Be careful as the automatic configuration does not configure the correct manager credentials, and it does not set up any databases or tables for the visual phonebook.
It just setup users and buttons for FOP2. Among the most important configurations you can set you have: the language to use on the client, whatever to use HTML5 websocket or not, and optionally the presence options. You can set any number of options and their hex colors, do not remove the first 2 lines as they are mandatory.
The empty presence is the one for the "available" state. This feature lets you select one of the options you define, and it will flag your extension with that color and a tooltip with the text description when someone mouse overs the presence icon.
This way a receptionist will get a hint about your availability to take calls without the need to ring your phone. Also, you can make Asterisk do stuff when the presence is changed.
There are currently two plugins for doing this:. The later will instead perform a queue member pause action with reason. You can also do so from the queue member list in a queue button. Since FOP2 version 2. Evaluate Confluence today. Pages Blog. Page tree. Browse pages. A t tachments 0 Page History. Jira links. Daver Jorge. Permalink 03 Jun ,
0コメント