<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>
<font size="3" face="Times New Roman">
</font><font size="3"><font face="Calibri">Well… Sorry for this long post.</font></font><BR><font size="3" face="Calibri"></font> <BR><p style="margin: 0cm 0cm 10pt; text-align: justify;" class="MsoNormal"><font size="3"><font face="Calibri">I work 100% dedicated to SMB - Small
Medium Business. In this market there is an enormous growth of multiples
devices in all companies. Most of the SMB I work with are looking for:</font></font></p><font size="3" face="Times New Roman">
</font><BR><p style="margin: 0cm 0cm 0pt 54pt; text-align: justify; text-indent: -36pt; mso-add-space: auto; mso-list: l2 level1 lfo1;" class="MsoListParagraphCxSpFirst"><font face="Calibri"><font size="3">- Let their employees bring their own device
(BYOD);</font></font></p><p style="margin: 0cm 0cm 0pt 54pt; text-align: justify; text-indent: -36pt; mso-add-space: auto; mso-list: l2 level1 lfo1;" class="MsoListParagraphCxSpMiddle"><font face="Calibri"><font size="3">- Enable chat, voice and video, with presence
information in all devices;</font></font></p><p style="margin: 0cm 0cm 0pt 54pt; text-align: justify; text-indent: -36pt; mso-add-space: auto; mso-list: l2 level1 lfo1;" class="MsoListParagraphCxSpMiddle"><font face="Calibri"><font size="3">- Not have to pay for premium solutions like
sophisticated SBCs to enable the workforce to work either internally (in the
company) or externally (from the Internet);</font></font></p><p style="margin: 0cm 0cm 0pt 54pt; text-align: justify; text-indent: -36pt; mso-add-space: auto; mso-list: l2 level1 lfo1;" class="MsoListParagraphCxSpMiddle"><font face="Calibri"><font size="3">- Have a single number for voice and video in all
devices;</font></font></p><p style="margin: 0cm 0cm 10pt 54pt; text-align: justify; text-indent: -36pt; mso-add-space: auto; mso-list: l2 level1 lfo1;" class="MsoListParagraphCxSpLast"><font face="Calibri"><font size="3">- Reduced complexity, setup time and maintenance;</font></font></p><p style="margin: 0cm 0cm 10pt 54pt; text-align: justify; text-indent: -36pt; mso-add-space: auto; mso-list: l2 level1 lfo1;" class="MsoListParagraphCxSpLast"><font size="3" face="Calibri"></font> </p><p style="margin: 0cm 0cm 10pt; text-align: justify;" class="MsoNormal"><font size="3"><font face="Calibri">With all the above in mind, I believe
Kamailio is just wonderful, why:</font></font></p><p style="margin: 0cm 0cm 10pt; text-align: justify;" class="MsoNormal"><font size="3" face="Calibri"></font> </p><p style="margin: 0cm 0cm 0pt 54pt; text-align: justify; text-indent: -36pt; mso-add-space: auto; mso-list: l0 level1 lfo2;" class="MsoListParagraphCxSpFirst"><font face="Calibri"><font size="3">- It is inexpensive!!!</font></font></p><p style="margin: 0cm 0cm 0pt 54pt; text-align: justify; text-indent: -36pt; mso-add-space: auto; mso-list: l0 level1 lfo2;" class="MsoListParagraphCxSpMiddle"><font face="Calibri"><font size="3">- No limit or licenses for users. In this way any
employee can have their PC, their iPad or Android tablet, their iPhone or
Android phone, their table phone, etc.<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /><o:p></o:p></font></font></p><font size="3" face="Times New Roman">
</font><font face="Calibri"><font size="3">- Using the right device or software client (some of them freeware) they
can, once again, reduce cost.<o:p></o:p></font></font><BR><font size="3" face="Times New Roman">
</font><font face="Calibri"><font size="3">- Very key: Unlike several alternatives on the
market, Kamailio does not interfere with the RTP in between SIP clients, it
does raw media switching using RTPProxy. So, more complex SIP usage like in
video will not be affected by the SIP solution.</font></font><BR> <BR><font size="3"><font face="Calibri">I know that you can always find
the information to deploy such solution with the specs above. However, the
information is a kind of “scattered” and, unlike the alternatives that would
not address all the exposed issues, it takes quite long to get the server configured
to do what we want. And yes, maybe because I am just a newbie to Kamailio, sorry for that.</font></font><BR> <BR><font size="3"><font face="Calibri">With the above in mind I would
like to see, and of course contribute for, a “how to” to deploy a Kamailio
server with the following specs:</font></font><BR><font size="3" face="Calibri"></font> <BR><p style="margin: 0cm 0cm 0pt 54pt; text-align: justify; text-indent: -36pt; mso-add-space: auto; mso-list: l1 level1 lfo3;" class="MsoListParagraphCxSpFirst"><span style="mso-bidi-font-family: Calibri; mso-bidi-theme-font: minor-latin;"><span style="mso-list: Ignore;"><font size="3" face="Calibri">- </font></span></span><font face="Calibri"><font size="3">If you thing about companies with up to 10k
employees, each employee with up to 4 SIP terminals (i.e.: table phone,
cellular phone, PC and tablet), then you would need a solution scalable for 40k
devices.<o:p></o:p></font></font></p><font size="3" face="Times New Roman">
</font><BR><p style="margin: 0cm 0cm 0pt 54pt; text-align: justify; text-indent: -36pt; mso-add-space: auto; mso-list: l1 level1 lfo3;" class="MsoListParagraphCxSpMiddle"><span style="mso-bidi-font-family: Calibri; mso-bidi-theme-font: minor-latin;"><span style="mso-list: Ignore;"><font size="3" face="Calibri">- </font></span></span><font face="Calibri"><font size="3">All devices from a user should ring when
receiving a call.<o:p></o:p></font></font></p><font size="3" face="Times New Roman">
</font><BR><p style="margin: 0cm 0cm 0pt 54pt; text-align: justify; text-indent: -36pt; mso-add-space: auto; mso-list: l1 level1 lfo3;" class="MsoListParagraphCxSpMiddle"><font face="Calibri"><font size="3">- Calling outside (PSTN) should be impersonated so
the user would have a single number seem outside of the company.<o:p></o:p></font></font></p><font size="3" face="Times New Roman">
</font><BR><p style="margin: 0cm 0cm 0pt 54pt; text-align: justify; text-indent: -36pt; mso-add-space: auto; mso-list: l1 level1 lfo3;" class="MsoListParagraphCxSpMiddle"><span style="mso-bidi-font-family: Calibri; mso-bidi-theme-font: minor-latin;"><span style="mso-list: Ignore;"><font size="3" face="Calibri">- </font></span></span><font face="Calibri"><font size="3">The solution should have an internal interface
(LAN) and an external Interface (WAN/Internet), promoting RTP relay for NATed
devices.<o:p></o:p></font></font></p><font size="3" face="Times New Roman">
</font><BR><p style="margin: 0cm 0cm 0pt 54pt; text-align: justify; text-indent: -36pt; mso-add-space: auto; mso-list: l1 level1 lfo3;" class="MsoListParagraphCxSpMiddle"><font face="Calibri"><font size="3">- The solution should not interfere with RTP, meaning
no transcoding. If an end point fulfills the other part RTP offer, they would
connect. If not, it would be just rejected.<o:p></o:p></font></font></p><font size="3" face="Times New Roman">
</font><BR><p style="margin: 0cm 0cm 0pt 54pt; text-align: justify; text-indent: -36pt; mso-add-space: auto; mso-list: l1 level1 lfo3;" class="MsoListParagraphCxSpMiddle"><span style="mso-bidi-font-family: Calibri; mso-bidi-theme-font: minor-latin;"><span style="mso-list: Ignore;"><font size="3" face="Calibri">- </font></span></span><font face="Calibri"><font size="3">The solution should be able to record calls.<o:p></o:p></font></font></p><font size="3" face="Times New Roman">
</font><BR><p style="margin: 0cm 0cm 0pt 54pt; text-align: justify; text-indent: -36pt; mso-add-space: auto; mso-list: l1 level1 lfo3;" class="MsoListParagraphCxSpMiddle"><span style="mso-bidi-font-family: Calibri; mso-bidi-theme-font: minor-latin;"><span style="mso-list: Ignore;"><font size="3" face="Calibri">- </font></span></span><font face="Calibri"><font size="3">The solution should be able to use SIP trunk as
the way out to PSTN.<o:p></o:p></font></font></p><font size="3" face="Times New Roman">
</font><BR><p style="margin: 0cm 0cm 10pt 54pt; text-align: justify; text-indent: -36pt; mso-add-space: auto; mso-list: l1 level1 lfo3;" class="MsoListParagraphCxSpLast"><span style="mso-bidi-font-family: Calibri; mso-bidi-theme-font: minor-latin;"><span style="mso-list: Ignore;"><font size="3" face="Calibri">- </font></span></span><font face="Calibri"><font size="3">The solution should be able to integrate, via
RADIUS or LDAP, with the customer existing directory, most of the cases
Microsoft.</font></font></p><p style="margin: 0cm 0cm 10pt 54pt; text-align: justify; text-indent: -36pt; mso-add-space: auto; mso-list: l1 level1 lfo3;" class="MsoListParagraphCxSpLast"> </p><p style="margin: 0cm 0cm 10pt 54pt; text-align: justify; text-indent: -36pt; mso-add-space: auto; mso-list: l1 level1 lfo3;" class="MsoListParagraphCxSpLast"><font size="3"><font face="Calibri">Now, when look at these specs,
Kamilio does all of this! However, it may take one year before someone “Kamailio
dummy” like myself to get all the knowledge to do it. Of course I know I must
invest on more knowledge but the more companies easily install and start using
Kamailio on the enterprise, the better is my value if I get to know it in depth.
So that is why I would like to see a “working group” within the existing Kamailio
community, with more focus on easing up the deployment of it on the enterprise.
I believe more people had the same problem I am having: it is a lot to study
specially if you are not a programmer; because of it not a lot of SMB companies are using it,
making investing on learning it, in my case, low return.</font></font></p><p style="margin: 0cm 0cm 10pt 54pt; text-align: justify; text-indent: -36pt; mso-add-space: auto; mso-list: l1 level1 lfo3;" class="MsoListParagraphCxSpLast"> </p><p style="margin: 0cm 0cm 10pt 54pt; text-align: justify; text-indent: -36pt; mso-add-space: auto; mso-list: l1 level1 lfo3;" class="MsoListParagraphCxSpLast"><font size="3"><font face="Calibri">Cheers!</font></font></p><p style="margin: 0cm 0cm 10pt 54pt; text-align: justify; text-indent: -36pt; mso-add-space: auto; mso-list: l1 level1 lfo3;" class="MsoListParagraphCxSpLast"> </p><p style="margin: 0cm 0cm 10pt 54pt; text-align: justify; text-indent: -36pt; mso-add-space: auto; mso-list: l1 level1 lfo3;" class="MsoListParagraphCxSpLast"><font size="3"><font face="Calibri">Moacir<o:p></o:p></font></font></p><font size="3" face="Times New Roman">
</font><br> <BR><div><div id="SkyDrivePlaceholder"></div><hr id="stopSpelling">From: oej@edvina.net<br>Date: Fri, 21 Dec 2012 16:58:53 +0100<br>To: miconda@gmail.com; sr-users@lists.sip-router.org<br>Subject: Re: [SR-Users] RADIUS authentication<br><br><br><div><div>21 dec 2012 kl. 16:55 skrev Daniel-Constantin Mierla <<a href="mailto:miconda@gmail.com">miconda@gmail.com</a>>:</div><br class="ecxApple-interchange-newline"><blockquote>
<div>
Hello,<br>
<br>
Kamailio is used a lot in enterprises. Apart of the media processing
services (e.g., voicemail, audio conferencing), kamailio offers all
needed in an enterprise, including instant messaging and presence.<br></div></blockquote>We've done quite a lot of enterprise-style installations and also integrated with LDAP. As Daniel patiently have repeated, there is a problem with the </div><div>authentication so we can't simply use LDAP authentication, but have successfully implemented LDAP-based authentication in many places.</div><div><br></div><div>Do you have any other concerns or ideas on what we can do in the enterprise sector? We're quite open on discussing it.</div><div><br></div><div>/O</div><div><br><blockquote><div>
<br>
It still seems to be unclear for you where is the problem with
Kamailio and M$ directory or other existing user authentication
systems. Let me rephrase: the problem is in the specifications of
SIP, respectively in the user authentication mechanism required by
this protocol.<br>
<br>
SIP requires www-digest authentication mechanims. www-digest
authentication requires that password is stored in clear text or in
HA1 format. Maybe reading the page at next link puts more light:<br>
<br>
- <a class="ecxmoz-txt-link-freetext" href="http://en.wikipedia.org/wiki/Digest_access_authentication" target="_blank">http://en.wikipedia.org/wiki/Digest_access_authentication</a><br>
<br>
Now, the devices are the problem, because they can authenticate to
the server only using www-digest. Kamailio cannot do anything alone.<br>
<br>
Alternative to www-digest authentication is to use ssl certificates.
That is fine for Kamailio, but not many sip phones support it.<br>
<br>
Hope is more clear now. Kamailio is as friendly to enterprises as it
is for carriers or operators. It is nothing that can be done more to
run in enterprise environment.<br>
<br>
Cheers,<br>
Daniel<br>
<br>
<div class="ecxmoz-cite-prefix">On 12/21/12 11:20 AM, Moacir Ferreira
wrote:<br>
</div>
<blockquote cite="mid:COL125-W243A3FCB880CA6B5A6E231C8360@phx.gbl">
<style><!--
.ExternalClass .ecxhmmessage P
{padding:0px;}
.ExternalClass body.ecxhmmessage
{font-size:10pt;font-family:Tahoma;}
--></style>
<div dir="ltr">
<font size="3" face="Times New Roman">
</font><br><p class="ecxMsoNormal"><span lang="EN-US"><font size="3"><font face="Calibri">Don’t get
me wrong… Kamailio is just a great product as it is.
Actually I think it does
much more than it would be necessary as a carrier grade
software. My idea is to
have more people involved discussing the “enterprise”
issues and possible
solutions for problems like the one I described. The
“impression” that I have
is that Kamailio’s community is much more devoted to the
“carrier” side of the
software than to the use of it on enterprises.</font></font></span></p>
<font size="3" face="Times New Roman">
</font><br><p class="ecxMsoNormal"><span lang="EN-US"><font size="3" face="Calibri"> </font></span></p>
<font size="3" face="Times New Roman">
</font><br><p class="ecxMsoNormal"><span lang="EN-US"><font size="3"><font face="Calibri">Moacir</font></font></span></p>
<font size="3" face="Times New Roman">
</font><br>
<br>
<div>> Date: Fri, 21 Dec 2012 10:41:25 +0200<br>
> To: <a class="ecxmoz-txt-link-abbreviated" href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a><br>
> From: <a class="ecxmoz-txt-link-abbreviated" href="mailto:jh@tutpro.com">jh@tutpro.com</a><br>
> Subject: Re: [SR-Users] RADIUS authentication<br>
> <br>
> Moacir Ferreira writes:<br>
> <br>
> > So my next question is: is it there on the Kamailio
community anyone<br>
> > willing to work on a “Kamailio Enterprise Edition”?<br>
> <br>
> what do you mean by such an edition? do you want to
integrate asterisk<br>
> like pbx capabilities to k or what? if so, my
understanding is that<br>
> most k folks want to keep them separate and just connect
ip pbxes to k<br>
> like any other sip uas.<br>
> <br>
> -- juha<br>
> <br>
> _______________________________________________<br>
> SIP Express Router (SER) and Kamailio (OpenSER) -
sr-users mailing list<br>
> <a class="ecxmoz-txt-link-abbreviated" href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a><br>
>
<a class="ecxmoz-txt-link-freetext" 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>
</div>
</div>
<br>
<fieldset class="ecxmimeAttachmentHeader"></fieldset>
<br>
<pre>_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
<a class="ecxmoz-txt-link-abbreviated" href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a>
<a class="ecxmoz-txt-link-freetext" 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>
</pre>
</blockquote>
<br>
<pre class="ecxmoz-signature">--
Daniel-Constantin Mierla - <a class="ecxmoz-txt-link-freetext" href="http://www.asipto.com/" target="_blank">http://www.asipto.com</a>
<a class="ecxmoz-txt-link-freetext" href="http://twitter.com/#%21/miconda" target="_blank">http://twitter.com/#!/miconda</a> - <a class="ecxmoz-txt-link-freetext" href="http://www.linkedin.com/in/miconda" target="_blank">http://www.linkedin.com/in/miconda</a></pre>
</div>
_______________________________________________<br>SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list<br><a href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a><br>http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users<br></blockquote></div><br><br>_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</div> </div></body>
</html>