Upgrading your SIPIS installation

The following document describes SIPIS upgrade process.


Upgrading SIPIS server from Debian 7 Wheezy to Debian 8 Jessie is not supported by Acrobits. If you want to run SIPIS on Debian 8 Jessie, please do a clean installation.


Make sure that you have only this server set up as NotificationServer in your Settings.xml file: <NotificationServer Name="*" Host="pnm.cloudsoftphone.com" Port="6552" Premium="No" RequiresTls="Yes" />

Backing Up

We recommend that you create a full backup of your SIPIS machine before the upgrade. At minimum you should backup the following:

  • File /etc/sipis/sipis.key
  • File /etc/sipis/Settings.xml
  • Your certificates and keys.
  • The sipis database.
  • If you use stunnel backup also /etc/stunnel directory.

Doing the upgrade

Upgrading SIPIS can be as simple as doing

aptitude update && aptitude upgrade

The upgrade process may ask you whether you want to replace your configuration files with new defaults. You should review these requests. If you are unsure, answer No. If you answer Yes, the system should leave a backup file at the same location with dpkg-old added to its name. If you answer No, the system will create new file in the location with .dpkg-dist added to its name. In both cases you can review the differences between your configuration and new default configuration and adjust your settings as you wish.


You may want to use new configuration files for logrotate (located in /etc/logrotate.d).


Do not forget to change NotificationServer as described above.

stunnel on Debian Wheezy


We do not support Debian 7 Wheezy anymore.

If you use stunnel on Debian 7 Wheezy there may be a manual step that needs to be done. The old installation guide advised to create file /etc/stunnel/stunnel.conf. The tcpudpbridge package creates a new configuration file in /etc/stunnel/tcpudpbridge.conf. You should replace this file with your old configuration. In most cases this is as simple as running

mv /etc/stunnel/stunnel.conf /etc/stunnel/tcpudpbridge.conf

and then restarting stunnel by running

service stunnel4 restart


The reason this step is not done automatically is that you may have other services configured in your /etc/stunnel/stunnel.conf file.