My perception is that SER is something like a kernel, but Kamailio a user-oriented distribution and ecosystem wrapper around it that serves to "practicalise" it in an applied way.<br><br>--<br>Alex Balashov - Principal <br>Evariste Systems LLC <br>235 E Ponce de Leon Ave <br>Suite 106<br>Decatur, GA 30030 <br>Tel: +1-678-954-0670 <br>Fax: +1-404-961-1892 <br>Web: http://www.evaristesys.com/, http://www.alexbalashov.com<br><br>Daniel-Constantin Mierla <miconda@gmail.com> wrote:<br><br>
Hello,<br>
<br>
if you install from sources, there is practically everything: ser +
kamailio together, it is up to you what modules you want to use.<br>
<br>
If you install from kamailio packages (debian, centos), you get only
kamailio specific modules (what is located in modules/ and
modules_k/).<br>
<br>
Maturity of the code is the same, I am more into kamailio specific
modules, though, since I use them. Kamailio is traditionally more
interactive in terms of public relations, having a clear release
policy, with packages built every time.<br>
<br>
Also, kamailio specific modules have more into SIMPLE extensions (I
mean here presence, xcap, ...), but this is not a problem since you
can use the modules with the ones developed in the past by SER. So
there is nothing different between Kamailio and SER if you install
from sources. As mentioned in the link, there are just some
inter-module dependencies, so when using a module, you have have to
use another specific one. This is actually valid in the same group
of modules (like in modules_k), one module requires another one.<br>
<br>
What really make the difference in a deployment is the database
structure used behind. If you start from scratch, it does not matter
probably, but people upgrading from older versions, tend to stick to
what they have, so they continue using one or the other.<br>
<br>
From my observations on this mailing list, it is more likely you get
people answering more often for kamailio than ser. Also, there are
more tutorials showing how to use kamailio, including integration
with asterisk, if that is main concern, for example:<br>
<br>
* <a class="moz-txt-link-freetext" href="http://kb.asipto.com/asterisk:index">http://kb.asipto.com/asterisk:index</a><br>
<br>
Cheers,<br>
Daniel<br>
<br>
<br>
<br>
On 4/9/12 9:43 PM, Daniel Gonzalez wrote:
<blockquote
cite="mid:CAAOi-OG+kF+MEQjoDrbop67+dj1Q-PJ-Yg_OgZNjBMwYDqvBdQ@mail.gmail.com"
type="cite">Thanks for the link.
<div><br>
</div>
<div>If I understand correctly, both projects share the same
source code, and implement more or less the same functionality.
<div>Is there a list of specific features which are only
available in SER or in Kamailio?</div>
<div><br>
</div>
<div>Which is the most widely deployed / documented option?
Which is more mature / stable? Which is the option which
interoperates easier with Asterisk?</div>
<div><br>
</div>
<div>Sorry for the beginner questions, but I have found no place
where this questions are adressed.<br>
<br>
<div class="gmail_quote">On Mon, Apr 9, 2012 at 9:17 PM,
SamyGo <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:govoiper@gmail.com">govoiper@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>:-|
</div>
<div><br>
</div>
<a moz-do-not-send="true"
href="http://www.kamailio.org/w/sip-router-releases/"
target="_blank">http://www.kamailio.org/w/sip-router-releases/</a>
<div><br>
</div>
<div><br>
<br>
<div class="gmail_quote">
<div>
<div class="h5">
On Mon, Apr 9, 2012 at 11:06 PM, Daniel Gonzalez <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:gonvaled@gonvaled.com"
target="_blank">gonvaled@gonvaled.com</a>></span>
wrote:<br>
</div>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<div class="h5">Hello,<br>
<br>
I am starting to deploy a SIP router, and after
reading the<br>
documentation in <a moz-do-not-send="true"
href="http://sip-router.org" target="_blank">http://sip-router.org</a>
I am a bit confused. I am<br>
planning to integrate the SIP router with an
asterisk PBX. Which of<br>
the available projects is recommended to get in
touch with the<br>
technology, SER or Kamailio? Which are most of
you in the list using?<br>
Is there a particular use case where one or the
other is more<br>
appropriate?<br>
<br>
Thanks,<br>
Daniel Gonzalez<br>
<br>
</div>
</div>
_______________________________________________<br>
SIP Express Router (SER) and Kamailio (OpenSER) -
sr-users mailing list<br>
<a moz-do-not-send="true"
href="mailto:sr-users@lists.sip-router.org"
target="_blank">sr-users@lists.sip-router.org</a><br>
<a moz-do-not-send="true"
href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users"
target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a><br>
</blockquote>
</div>
<br>
</div>
<br>
_______________________________________________<br>
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users
mailing list<br>
<a moz-do-not-send="true"
href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a><br>
<a moz-do-not-send="true"
href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users"
target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a>
<a class="moz-txt-link-freetext" href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Daniel-Constantin Mierla
Kamailio Advanced Training, April 23-26, 2012, Berlin, Germany
<a class="moz-txt-link-freetext" href="http://www.asipto.com/index.php/kamailio-advanced-training/">http://www.asipto.com/index.php/kamailio-advanced-training/</a></pre>