Lightweight SIP application built on vert.x.
It's intended to be used as addon for full-featured PBX to implement programmable voice scenarios in Java (see motivation).
Long story short:
- need to program voice dialogs
- want to do it in Java
- want to do it without 3rd-party services, on open-source stack
- want to use mature open source PBX for other telephony tasks
There are several popular open-source implementations of SIP stack in JAVA, for example:
JAIN-SIP-ri - JAIN SIP API Specification contains low-level SIP messages processing, SIP sessions handling (see Dialogs and Transactions) and transport layer (see SipStackImpl).
Sip-servlets - Java SIP Servlet specification allows building full-featured PBX system, uses JAIN-SIP-ri for message processing and application servers for transport layer and SIP sessions handling.
We need trivial SIP application, capable of accepting incoming calls (UAS) and processing call using programmable scenario. Specifically, we want to handle most of the call processing (like registration, initiation calls with users, dialplans) using full-featured mature PBX and delegate IVR part to lightweight, easy to use and fun to work with Java SIP application.
We can use sip-servlets, but there are issues:
- SIP servlets have all features to build PBX - they can be used as PBX and programmable IVR both, but popular PBXs like Asterisk and Freeswitch are more mature technologies, and they perfectly suited to do call processing and require less resources.
- SIP servlets can be used as addon to PBX to process IVR, but they have lots of non-needed for our task features - this involves learning curve (SIP Servlets specification) and customization, troubleshooting and debugging becomes complex.
- SIP servlets are heavy (comparing to vert.x). Available implementations of sip servlets are running on application servers (like Tomcat or Wildfly), and vert.x Verticles are much faster to boot and require less resources.
- Available SIP servlets implementations use blocking IO.
Implementation is very simple, because we implemented only needed SIP processing, basing on invariants:
- UAC directly calls UAS - no proxying => SipSession = Dialog = Call (between PBX and robot-sip-server); at most 1 Dialog can be established from 1 INVITE request.
- No security and registration, no secure transport.
- No reinvites.
- Very lightweight SIP application implemented as Verticle
- Simplest possible system with minimal needed features. Trivial to undarstand and start working with.
- Vert.x (and Quarkus if you want) and Java ecosystem
See examples module in the repository.
Also see example with media (you can call this robot from softphone and hear phrase): example robot announcement
Project is hosted on gitlab: https://gitlab.com/ivoice-oss/robot-sip-server
Github repository is mirror.