Installation

Installing from tarball

If you install from tarball be sure to download the one corresponding to your glibc version. Please check the System Requirements page to find out what glibc version you have.

After downloading the proper package, you will have to extract it with the command:

Change to the extracted FOP2 directory:

For the sake of simplicity, included in the tarball there is a Makefile that can install the files for you, just type:

The installation will copy the server files under /usr/local/fop2 and the web pages under /var/www/html/fop2, /var/www/fop2 or /srv/www/htdocs/fop2 depending on your distribution. It will also copy an init script for you.

FreePBX integration

For a complete FreePBX integration experience, you will need to copy a configuration file manually. It is not installed automatically because you might be already using the configuration file for other purposes, so it is left to be done by hand. The file in question is extensions_override_freepbx.conf located in /usr/local/fop2, and must be copied into /etc/asterisk . If you already have some content in that file, do not overwrite it but append the contents. This file is needed if you want to integrate FOP2 presence with FreePBX DND feature code. You do not need to do this if you are not using FreePBX.

To append the contents to the end of your original file:

Visual Phonebook

Installation instructions for the visual phonebook are available here

Copy files by hand

You can also opt to install the files manually and place them to suitable locations on your hard disk. For example, you can move the daemon files and configurations to /usr/local, and the web pages to a directory inside your webserver web root:

Before starting the service, some basic configuration is required in fop2.cfg and probably in /etc/asterisk/manager.conf, because the FOP2 daemon connects via TCP to the Asterisk Manager Interface (AMI) using a username and secret. The basic daemon config is covered here.

Once that the files are in place and the manager credentials configured you will have to start the service. There are a number of ways to do that. The best way is to use a proper init script for your distribution, another way is to start it from /etc/rc.local.

That's it!