<br><br><div class="gmail_quote">On 12 August 2010 10:21, Daniel-Constantin Mierla <span dir="ltr"><<a href="mailto:miconda@gmail.com" target="_blank">miconda@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Timo,<div><div></div><div><br>
<br>
On 8/11/10 11:58 PM, Timo Reimann wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hey Brian,<br>
<br>
<br>
On 11.08.2010 13:01, dotnetdub wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I see this in every call setup..<br>
<br>
CRITICAL: dialog [dlg_hash.c:591]: bogus event 6 in state 2 for<br>
dlg 0xaf933bd0 [3739:1530909163] with clid<br>
'<a href="mailto:5959362a340dfa7938cf52ae1ba4b9d7@my.proxy.com" target="_blank">5959362a340dfa7938cf52ae1ba4b9d7@my.proxy.com</a><br>
<mailto:<a href="mailto:5959362a340dfa7938cf52ae1ba4b9d7@my.proxy.com" target="_blank">5959362a340dfa7938cf52ae1ba4b9d7@my.proxy.com</a>>' and tags<br>
'as5b636a8a' ''<br>
<br>
I am running SIP-Router 3.01<br>
<br>
I note this<br>
thread: <a href="http://www.mail-archive.com/sr-dev@lists.sip-router.org/msg05668.html" target="_blank">http://www.mail-archive.com/sr-dev@lists.sip-router.org/msg05668.html</a><br>
<br>
but it's inconclusive.<br>
</blockquote>
The conclusion took place in a different thread: Daniel committed a<br>
patch to master on 2 July<br>
<br>
<a href="http://lists.sip-router.org/pipermail/sr-dev/2010-July/008097.html" target="_blank">http://lists.sip-router.org/pipermail/sr-dev/2010-July/008097.html</a><br>
<br>
and asked people to test the patch on 5 July prior to backporting it<br>
into 3.0:<br>
<br>
<a href="http://lists.sip-router.org/pipermail/sr-dev/2010-July/008109.html" target="_blank">http://lists.sip-router.org/pipermail/sr-dev/2010-July/008109.html</a><br>
<br>
Klaus Feichtinger took the time for validation, and things seem to be<br>
looking good. However, AFAICS the patch wasn't brought into 3.0 which<br>
means that you still run on a race-conditioned version of SIP-Router<br>
that causes the log message to appear quite frequently yet.<br>
<br>
Daniel, considering Klaus' successful test runs would it be acceptable<br>
to get the patch (commit f1c35c1325) into 3.0 from your point of view?<br>
</blockquote>
<br></div></div>
it is backported, I did many cherry-picks resulting in a single email with bulk commits to kamailio_3.0 content:<br>
<a href="http://lists.sip-router.org/pipermail/sr-dev/2010-July/008213.html" target="_blank">http://lists.sip-router.org/pipermail/sr-dev/2010-July/008213.html</a><br>
<br>
Cheers,<br>
Daniel<div><div></div><div><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
It doesn't seem to cause any issue but I would like to get it sorted.<br>
</blockquote>
It definitely doesn't cause any critical issues to the proper working of<br>
SIP-Router. The worst it can do is mess up a call's dialog state when<br>
the race condition kicks in. Once the race condition is ruled out,<br>
occurrences of the message boil down to broken UAs as Henning pointed<br>
out already.<br>
<br>
<br>
HTH,<br>
<br>
--Timo<br>
</blockquote>
<br></div></div><font color="#888888">
-- <br>
Daniel-Constantin Mierla<br>
<a href="http://www.asipto.com/" target="_blank">http://www.asipto.com/</a><br>
<br></font></blockquote><div><br></div><div>Thanks Gents.</div><div><br></div><div>I will wait until 3.1 drops and update these two boxes to get the fix.</div><div><br></div><div>Brian</div><div><br></div><div> </div></div>
<br>