Mar 14

VOIP Security

VoIP technology introduce tremendous advantages for the telecommunication industry and changed the way we communicate in our life.

VoIP is everywhere today, applications running on your smartphone to your telco provider barebone network or interconnections.

VoIP has also earned a place among the trusted technologies an enterprise will choose to deploy in order to provide advance features to end users or a way to cut down costs.

But we used to overlook an important aspect of VoIP, security. Pay no attention to security and soon you will regret.

VoIP cost, functionality and reliability are of course important concerns but security should be a major issue too and you should be aware of the voip security concerns.

Continue reading →

Jul 12

Mobicents Arquillian Sip Servlets Extension 1.0.0-ALPHA1

The 1.0.0-ALPHA1 release of the Arquillian Sip Servlets extension has been released.

This extension will bring all the goodies of Arquillian to Sip Servlets testing. It provides two embedded containers, Tomcat 6 and Tomcat 7, running Mobicents Sip Servlets 1.7.0.

Together with SipUnit 2.0.0, this extension will provide a complete environment to test Sip Servlets applications. And of course since SipUnit uses Junit, tests can be performed either inside an IDE such as Eclipse or using Maven surefire.

You can have complete control over the container’s lifecycle and also the test archive deployment (your Sip Servlets application) in order to meet the special needs of any testing scenario.

User Guide can be found here

Several examples of the project can be found here

Any bug you discover or you have a feature that you would like to see in the next release, please post it here

Maven artifacts can be found in the following repository:

            <name>Mobicents Releases Repository</name>

Any feedback would be much appreciated in order to improve the project.

Mar 12

Locating SIP Servers – Comments on the RFC3263 for SIPS URIs

RFC3263 describes the DNS procedure and guidelines to be followed in order to locate SIP Servers. From the abstract of RFC3263:

The Session Initiation Protocol (SIP) uses DNS procedures to allow a client to resolve a SIP Uniform
Resource Identifier (URI) into the IP address, port, and transport protocol of the next hop to contact. It
also uses DNS to allow a server to send a response to a backup client if the primary client has failed.
This document describes those DNS procedures in detail.
When it comes to implement the proposed guidelines from RFC3263 in order to locate SIP server, the specification doesn’t seem to cover enough all the possible situations, specially for SIPS URI, and that is why we should consider to change some points there.
The purpose of this post is, first to indicate which points of the proposed RFC3263 mechanisms could create problems when it comes to resolve the transport for SIPS URIsĀ and how these points should be changed by applying some rules on the results of the DNS query. Second this post provides what is the minimum DNS configuration for SIP, that is the minimum required NAPTR, SRV and A records according to the RFC3263.

Continue reading →

Apr 11


With the advent of JSR 299 CDI it was about time to present a framework for Sip Servlets based on CDI and so CDI-Telco-Framework is here. Check the release announcement in the Mobicents google group.
In this article I will try to provide an overview of what CDI-Telco-Framework can do for you and a tutorial for your first application based on CTF.

Continue reading →

Apr 11

CTF and MSS 2.0.0.Alpha2

CDI-Telco-Framework 1.0.0.Alpha1, that supports all the versions of MSS 1.x and MSS 2.x, and MSS 2.0.0.Alpha2 on Tomcat 7.0.8, just released.

Check the release announcement in the Mobicents google group.

Please give it a try and provide your feedback.