<div dir="ltr">Yes, you are right.<div><br></div><div>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).</div>
<div><br></div><div>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.</div>
<div><br></div><div>This approach is much simpler, now I have to prove it actually works ;-)</div><div><br></div><div>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. <br>
</div><div><br></div><div>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.</div>
<div><br></div><div>NkSIP looks like a perfect fit for Kazoo!</div><div><br></div><div><div><br></div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jul 10, 2013 at 11:23 PM, Tom Samplonius <span dir="ltr"><<a href="mailto:tom@samplonius.org" target="_blank">tom@samplonius.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><br><div><div class="im"><div>On 2013-07-10, at 12:10 PM, Motiejus Jakštys <<a href="mailto:desired.mta@gmail.com" target="_blank">desired.mta@gmail.com</a>> wrote:</div>
<br><blockquote type="cite">Hi Carlos,<br><br>this is very interesting and certainly a lot of work. Can you tell us<br>more where this project is going? Is there (will be there) a company<br>backing this? In my perspective, VoIP world certainly needs something<br>
better than Asterisk... So this is a certainly a great job, but what<br>next?<br></blockquote></div><div>...</div><div><br></div><div> All of bigger installations are using FreeSwitch (<a href="http://www.freeswitch.org/" target="_blank">http://www.freeswitch.org/</a>) instead of Asterisk. The README says:</div>
<div><br></div></div><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div><div>NkSIP is a pure SIP framework, so it <em>does not support any real RTP media processing</em>
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 <a href="http://www.freeswitch.org" target="_blank">Freeswitch</a> or <a href="http://www.asterisk.org" target="_blank">Asterisk</a>.</div></div></blockquote><div>
<div><br></div><div> So, it looks like more of a replacement for OpenSIPS, which is often used a SIP load balancer, or session border controller. </div><div><br></div><div> If anything, NkSIP looks like a good component for Kazoo (<a href="http://2600hz.com/platform.html" target="_blank">http://2600hz.com/platform.html</a>, <a href="https://github.com/2600hz/kazoo" target="_blank">https://github.com/2600hz/kazoo</a>). 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.</div>
<span class="HOEnZb"><font color="#888888"><div><br></div><div><br></div><div>Tom</div><div><br></div></font></span></div><br></div></blockquote></div><br></div>