- Adding Repository
- Installing SIPIS
- Configuring SIPIS
- Control and Maintenance
- Firewall configuration
To run SIPIS without problems, your hardware should meet the following requirements depending on the number of expected users.
Add our key and repository to Debian:
- Execute the following command to install our public key:
wget -O - https://dist.acrobits.cz/debian/acrobits.gpg.key | apt-key add -
The fingerprint for our key is 1DB8 E683 A6F4 919B BFF1 6A7C FFCC BAF7 9FF5 CF45
Create a new file
/etc/apt/sources.list.d/Acrobits.listwith the following content:
deb http://username:firstname.lastname@example.org/debian stretch main
You will get a username and password from Acrobits representative.
Installing SIPIS is as simple as running:
apt-get install sipis
This will install our packages
loadbalancer2 and their dependencies (mainly
After installation your SIPIS needs to be properly configured.
Choose a database password. Edit the script
/usr/share/sipis/installdb, put your password there and run it. This script will create user sipis in your database, database sipis and will populate your database with required tables.
The configuration is located in
/etc/acrobits/LoadBalancer2/Settings.xml. If you do not use TLS as a transport, default configuration should work fine for you.
LoadBalancer2 connects to sipis on 127.0.0.1:14998. If you change SIPIS listening address from the default one it will be necessary to change the configuration of
Backend to reflect this change..
If you use TLS, uncomment the following tags in the configuration file:
PrivateKey. For the latter two, enter the path to your certificate file (which should include all necessary intermediate certificates) and to you key file.
Certificate and PrivateKey must be readable by user
sipis. If your setup does not work, this is the first thing to look at.
Once you configure LoadBalancer2 and SIPIS, make sure LoadBalancer2 is enabled and started:
systemctl enable LoadBalancer2.service systemctl restart LoadBalancer2.service
/etc/sipis/Settings.xml. You can find full documentation here.
The only thing that needs to be set is the database password in the attribute
OpenString of the
Database element. Insert the password you used for the database. We also recommend you set
Administrator password and set an appropriate
Name for your SIPIS.
Server section choose a name to your SIPIS server. If you want more than one SIPIS servers sharing the database each of them must have a unique name. Change of this parameter will mean that SIPIS will not load its database entries (because it would think they belong to different SIPIS instance).
Address shows address where SIPIS listens to requests. We recommend keeping it
0.0.0.0 so that SIPIS listens on all interfaces. If you decide to change it, you will have to change the
Backend settings for LoadBalancer2 and replace address
127.0.0.1 with your chosen address. Change of this parameter requires restart of SIPIS.
HttpServer is a built in HTTP server. It is by default accessible on http://your_server:5000/stats. If you want it to listen only on localhost, change 0.0.0.0 to 127.0.0.1. You can also change the port (in that case adjust the configuration when setting up HTTPS registrations – see the following section).
With password set in
Administrator section you can use the HTTP interface to execute actions.
You can change the lock file name in
Lock section to match the name of your server if you wish.
The device sends the SIP registration information to SIPIS using HTTPS. This uses SIPIS HTTP interface. To make this communication encrypted it is necessary to place either stunnel or HTTPS proxy (or equivalent) in front of SIPIS. Here we describe two options: stunnel and nginx. If you do not know which one to choose, use nginx method.
apt-get install stunnel
Edit the file and set path to the key and certificate file for your server.
systemctl restart stunnel4.service
- To start SIPIS run
systemctl start sipis.service
To make SIPIS run automatically when your computer starts run
systemctl enable sipis.service
To stop SIPIS run
systemctl stop sipis.service
to reload it after configuration change run
systemctl reload sipis.service
SIPIS produces a lot of log output. We provide logrotate configuration file so that logs are properly rotated. Debian has logrotate installed by default.
Your SIPIS installation should be reachable from your customer’s devices on the following ports:
Your SIPIS should be able to connect to your SIP server on the port you use (typically 5060 or 5061 for TLS) and to pnm.cloudsoftphone.com on port 6552 (see note).