[erlang-questions] [ANN] NkSIP Erlang SIP Application Server

[Carlos González Florido]

Yes, you are right.

NkSIP is clearly an OpenSIPS/Kamailio replacement (but NkSIP is not yet
even near the maturity of those projects, and I'm not a SIP guru with the
experience of the people backing them).

The reason to develop NkSIP instead of using OpenSIPS/Kamailio/etc. is that
(at least for me) it is quite complex and not "natural" to develop
applications with these SIP servers. I don't really fully support their
architecture with hundreds of modules... For me it should be more like an
application flow. You don't need a Least Cost Route, Call Detail Record or
distribution module, it is much easier to do it in your application code
within 50 Erlang code lines. At least using Erlang, I think it makes no
sense to have a lot of modules to connect to a lot of databases, just
implement the callbacks you need and use whatever backend you want.  I'm
not saying that being modular is a bad thing (NkSIP will probably have some
kind of modules or plugins in the future), but they should be much more
horizontal.

This approach is much simpler, now I have to prove it actually works ;-)

Another reason is that SIP is evolving quickly, and it is much, much easier
to add functionality using Erlang and a OTP structure that in low level C
modules.

Of course OpenSIPS and Kamailio should perform much better, but I suppose
this advantage is not so clear when you start using many processor cores.
Finally, NkSIP will have soon a fully distributed, highly available
solution. While you can build such a solution with those projects, it is
going to be much more difficult.

NkSIP looks like a perfect fit for Kazoo!




On Wed, Jul 10, 2013 at 11:23 PM, Tom Samplonius <tom@REDACTED> wrote:

>
> On 2013-07-10, at 12:10 PM, Motiejus Jakštys <desired.mta@REDACTED>
> wrote:
>
> Hi Carlos,
>
> this is very interesting and certainly a lot of work. Can you tell us
> more where this project is going? Is there (will be there) a company
> backing this? In my perspective, VoIP world certainly needs something
> better than Asterisk... So this is a certainly a great job, but what
> next?
>
> ...
>
>   All of bigger installations are using FreeSwitch (
> http://www.freeswitch.org/) instead of Asterisk.  The README says:
>
> NkSIP is a pure SIP framework, so it *does not support any real RTP media
> processing* it can't record a call, host an audio conference or
> transcode. These type of tasks should be done with a SIP media server, like
> Freeswitch <http://www.freeswitch.org> or Asterisk<http://www.asterisk.org>
> .
>
>
>   So, it looks like more of a replacement for OpenSIPS, which is often
> used a SIP load balancer, or session border controller.
>
>   If anything, NkSIP looks like a good component for Kazoo (
> http://2600hz.com/platform.html, https://github.com/2600hz/kazoo).  The
> Kazoo platform uses OpenSIPS and FreeSwitch, but most of the other stuff is
> Erlang (RabbitMQ, BigCouch, etc.).  Rather than using RabbitMQ to
> distribute SIP events from OpenSIPS/FreeSwitch between nodes and zones,
> using a SIP registrar on top of Riak seems a lot simpler.
>
>
> Tom
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20130711/9e4ad31c/attachment.htm>