I signed off on distributing the 0.3 release of #SipWitchQt for initial public availability, starting today.
Perhaps the easiest way to setup a local sipwitchqt server is with our #Ubuntu #GNU/Linux #ppa. Simply install from the ppa:
sudo add-apt-repository ppa:tychosoft/ppa
We also have a debian archive which includes arm builds you can use with raspian. For #Debian, add: "deb https://www.cherokeesofidaho.org/public/ debian/" to a debian sources list. The debian packaging we made can be adapted for #Devuan and also includes a standard init script, if someone wants to adapt and test it there.
You can then install a server preset to use a local sqlite3 database:
The swlite-initialize will setup your local sqlite3 database properly.
The more adventuresome can install sipwitchqt-server and sipwitchqt-utils instead of sipwitchqt-local, set #mysql config credentials in the /etc/sipwitchqt.conf file, and use ipl-sipwitch to create an initial mysql server database for your server.
You can then start loading clients on other machines with: sudo apt-get install sipwitchqt-desktop
It is possible to package #rpm builds, and anyone could use our default rpm spec with the #opensuse build system.
Since sipwitchqt uses #zeroconfig, most of the client config will be plug and play from your debian server if on a local network. You would login with your first desktop client using the extension # and secret you defined in swlite-initialize. From the phonebook in the client application you can add additional extensions and define groups as needed.
during what was otherwise mostly a very difficult year, work began on a new sipwitch server over six months back. Because there had not been much progress on it since September, I finally held a release planning meeting this past weekend simply to help define what a future minimum first (0.1) release might eventually one day be. Out of that discussion came a decision to provide a dedicated sipwitch specific voip client. I thought I would show an early mock-up of the proposed SipWitchQt desktop client ui that was discussed to see what others might think of it.
This past week was a good week for getting some further work done on the new SipWitchQt voip server. Naturally I am using a #GPLv3 license. A lot of initial development is being done on #fedora and #debian, though the project is also cross-platform.
I no longer see sip interop as the space to offer truly secure communications the way I once did last decade. Still there are other interesting roles and purposes in the sip interop space that I do want to explore further, and this seems a fun way to do so. In particular, offering a pure general purpose enterprise sip server that can be deployed embedded, locally, containerized, or even cloud deployed, depending on need and entirely at the user's choice, seems interesting in it’s own way.