Sipcraft will be an enterprise class on-premise IP telephony system.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
David Sugar d3af01ec1e TLS for upstream support (!45) 21 hours ago
cmake Start of MQTT provisioning support (!44) 3 days ago
server TLS for upstream support (!45) 21 hours ago
test Improved nonce support (!39) 3 weeks ago
utils Start of MQTT provisioning support (!44) 3 days ago
vendor TLS for upstream support (!45) 21 hours ago
.clang-tidy Start of MQTT provisioning support (!44) 3 days ago
.gitattributes Start of MQTT provisioning support (!44) 3 days ago
.gitignore TLS for upstream support (!45) 21 hours ago Prep for next release (0.1.1) 3 days ago
CMakeLists.txt Prep for next release (0.1.1) 3 days ago Update primary docs for gitea (#22) 4 months ago
Doxyfile Resolve "Improve Quality" 6 months ago Initial checkin 11 months ago Start of MQTT provisioning support (!44) 3 days ago
TODO Initial checkin 11 months ago TLS for upstream support (!45) 21 hours ago Start of MQTT provisioning support (!44) 3 days ago

About Sipcraft

Sipraft is an enterprise class on-premise office ip telephony system. The service would typically be used in conjunction with a telephony application server, a gateway or external VoIP provider, and will support either manual or dynamic provisioning integrating with MQTT. Sipcraft can run on generic and lower end GNU/Linux servers, including the Raspberry Pi. Sipcraft and associated ip telephony services may also be provided in container images. My preferred installation target is Devuan GNU/Linux. A 3 digit local dialing plan and a maximum of 600 connected sip devices are supported by Sipcraft.

As an enterprise ip telephony server designed for wide integration, Sipcraft is commonly deployed with MQTT Mosquitto in conjunction with a web/app server such as switchroom, a dedicated Bayonne application server, and a management console. A golang web integration service is being written as a separate package to integrate with and dynamically provision sipcraft.

Alternate web and integration services may also be used in place of switchroom using sipcraft MQTT. These can then be tailored for the needs of specific markets. Sipcraft will also support facility automation as well as integrating a pa system, sip door entry systems, and sip enabled security cameras. Sipcraft will be able to register with external providers and gateways.

Sipcraft shares no common code with, but loosely relates to work on both gnu sipwitch and SipWitchQt. Sipcraft development is closely related to Coventry.


Basic documentation, including an architecture overview and roadmap, will be added as additional markdown files. An installation guide for various GNU/Linux distributions and BSD systems may also be added. User operation, server admin, and configuration should be similarly added here. Developer documentation can be generated from source file headers using Doxygen. Live documentation can also be made available over the web framework.


Sipcraft requires eXosip2 version 5.2.1 or later and either openssl or libressl to build and run. It also requires the Postgresql client libraries, 9.0 or later. If the systemd support library is present at build time then support for the systemd notify socket may also be added.

A typical "install" target is created to support local installation. This should include an example config file. A logrotate config can also be added. All running directories that may be required are either made by "install" or created when the service executes. Execution in daemon mode is performed by an init script or systemd unit file. The sipcraft.conf file (or custom.conf) should be edited for the postgres database that you will need to connect to.

Sipcraft will include a Ruby web integration service that can be optionally installed and started in daemon mode as well. The supporting database schema is managed thru Ruby Sequel, which can be executed to load the database and perform schema updates. Web service installation and database updates will be perform thru additional custom cmake targets.

When cmake is used to produce a Debug build this instance can be executed directly; no further install is required. The debug build uses the config file found in the test/ directory, and a test/custom.conf file can be added with configuration overrides for local developer testing. The preferred cmake build type for live installation and running of debug builds is RelWithDebugInfo.


A more complete overview of participation will be provided in This project uses cmake, and c++17 for core server development. We use the ctest framework for unit testing and gcovr for coverage reports. Sipcraft can be built with gcc or clang and can be tested on just about any posix platform, including bsd systems and maybe even MacOS, not just GNU/Linux.

This project project can also be built for running unit tests using the cmake ctest framework. This is enabled by default for Debug builds. To produce code coverage reports you can cmake a debug build with -DCOVERAGE_TYPE=gcov set. You can then use the make the "coverage" target and produce reports with gcovr or lcov. The "lint" target validates code with cppcheck and rubocop.


Support is offered thru When entering a new support issue, please mark it part of the support project. I also have Sipcraft packaging build support for some GNU/Linux distributions will be found on In the future maybe other means of support will become possible.