<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'>
Opening the previous message I saw it was messy... Here it goes again:<BR> <BR>Well… Sorry for this long post.<BR><br>I work 100% dedicated to SMB - Small Medium Business. In this market there is an enormous<br>growth of multiples devices in all companies. Most of the SMB I work with are looking for:<BR> <BR>- Let their employees bring their own device (BYOD);<BR> <BR>- Enable chat, voice and video, with presence information in all devices;<BR> <BR>- Not have to pay for premium solutions like sophisticated SBCs to enable<br> the workforce to work either internally (in the company) or externally (from the Internet);<BR> <BR>- Have a single number for voice and video in all devices;<BR> <BR>- Reduced complexity, setup time and maintenance;<BR><br>With all the above in mind, I believe Kamailio is just wonderful, why:<BR><br>- It is inexpensive!!!<BR> <BR>- No limit or licenses for users. In this way any employee can have their PC,<br> their iPad or Android tablet, their iPhone or Android phone, their table phone, etc.<BR> <BR>- Using the right device or software client (some of them freeware) they can, once again, reduce cost.<BR> <BR>- Very key: Unlike several alternatives on the market, Kamailio does not interfere<br> with the RTP in between SIP clients, it does raw media switching using RTPProxy.<br> So, more complex SIP usage like in video will not be affected by the SIP solution.<BR> <BR>I know that you can always find the information to deploy such solution with the specs above.<br>However, the information is a kind of “scattered” and, unlike the alternatives that would not<br>address all the exposed issues, it takes quite long to get the server configured to do what<br>we want. And yes, maybe because I am just a newbie to Kamailio, sorry for that.<BR>With the above in mind I would like to see, and of course contribute for, a “how to” to deploy<br>a Kamailio server with the following specs:<BR> <BR>- If you thing about companies with up to 10k employees, each employee with up to 4 SIP terminals<br> (i.e.: table phone, cellular phone, PC and tablet), then you would need a solution scalable for 40k devices.<BR> <BR>- All devices from a user should ring when receiving a call.<BR> <BR>- Calling outside (PSTN) should be impersonated so the user would have a single number seem outside<br> of the company.<BR> <BR>- The solution should have an internal interface (LAN) and an external Interface (WAN/Internet),<br> promoting RTP relay for NATed devices.<BR> <BR>- The solution should not interfere with RTP, meaning no transcoding. If an end point fulfills<br> the other part RTP offer, they would connect. If not, it would be just rejected.<BR> <BR>- The solution should be able to record calls.<BR> <BR>- The solution should be able to use SIP trunk as the way out to PSTN.<BR> <BR>- The solution should be able to integrate, via RADIUS or LDAP, with the customer existing directory,<br> most of the cases Microsoft.<BR> <BR>Now, when look at these specs, Kamilio does all of this! However, it may take one year before someone<br>“Kamailio dummy” like myself to get all the knowledge to do it. Of course I know I must invest on more<br>knowledge but the more companies easily install and start using Kamailio on the enterprise, the better<br>is my value if I get to know it in depth. So that is why I would like to see a “working group” within<br>the existing Kamailio community, with more focus on easing up the deployment of it on the enterprise.<br>I believe more people had the same problem I am having: it is a lot to study specially if you are not<br>a programmer; because of it not a lot of SMB companies are using it, making investing on learning it,<br>in my case, low return.<BR> <BR>Cheers!<BR> <BR>Moacir<br><BR> </div></body>
</html>