well put dan! I really don't understand why you would bother bringing this to our attention at all Henning. <br><br><div class="gmail_quote">On Fri, Nov 14, 2008 at 11:12 PM, Dan Pascu <span dir="ltr"><<a href="mailto:dan@ag-projects.com">dan@ag-projects.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
I fail to see what worries you if all is fine and dandy in paradise. Don't<br>
mind us, we are just a bunch of loonies with weird ideas anyway.<br>
<div><div></div><div class="Wj3C7c"><br>
On Friday 14 November 2008, Henning Westerholt wrote:<br>
> Hello all,<br>
><br>
> recently some statement came to my attention that "there is a common<br>
> consent that the current design/architecture of [..] OpenSER (inherited<br>
> from SER) is no longer able to deliver and to meet the present<br>
> requirements and demands".<br>
><br>
> I don't want to argue that much about this opinion, in fact the demands<br>
> to a Voice over IP solution depends very much on the certain setup. But<br>
> i want to share some details from my experiences in developing and<br>
> operating a big VoIP infrastructure here at 1&1.<br>
><br>
> We've about 2 million customers on our platform, that uses over 5<br>
> million individual numbers and terminate about 1 billion minutes per<br>
> month. We're able to provide a good service with the actual<br>
> architecture of OpenSER without any real problems. Of course there is<br>
> always some room for improvements, but so far the main challenges we<br>
> faced were not in the scalability or performance areas. More important<br>
> issues are e.g. the inherent complexity of the SIP protocol and the<br>
> maintainance of a good quality assurance and integration process.<br>
><br>
> We started some years ago with OpenSER 0.9.5, which we then extended a<br>
> lot in house. For example we implemented more than 25 own modules, a<br>
> own path implementation, did a lot of bug fixing and workarounds for<br>
> certain problems we've found. We're able to reduce this amount of<br>
> proprietary code a lot in the past, because of progress in the OpenSER<br>
> development, intregration of our "key" modules and a lot of other<br>
> contributions. We're using now something between OpenSER 1.3 and<br>
> Kamailio 1.4 with only a few private extensions.<br>
><br>
> So in my opinion the actual design of our server is not "[..] an<br>
> inevitable dead-end that needs to be avoided.". I rather think that<br>
> we'll be able with continuing improvements to tackle the upcoming<br>
> challenges well, especially as we will work together in the future with<br>
> the SER developers in improving important areas of this software.<br>
><br>
> But this is just my personal opinion, everybody is of course free to<br>
> have their own position.<br>
><br>
> With best regards,<br>
><br>
> Henning Westerholt<br>
<br>
<br>
<br>
--<br>
</div></div><font color="#888888">Dan<br>
</font><div><div></div><div class="Wj3C7c"><br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
</div></div></blockquote></div><br>