<div dir="ltr">Hello Daniel,<div><br></div><div>I have re-installed kamailio from last 4.1 branch, but unfortunately, the problem persists.<br></div><div>Failed call with callID=2-17858@10.25153.150.</div><div>The log file i send to your private mail.</div><div><br></div><div>Best regards,</div><div>Julia</div><div><br></div><div> </div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Jan 25, 2015 at 12:03 AM, 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">
<div bgcolor="#FFFFFF" text="#000000">
Hello,<br>
<br>
got the time to analyze your last logs and I discovered that the
previous patch was not resetting properly the dialog shortcuts. I
pushed a fix, can you try again with the latest version from one of
the branches: master, 4.2 or 4.1?Let me know the results.<br>
<br>
Cheers,<br>
Daniel<div><div><br>
<br>
<div>On 15/01/15 23:42, Daniel-Constantin
Mierla wrote:<br>
</div>
<blockquote type="cite">
Hello,<br>
<br>
I looked at the logs, but I cannot see the log message I added
with the patch for reseting local dialog shortcuts after onreply
and failure route. It shuld be something like:<br>
<br>
"... resetting the local dialog shortcuts"<br>
<br>
Are you sure you are running the latest branch 4.1? You can send
the output of kamailio -v to double check here.<br>
<br>
I separated the logs per process and looked when a 301 was
received, apparently the ones for Call-ID: 4-21712 are matching
the same dialog. I found something not printing the same kind of
logs like for other 301 for Call-ID: 2-21712. If you can point the
line in the logs where you think it was the wrong dialog match, I
can investigate from there, but now I couldn't find any lead.<br>
<br>
Anyhow, if it is the latest branch 4.1 and the problem still
persists, can you add the following xlog at the beginning of main
request_route (or the route {...} ), plus in each reply_route,
onreply_route and failure_route:<br>
<br>
xlog("processing $rm ( $ci / %ft / $tt / $hdr(Via) ) [$fu =>
$tu]\n");<br>
<br>
Then redo the tests to catch the issue and send me the new logs.
Because you use sipp with tags like '4', it is hard to search on a
single tocken and I want to have the all message attribute when a
relevant route block is executed.<br>
<br>
Cheers,<br>
Daniel<br>
<br>
<div>On 14/01/15 15:07, Daniel-Constantin
Mierla wrote:<br>
</div>
<blockquote type="cite">
Hello Julia,<br>
<br>
ok, I will look over the logs very soon.<br>
<br>
As a short note for the future, make the archives zip or tgz,
being more common formats that can be unarchived everywhere
without installing additional app, being handy to open even on
small devices. Now it is ok with rar, being at the desk.<br>
<br>
Cheers,<br>
Daniel<br>
<br>
<div>On 14/01/15 14:43, Julia
Boudniatsky wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Hello Daniel,
<div><br>
<div>Please find in attached file the debug 3 log.</div>
<div>Failed call with Call-ID: <a href="mailto:4-21712@10.25.153.150" target="_blank">4-21712@10.25.153.150</a>.</div>
<div>The problem occurred with all modes of
"dlg_match_mode "<br>
</div>
<div>The same load test in 3.3 executed without failures.</div>
<div><br>
</div>
<div>Thank you,</div>
<div><br>
</div>
<div>Julia.</div>
</div>
</div>
</blockquote>
</blockquote>
<br>
<pre cols="72">--
Daniel-Constantin Mierla
<a href="http://twitter.com/#%21/miconda" target="_blank">http://twitter.com/#!/miconda</a> - <a href="http://www.linkedin.com/in/miconda" target="_blank">http://www.linkedin.com/in/miconda</a></pre>
</blockquote>
<br>
<pre cols="72">--
Daniel-Constantin Mierla
<a href="http://twitter.com/#!/miconda" target="_blank">http://twitter.com/#!/miconda</a> - <a href="http://www.linkedin.com/in/miconda" target="_blank">http://www.linkedin.com/in/miconda</a></pre>
</div></div></div>
</blockquote></div><br></div></div>