Author:
    Elena-Ramona Modroiu

• Kamailio (OpenSER) 3.1.0 installed.
• Web server (e.g., Apache) with mod_rewrite enabled
• PHP5 with MySQL and GD support

Latest version of SIREMIS 2.x is available at:

• http://siremis.asipto.com/pub/downloads/siremis/
• it includes everything, so you do not need to download something extra

Untar the archive on the local file system (e.g., in your web server root folder):

• cd /var/www
• tar xvfz siremis-x.y.z.tgz

If you want to setup an alias for Apache 2.x, you can run 'make apache-conf' and you get the config snippet printed:

siremis-2.0# make apache-conf
# siremis apache conf snippet ...

	Alias /siremis "/var/www/siremis-2.0/siremis"
	<Directory "/var/www/siremis-2.0/siremis">
		Options Indexes FollowSymLinks MultiViews
		AllowOverride All
		Order allow,deny
		Allow from all
		<FilesMatch "\.xml$">
			Order deny,allow
			Deny from all
		</FilesMatch>
		<FilesMatch "\.inc$">
			Order deny,allow
			Deny from all
		</FilesMatch>
	</Directory>

You can copy&paste it to Apache conf file (e.g., for Apache2 on Debian/Ubuntu: /etc/apache2/sites-available/default).

This will make SIREMIS available under http://yourwebserver.com/siremis/. If you want to use a different alias, edit Makefile and change the value of URLBASE

Next step is to create .htaccess and Siremis configuration files, you have to run 'make prepare':

siremis-2.0# make prepare
updating htaccess file...
updating app.inc file...
done

Make sure that following directories have write access for web server user:

• siremis/log
• siremis/session
• siremis/files
• siremis/themes/default/template/cpl

Do not forget to restart the web server after doing the changes in its configuration file.

Database server to be used is MySQL.

You have to create a MySQL user that has access to Siremis database, for example:

GRANT ALL PRIVILEGES ON siremis.* TO siremis@localhost IDENTIFIED BY 'siremisrw';

This user will be needed later during the installation, of course, you can use an existing MySQL user that has enough privileges.

Also, you have to create Kamailio database with kamdbctl tool, if you don't have it already:

kamdbctl create

You don't need to do anything else to setup the database of Siremis 2.0, the rest of the process is down via web installation wizard.

Once you have done the steps above, access the web page:

• http://yourwebserver.com/siremis/

When you do it first time, you are redirected to an installation wizard. Follow the steps.

You get a page to start the setup process.

First step shows the status of required items. You have to update local configuration until all the items are checked ok.

In the second step you have to introduce the details to access Kamailio and Siremis database.

When you install Siremis first time, you probably have to check:

• Create Siremis Database - this create database 'siremis'
• Import Default Data - this imports initial data into database 'siremis'
• Update SIP Database - this updates the structure of Kamailio database for accounting and charts modules
• Replace DB Config - this updates Siremis configuration file with the details to access databases

This page presents a status report of installation, showing whether the required directories have writable access and summary of database access details.

This is the end of installation, presenting the username and password to login to Siremis. This page is automatically redirected to login page after a short period of time.

The login page has a protection for blocking login bots, asking to enter a code printed in an image.

After first login, do not forget to update the password for user admin.

• remove the install directory: siremis/install

If you want to run again installation wizard:

• restore directory: siremis/install
• remove file: siremis/install.lock

These are special Siremis components that need further configuration in order to work:

• Install Accounting Services
• Install MI Commands Panel
• Install Charts Services

Siremis is an administration tool, it is recommended to:

• run it in a private network
• run it over HTTPS
• add extra protection at HTTP server or firewall layers (e.g., HTTP auth, IP restrictions, etc)