Mobicents in production – Attikis from the inside

Adam Warski

11 Apr 2011.1 minute read

One of the main parts of the Attikis system is a VoIP module that services incoming alarms and outgoing voice mail. The module was built 100% based on an open-source project, Mobicents. We used two components of Mobicents: Mobicents SIP Servlets and Mobicents Media Server.

When Attikis gets an incoming connection, first it is intercepted by one of our SIP Servlets. Thanks to a cohesive application writing model, people with JEE experience have little problem starting work with SIP Servlets. And everything runs on the tried and tested JBoss Application Server 5.1. Next, the servlet decides what to do with the connection. Usually a session with the Media Server is started. Because both servers come from the same platform, they have no problems working together and their integration is very easy. Mobicents Media Server receives the alarm signal, parses it and sends it on for further processing.

SIP Servlets also serve outgoing connections, made in order to inform users about alarms that have been set off. The Mobicents platform includes a TTS (Text-To-Speech) engine, which works out very well in testing, but due to the quality of generated sound we decided to use a different solution.

Our general experience with Mobicents servers is very positive. First of all, the software is very well written. Moreover, the programmers working on the project are very helpful; if you have any problems you can ask on the forum. A significant factor is that the project is open-source, so it’s easy to apply patches where the need arises (for instance in the Attikis project we had to adapt tone recognition to the high requirements of alarm systems).

And the most important thing: the Mobicents servers on Attikis production environments have been performing stably and without significant problems for several months now.

Blog Comments powered by Disqus.