<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Rao,<br>
Thanks for keeping this discussion going. I agree that more
transparency is needed, and we are working on that.<br>
<br>
Let me help you out with some facts:<br>
- iptel.org is an open-source community open to anybody who wants to
contribute, on development, documentation, or community<br>
- iptel.org is not only focused on SER, but also on SERWeb, SEMS,
rtpproxy, as well as advancing SIP in general (the free SIP service,
SIP information, the product database...)<br>
- Many of the current developers of current SER are employed by what
was formerly known as iptelorg.com, now Tekelec, while many others
(including me) have no affiliation at all with iptelorg.com/Tekelec<br>
- Anyone participating in iptel.org work can get an iptel.org email
address (and anyone using the free SIP service will have an iptel.org
SIP account)<br>
- Commercial iptelorg.com/Tekelec is focused on large-scale SIP server
deployments for telecom companies, both IETF SIP and IMS<br>
- Open-source SER has a life and purpose on its own founded on a
handful of resourceful individuals who, though employed by
iptelorg.com/Tekelec, also spend personal time on the project due to
their interest in SIP (and would do so even if they changed jobs)<br>
- The features developed by SER developers at iptelorg.com/Tekelec are
partly influenced by what they do in their day job and partly what they
feel is important to SER as an open-source SIP server<br>
- Other developers/contributors are influenced by *their*
projects/dayjobs/visions for SER<br>
- Anybody can contribute ideas and try to get a "sponsor" (developer)
for that functionality on serdev (or contribute code themselves)<br>
- The iptel.org website, the SER - Getting Started document and much
other documentation is focused on the advancement of SIP, and we don't
really worry too much about whether people use ser or openser (in fact,
an effort to write an openser Getting Started document is in progress,
and we'll try to coordinate as much as possible on what is common)<br>
- SER is an open-source project that has much to improve when it comes
to documentation and transparency in processes, but we are making good
progress<br>
- SER open-source project is about quality, reliability and large-scale
setups with longer turn-around time on new releases and longer support
for older versions than what is normal for open-source projects.
However, we have discussed introducing a new development track making
new features more easily accessible for those who want "bleeding edge"<br>
- Documentation improvements for SER will be in areas important for SIP
professionals, including release predictability, migration
documentation, scripting, quality improvements in best practices for
ser.cfg etc<br>
- SER's development will not be better than the people contributing and
everybody can make an effort<br>
<br>
I don't want to say anything bad about OpenSER. Most "old-timers" on
serusers know that I didn't like the fork, I think it would have been
possible to do things within (a better governed) shared open-source
project, but the community was never allowed to say its meaning and
personal differences probably made it impossible.<br>
OpenSER have done good things and some good people contribute code to
the project. <br>
<br>
As for VON, I'm not sure if Tekelec was there, probably not, but the
absence of a booth for iptel.org is more due to the fact that iptel.org
is a loose collection of individuals with sponsorship from FOKUS
Fraunhofer and iptelorg.com/Tekelec and not an entity that has
resources (or inclinations) to do commercial efforts.<br>
<br>
g-)<br>
<br>
Rao Ramaratnamma wrote:
<blockquote
cite="mid20061109201647.74488.qmail@web57812.mail.re3.yahoo.com"
type="cite">
<style type="text/css"><!-- DIV {margin:0px;} --></style>
<div
style="font-family: times new roman,new york,times,serif; font-size: 12pt;">
<div
style="font-family: times new roman,new york,times,serif; font-size: 12pt;">Hi
Weiter,<br>
<br>
Yeah, I have been trying to limit myself to technical observations too,
but the governance aspect is somewhat interesting too as a hint for
future development, even though I guess even this is much more
confusing than the technical ones. I have investigated, both projects
have their firms with them that pursue their commercial interests which
creates a risk of possibly departing from the public interest, like
with redhat. From this angle they look quite similar. But if any
worries me just a little bit more than openser. Appearance at
commercial shows on the "open" side versus technical event on the "net"
side if I take your BSD parallel, marketing "open" webpage accusing
"net" version bad, hiding root commerical sponsors on the "open"
webpage, this could be signs for a redhat-like doubleedged sword.
Hopefully I am oversensing because I mean it is natural that everybody
has SOME interest, but indisputably folks on both sides have done good
work, but same indisputably more TRANSPARENCY would be helpful for both
projects so that users can be less investigative.<br>
<br>
But I agree the technical comparison you suggest will be very useful if
not most useful. This is what I am eventually upto. Anything folks have
to tell in this topic is most welcome like the retransmission timers in
subject or user loading.<br>
<br>
rr<br>
<br>
disconcerted by the fact that the more I know the more I am confused
and determined to get over the learning curve quickly. also excuse the
abuse I crossposted again but I think cross interrogation is a bit
painful but the more effective :-)<br>
<br>
<div
style="font-family: times new roman,new york,times,serif; font-size: 12pt;">-----
Original Message ----<br>
From: Weiter Leiter <a class="moz-txt-link-rfc2396E" href="mailto:bp4mls@googlemail.com"><bp4mls@googlemail.com></a><br>
To: Kim Il <a class="moz-txt-link-rfc2396E" href="mailto:kim_il_s@yahoo.com"><kim_il_s@yahoo.com></a><br>
Cc: <a class="moz-txt-link-abbreviated" href="mailto:users@openser.org">users@openser.org</a><br>
Sent: Thursday, November 9, 2006 1:42:29 PM<br>
Subject: Re: Fw: [Users] TM : retransmission timers<br>
<br>
Common user barely has time to meet his boss requirements, rather than
playing around with different scenarios, platforms, environments. <br>
<br>
I only read one email where Daniel stated that OpenSER now performs a
whole much better while loading users from database. SER guys put no
figure out yet, neither bare numbers nor comparisons. I'm just really
curious to see how both servers perform, that's all.
<br>
<br>
Even though I must maintain my SER, I kinda like OpenSER's faster
releases and developers' responsiveness (that I shamelessly exploit for
the common code left there :-), which is pretty much nonexistent with
iptel (at least this is the general belief here at OpenSER). But about
this I'll probably have to fight on SER's mailing list. I still wish
that one day I won't have to compare features; heck, NetSER and FreeSER
are still available ;-).
<br>
<br>
WL.<br>
<br>
PS. Maybe regretfully, I haven't seen any iptel booth at von this year,
while OpenSER guys put up a nice show. My congrats.<br>
<br>
<div><span class="gmail_quote">On 11/9/06, <b
class="gmail_sendername">Kim Il</b> <<a rel="nofollow"
target="_blank" href="mailto:kim_il_s@yahoo.com">kim_il_s@yahoo.com</a>>
wrote:
</span>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I
can see what you are hinting at, but I guess that the users are the
unbiased party that should do the judgment and not the parties who have
something to gain.<br>
<br>
cheers
<div><span><br>
<br>
<b><i>Weiter Leiter <<a rel="nofollow" target="_blank"
href="mailto:bp4mls@googlemail.com">bp4mls@googlemail.com</a>></i></b>
wrote:
<blockquote
style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;">
This features comparisons are not to last for too long, some
performance comparisons would also be nice. After all, there are plenty
of UA-level stacks out there. At least now that both projects get to
have stable releases after forking and some core functionality remained
shared. <br>
<br>
I wonder what "unbiased" organization will take up the challenge. :-)<br>
<br>
<div><span class="gmail_quote">On 11/8/06, <b
class="gmail_sendername">Kim Il</b> <<a rel="nofollow"
target="_blank" href="mailto:kim_il_s@yahoo.com">
kim_il_s@yahoo.com </a>> wrote:</span>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Mike,<br>
<br>
this is a really good start and we should collect these things so as
to help the community to take the right choice. I would also suggest
that what ever ground breaking issues we list we stay at the functional
level (I do not think anyone is helped by using a description
containing "allowing carrier grade platforms" and similar marketing
phrases). <br>
<br>
cheers</blockquote>
<div><br>
{truncated because too large}<br>
</div>
<br>
</div>
<br>
</blockquote>
<br>
</span></div>
<p> </p>
<hr size="1">Sponsored Link <br>
<br>
Talk more and pay less. Vonage can save you up to $300 a year on your
phone bill. <a rel="nofollow" target="_blank"
href="http://clk.atdmt.com/VON/go/yhxxxvon1080000017von/direct/01/">
Sign up now.</a>
</blockquote>
</div>
<br>
<div>_______________________________________________<br>
Users mailing list<br>
<a class="moz-txt-link-abbreviated" href="mailto:Users@openser.org">Users@openser.org</a><br>
<a target="_blank"
href="http://openser.org/cgi-bin/mailman/listinfo/users">http://openser.org/cgi-bin/mailman/listinfo/users</a><br>
</div>
</div>
<br>
</div>
</div>
<br>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
Serusers mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Serusers@lists.iptel.org">Serusers@lists.iptel.org</a>
<a class="moz-txt-link-freetext" href="http://lists.iptel.org/mailman/listinfo/serusers">http://lists.iptel.org/mailman/listinfo/serusers</a>
</pre>
</blockquote>
</body>
</html>