<!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">
Disclaimer: I am affiliated with SER, iptel.org and allthough
attempting to give an objective account from a user perspective, I will
probably be accused of being biased in many of the things I state.<br>
-------------<br>
You may want to read the SER - Getting Started document<br>
<a class="moz-txt-link-freetext" href="http://www.iptel.org/ser/doc/gettingstarted">http://www.iptel.org/ser/doc/gettingstarted</a><br>
and especially:<br>
<a class="moz-txt-link-freetext" href="http://siprouter.onsip.org/doc/gettingstarted/ch03.html">http://siprouter.onsip.org/doc/gettingstarted/ch03.html</a><br>
<br>
Since that was written, OpenSER has released 1.0 and 1.1, while SER is
now about to release its first major release since the fork.<br>
<br>
I haven't followed OpenSER closely, so I cannot speak for it, but SER's
upcoming release addresses many of the major shortcomings found in
SER/OpenSER's shared roots, i.e. SER 0.9.x. These changes include a
major rewrite of timers, as well as big improvement in the database
model.<br>
<br>
AFAIK, the module interfaces are still fairly similar, but a major
difference in how variables and message data is manipulated (thus
causing modules to be different): openser has further developed the
pseudo-variables introduced with avpops module, while SER has
introduced selects. Which one you prefer is a matter of taste, but
IMHO ser.cfg for upcoming SER is greatly easier to read, as well as
maintain compared to the pseudo-variable approach, and it is my firm
opinion that new users will find SER more intuitive to use when they
start getting their teeth into SIP server configuration and maintenance.<br>
<br>
As for documentation, the SER pre-release does not have complete
documentation, and yes, the documentation effort is lagging behind a
bit. I'm in charge of that effort, and the goal is to have a
satisfactory set of documentation for the upcoming release. The last
few months of improvements at iptel.org are evidence of that process.
OpenSER has focused on documentation and seems to have a fairly good
documentation.<br>
<br>
Finally, to your wish of combining ser and openser: ser and openser
have some shared modules, but only where the developers have commited
to maintaining in both environments. The cores are by now also quite
far apart. So, as each project has its own priorities, expect some
features to developed in both (by different developers and different
code), while other features to be only found in one.<br>
<br>
In the end, it boils down to which piece of software you feel satisfies
your needs, whether you have confidence in the project moving in the
direction you need, and whether the project will deliver the software
in a satisfactory, bug-free condition at the intervals you need.<br>
g-)<br>
<br>
Rao Ramaratnamma wrote:
<blockquote
cite="mid20061107221827.37285.qmail@web57808.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;">sorry
for reposting -- I think this question belongs to both mailing list.<br>
I am really stuck with this.<br>
<br>
rr<br>
<br>
<div
style="font-family: times new roman,new york,times,serif; font-size: 12pt;">-----
Forwarded Message ----<br>
From: Rao Ramaratnamma <a class="moz-txt-link-rfc2396E" href="mailto:raramarat@yahoo.com"><raramarat@yahoo.com></a><br>
To: Christian Schlatter <a class="moz-txt-link-rfc2396E" href="mailto:cs@unc.edu"><cs@unc.edu></a>; <a class="moz-txt-link-abbreviated" href="mailto:users@openser.org">users@openser.org</a><br>
Sent: Tuesday, November 7, 2006 11:15:27 PM<br>
Subject: Re: [Users] TM : retransmission timers<br>
<br>
<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;">the
ser ottendorf announcement does mention improved timers. Cannot openser
include this feature too and cannot I merge ser with openser for good
timers? I am still trying to understand the difference between ser and
openser but standart compliance seems to be very important matter!<br>
<br>
Cannot people provide me with some hints? I am sure that I am not the
only who is asking the difference between ser and openser. ser
documentation does not appear uptodate, but the software as sannounced
appears impressive. I have already asked this question but did not
receive any answer. <br>
<br>
thank you in advance!<br>
<br>
rr<br>
<br>
<div
style="font-family: times new roman,new york,times,serif; font-size: 12pt;">-----
Original Message ----<br>
From: Christian Schlatter <a class="moz-txt-link-rfc2396E" href="mailto:cs@unc.edu"><cs@unc.edu></a><br>
To: <a class="moz-txt-link-abbreviated" href="mailto:users@openser.org">users@openser.org</a><br>
Sent: Tuesday, November 7, 2006 10:52:56 PM<br>
Subject: Re: [Users] TM : retransmission timers<br>
<br>
<div>Greg Fausak wrote:<br>
> Hello,<br>
> <br>
> I believe this is a well known bug.<br>
> Granularity of timers is 1 second. So, if you sign up for a timer
to<br>
> be fired in 1 second it will happen anywhere between 0 seconds and
1 <br>
> second.<br>
> 2 seconds will happen between 1 and 2 seconds. I usually set up my<br>
> timers to be 2, 2, 4, 8. There are VOIP providers that are pretty
<br>
> sticky about<br>
> the first 500ms. If you are using one of them you're out of luck.<br>
<br>
Yes, there is a timer process that wakes up every second to perform <br>
retransmissions. I was actually quite surprised that OpenSER, which is <br>
known to be very standards compliant, does not follow the RFC 3261 <br>
retransmission timeouts. On the other hand, the RFC 3261 timeout values
<br>
are just suggestions and standards compliant SIP UA must accept shorter
<br>
timeouts. Still it would be nice if OpenSER would support sub second <br>
timers, this would allow for shorter fail-over times.<br>
<br>
Christian<br>
<br>
> <br>
> I believe SER has made timer changes to support more exact timer<br>
> intervals. They are a completely different camp, with a different
feature<br>
> set (although they share the same roots).<br>
> <br>
> -g<br>
> <br>
> <br>
> On 11/7/06, Jean-François SMIGIELSKI <a class="moz-txt-link-rfc2396E" href="mailto:jf-smig@ibelgique.com"><jf-smig@ibelgique.com></a>
wrote:<br>
>> Hello,<br>
>><br>
>> I made strange observations about the intervals between <br>
>> retransmissions with the TM module.<br>
>> In my experiments, I used the default parameters for the TM
module <br>
>> timers, and I sent an INVITE that cannot receive answers (it
has a <br>
>> well known R-URI pattern that is forwarded to a place and
port that <br>
>> nobody listen).<br>
>><br>
>> When reading RFC3261, I expected to see intervals between <br>
>> retransmissions of |500ms|1s|2s|4s|8s|16s|. 7 transmissions,
during 32s.<br>
>><br>
>> But with OpenSER, (I have tested with the debian package
1.1.0-5 on a <br>
>> debian etch, and the cvs sources for 1.1.0 or 1.0.1compiled by
<br>
>> myself), I can see intervals like <500ms, 2s, 4s, 4s,4s,
... until 26s <br>
>> are spent (9 sendings). The first interval is sometomes very
short <br>
>> (40ms).<br>
>><br>
>> Altough I like the sequence of 4s separated transmissions, I
do not <br>
>> know why the first interval is so short, and why there is no
sending <br>
>> after 1s.<br>
>><br>
>> Did anybody observed such behaviours? Are they normal?<br>
>><br>
>> Thanks in advance!<br>
>><br>
>> JF Smigielski.<br>
>><br>
>><br>
>>
________________________________________________________________________<br>
>> iBELGIQUE, exprimez-vous !<br>
>> <a rel="nofollow" target="_blank"
href="http://web.ibelgique.com/">http://web.ibelgique.com/</a><br>
>><br>
>> _______________________________________________<br>
>> Users mailing list<br>
>> <a class="moz-txt-link-abbreviated" href="mailto:Users@openser.org">Users@openser.org</a><br>
>> <a rel="nofollow" target="_blank"
href="http://openser.org/cgi-bin/mailman/listinfo/users">http://openser.org/cgi-bin/mailman/listinfo/users</a><br>
>><br>
>><br>
>><br>
> <br>
> <br>
<br>
</div>
<div>_______________________________________________<br>
Users mailing list<br>
<a class="moz-txt-link-abbreviated" href="mailto:Users@openser.org">Users@openser.org</a><br>
<a rel="nofollow" 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>
</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>