Installation
Starting the service
Once FOP2 is installed and AMI credentials configured you can start the service. In RPM based systems you do it with the command:
#> /etc/rc.d/init.d/fop2 start
In Debian or Ubuntu the correct command is:
#> /etc/init.d/fop2 start
If you installed from tarball and did not install an init script, you can also start fop2 by adding a line like the following at the end of /etc/rc.local:
/usr/local/fop2/fop2_server -d
Command line usage:
The service daemon can be started also by hand at the linux console. You can try by changing to fop2_server directory and running it from there, eg:
#> cd /usr/local/fop2
#> ./fop2_server
#> ./fop2_server
The options and parameters for the daemon are the following:
Usage:
fop2_server [options]
Options:
-?, --help
-p, --pidfile
-c, --confdir
-l, --logdir
-d, --daemon
-v, --version
-X, --debuglevel
-r, --register
-t, --test
Options:
--help Print a brief help message and exits
--pidfile
Specify the pid file to use when running in daemon mode.
Defaults to /var/run/op_panel.pid
--confdir
Specify where to look for the configuration files. If omited,
it will look for them in the same directory where op_server.pl
resides
--logdir
If specified, will write the log files to that directory. If
not, it will output to STDOUT and STDERR
--daemon
Run the server in daemon mode, detaching itself from the
console
--version
Display the version and exits
--debuglevel
Sets the debug level for the logs. It overrides the value
inside fop2.cfg
--register
Starts the registration process to unlock number of buttons.
After purchasing you will receive a code via email that you
have to enter here to license the software.
--request
Generates a license file request to register the product manually
if your server does not have access to the Internet. You will have to
email the text request to us via email.
--code
Register code to use for the registration process, to avoid being
prompted for it. Good for batch registrations.
--name
Name to use in the registration process, to avoid being prompted
--iface Interface to bind the license too. Default interface to use is
is 'eth0'
--test Test and check Asterisk Manager Interface connection and
credentials. If the test is successfull, the AMI is accepting
connetions and the service ready to be started. If it fails,
you will have to check the correct AMI configuration in
fop2.conf and /etc/asterisk/manager.conf

