<html><head>
<meta content="text/html; charset=iso-8859-1" http-equiv="Content-Type">
<meta name="GENERATOR" content="MSHTML 8.00.6001.18904">
<style></style>
</head>
<body bgcolor="#ffffff"><div><font size="2" color="navy" face="Arial">
That's completely ridiculous.<br>
<br>
<br>--
<br>Kristian Kielhofner
<br><a href="http://blog.krisk.org">http://blog.krisk.org</a></font></div>
<br><div><hr size="2" width="100%" align="center" tabindex="-1">
<font face="Tahoma" size="2">
<b>From</b>: <a href="mailto:freeswitch-users-bounces@lists.freeswitch.org">freeswitch-users-bounces@lists.freeswitch.org</a> <<a href="mailto:freeswitch-users-bounces@lists.freeswitch.org">freeswitch-users-bounces@lists.freeswitch.org</a>>
<br>
<b>To</b>: <a href="mailto:freeswitch-users@lists.freeswitch.org">freeswitch-users@lists.freeswitch.org</a> <<a href="mailto:freeswitch-users@lists.freeswitch.org">freeswitch-users@lists.freeswitch.org</a>>
<br><b>Sent</b>: Thu Jun 10 12:30:42 2010<br>
<b>Subject</b>: Re: [Freeswitch-users] uuid_media hangs
<br></font><br></div>
<div>> are very keen to actually follow all these silly RFC</div>
<div>I agree, usually RFC are created first by university so by
students...</div>
<div> </div>
<blockquote style="BORDER-LEFT: #000000 2px solid; PADDING-LEFT: 5px; PADDING-RIGHT: 0px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px">
<div style="FONT: 10pt arial">----- Original Message ----- </div>
<div style="FONT: 10pt arial; BACKGROUND: #e4e4e4; font-color: black"><b>From:</b>
<a title="anthony.minessale@gmail.com" href="mailto:anthony.minessale@gmail.com">Anthony Minessale</a> </div>
<div style="FONT: 10pt arial"><b>To:</b> <a title="freeswitch-users@lists.freeswitch.org" href="mailto:freeswitch-users@lists.freeswitch.org">freeswitch-users@lists.freeswitch.org</a>
</div>
<div style="FONT: 10pt arial"><b>Sent:</b> Thursday, June 10, 2010 12:09
PM</div>
<div style="FONT: 10pt arial"><b>Subject:</b> Re: [Freeswitch-users]
uuid_media hangs</div>
<div><br></div>The funny part is you are willing to go to all this effort to
try to make us correct it because you know the other people wont.
<div>This type of finger pointing to RFC is typical to providers so now I have
to do free work to investigate it for you.</div>
<div>And I bet you are paying them money and not us, oh well,
typical.....Don't worry I won't hold it against you.</div>
<div><br></div>
<div>The philosophical question here is weather or not to send a requires
timer in the reinvite, so ok.</div>
<div>I can try to look it up for you but from a logical point of view, once
you establish in the original invite that you are going to use session timers,
every reinvite constitutes a timer refresh, so once you have agreed in the
original invite to use timers it would stand to reason to require the timer
option in every new re-invite since it represents a timer refresh.</div>
<div><br></div>
<div>But, let's face it... Who cares right? its a meaningless param in
an REINVITE. Most sip implementation wing it on most of these packet
parsers. The sofia developers are very keen to actually follow all these
silly RFC you are trying to quote and they have been relaxing it nonstop ever
since because nobody really follows any rules in SIP they just use them to
avoid having to patch their code. Especially in a deployed appliance in
a telco. They are really telling you they can't support it because the
code in their sip gateway fails when it sees this and they are too lazy to
change it so they pray that some RFC will let them off the hook. Trust
me, we've had worse. One place refused our calls because they did not
like the syntax of our user agent string......</div>
<div><br></div>
<div>So bottom line is I would trust the default behavior of
sofia-sip over most things any day but if they are really doing something
wrong the problem would be in the sofia-sip library not in FreeSWITCH so I am
not sure where to tell you to look in the code to correct it because we use
that code asis and avoid hacking into it a all costs. Try using grep
into the sofia-sip lib for the strings you know are meaningful.</div>
<div><br></div>
<div>P.S</div>
<div>All the event related things are fixed now, there was a small speed bump
along the way this week.</div>
<div><br></div>
<div><br></div>
<div><br></div>
<div><br>
<div class="gmail_quote">On Thu, Jun 10, 2010 at 4:34 AM, peely <span dir="ltr"><<a href="mailto:freeswitch@peely.com">freeswitch@peely.com</a>></span>
wrote:<br>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote"><br>Hi,<br><br>It's not a hijacked thread, I created this
with an issue around uuid_media,<br>initially it was hanging, then in the
latest git it receives a 4xx from the<br>far end due to the Requires: timer
support bot being supported in the<br>reinvite transaction. I did
anecdotally mention problems with events, which<br>I subsequently pulled off
to another thread.<br><br>I was looking at RFC 4028, in the examples it
shows the refresh event not<br>providing the Required: timer header even for
the refresh of the original<br>invite transaction, just the Supported:
timer. There's nothing in RFC 3725<br>regarding sesison timers in 3PCC but
as the reinvite for the media<br>adjustment is a new transaction, I don't
think it needs the Requires: timer<br>option to persist the timer support on
the original dialogue. This is<br>certainly the behaviour of the previous
equipment I had on this interconnect<br>and it operates using session timers
and 3PCC in several other environments<br>too.<br><br>I'm not brilliant with
C, but if you could please point me to the right<br>approach to removing the
Requires: timer field in the header I'd be happy to<br>test it and let you
know if it causes any problems with rienvites across<br>various carriers and
other platforms.<br><br><br><br>Cheers,<br><br><br>Neil.<br><font color="#888888">--<br>View this message in context: <a href="http://freeswitch-users.2379917.n2.nabble.com/uuid-media-hangs-tp5145657p5162317.html" target="_blank">http://freeswitch-users.2379917.n2.nabble.com/uuid-media-hangs-tp5145657p5162317.html</a><br>
</font>
<div class="im">Sent from the freeswitch-users mailing list archive at
Nabble.com.<br><br>_______________________________________________<br></div>
<div>
<div></div>
<div class="h5">FreeSWITCH-users mailing list<br><a href="mailto:FreeSWITCH-users@lists.freeswitch.org">FreeSWITCH-users@lists.freeswitch.org</a><br><a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br><a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Anthony Minessale II<br><br>FreeSWITCH <a href="http://www.freeswitch.org/">http://www.freeswitch.org/</a><br>ClueCon <a href="http://www.cluecon.com/">http://www.cluecon.com/</a><br>
Twitter: <a href="http://twitter.com/FreeSWITCH_wire">http://twitter.com/FreeSWITCH_wire</a><br><br>AIM:
anthm<br><a href="mailto:MSN%3Aanthony_minessale@hotmail.com">MSN:anthony_minessale@hotmail.com</a><br>GTALK/JABBER/<a href="mailto:PAYPAL%3Aanthony.minessale@gmail.com">PAYPAL:anthony.minessale@gmail.com</a><br>IRC:
<a href="http://irc.freenode.net">irc.freenode.net</a>
#freeswitch<br><br>FreeSWITCH Developer Conference<br><a href="mailto:sip%3A888@conference.freeswitch.org">sip:888@conference.freeswitch.org</a><br><a href="mailto:googletalk%3Aconf%2B888@conference.freeswitch.org">googletalk:conf+888@conference.freeswitch.org</a><br>
pstn:+19193869900<br></div>
<p>
<hr>
<p></p>_______________________________________________<br>FreeSWITCH-users
mailing
list<br><a href="mailto:FreeSWITCH-users@lists.freeswitch.org">FreeSWITCH-users@lists.freeswitch.org</a><br><a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br><a href="http://www.freeswitch.org">http://www.freeswitch.org</a><br></p>
</blockquote></body></html>