...

If the server process is running and logs have no error, this means the WCS server is ready to work and you can start testing it.

...

All the ways to start WCS

Starting the server is performed with this command:

sudo systemctl start webcallserver

Since build 5.2.801, WCS is starting as service from flashphoner user for better security

Besides, you can start the server using:

cd /usr/local/FlashphonerWebCallServer/bin
sudo ./webcallserver start

In builds 5.2.840 - 5.2.863 this command starts WCS also from flashphoner user.

Environment variables setup

Environment variables and parameters of the start are set in the setenv.sh script. In this script you can se additional parameters for WCS Core and WCS Manager. Also, here you can set the parameter that prevent memory leaks on multi-CPU systems:

...

cd /usr/local/FlashphonerWebCallServer/bin
sudo ./webcallserver start standalone

Launching with different user permissions

Since build 5.2.864, the permissions to launch WSC are defined as follows:

1. The command

sudo systemctl start webcallserver

starts WCS always from flashphoner user, if the user exists in system

2. The command

./webcallserver start

starts WCS from root when executing from root

sudo ./webcallserver start

or from flashphoner user, when executing from other non-root user

This affects the stanadlone mode too

./webcallserver start standalone

...

Parameters are set in the setenvwcs-core.sh properties file.

Here yoiu can add any specific startparameters Additional launching options can be set in bin/setenv.sh file using the following varaibles:

...