Hi Klaus,<div><br></div><div><meta http-equiv="content-type" content="text/html; charset=utf-8"><span class="Apple-style-span" style="border-collapse: collapse; font-family: arial, sans-serif; font-size: 13px; ">I work for a company called Smile Communications based in Johannesburg, South Africa (although legally registered in Mauritius) and we are a startup mobile comms company focussing on providing low cost voice and messaging services to underserved (bottom of the pyramid) customers across Africa. We have spectrum and operator licenses in Uganda, Tanzania, Nigeria & DRC thus far and are trying to acquire more as we go along. We launched in Uganda 18 months ago by rolling out our own Wimax network and fixed-wireless wimax/voip phones. We are now looking at rolling out in our other licensed countries. We built an entire voice/messaging stack integrating over 40 different open source projects using an SOA methodology.</span></div>
<div><span class="Apple-style-span" style="border-collapse: collapse; font-family: arial, sans-serif; font-size: 13px; "><br>We have now decided that with the slow uptake of Wimax voice handsets (in fact, no uptake :( ) we will now roll out LTE in our spectrum instead. This necessitates us to move our architecture from something slightly proprietary (although it is all based on SIP) to obey the IMS/VoLTE specifications. </span></div>
<div><span class="Apple-style-span" style="border-collapse: collapse; font-family: arial, sans-serif; font-size: 13px; "><br>Following our previous approach, we want to build the end to end IMS/OSS/BSS architecture in as cost effective manner as possible. We live by the motto that our customers make a decision to either eat lunch or make a phone call with the money they have at any given time - we want to make our calls as affordable as possible and hence keep our Capex and Opex costs as low as possible. We also want to have great flexibility and be able to make changes quickly without needing to call on product vendors.</span></div>
<div><span class="Apple-style-span" style="border-collapse: collapse; font-family: arial, sans-serif; font-size: 13px; "><br></span></div><div><span class="Apple-style-span" style="border-collapse: collapse; font-family: arial, sans-serif; font-size: 13px; ">At the same time our motto is provide back to the community - hence us publishing all the stuff we are going to do SR ;)</span></div>
<div><span class="Apple-style-span" style="border-collapse: collapse; font-family: arial, sans-serif; font-size: 13px; "><br></span></div><div><span class="Apple-style-span" style="border-collapse: collapse; font-family: arial, sans-serif; font-size: 13px; ">Cheers</span></div>
<div><span class="Apple-style-span" style="border-collapse: collapse; font-family: arial, sans-serif; font-size: 13px; ">Jason<br><br></span></div><div><div class="gmail_quote">On Thu, Apr 21, 2011 at 4:41 PM, Klaus Darilion <span dir="ltr"><<a href="mailto:klaus.mailinglists@pernau.at">klaus.mailinglists@pernau.at</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hi!<br>
<br>
Carsten, Jason, I wonder what is the main motivation for you to have IMS<br>
components?<br>
<br>
Are you using Kamailio in an mobile operator environment and thus have<br>
to support all the IMS interfaces, or do you plan to use those modules<br>
also in "normal" VoIP provider scenarios (benefits?)<br>
<br>
Thanks<br>
Klaus<br>
<br>
_______________________________________________<br>
sr-dev mailing list<br>
<a href="mailto:sr-dev@lists.sip-router.org">sr-dev@lists.sip-router.org</a><br>
<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev</a><br>
</blockquote></div><br></div>