<html><head></head><body><div class="ydpe1613d57yahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;"><div></div>
<div>Hi Bogdan,</div><div><br></div><div>I'll try to get this info and examine. <br></div><div>Thanks for the follow up :)<br></div>
</div><div id="yahoo_quoted_2867357561" class="yahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
On Monday, 11 March 2019, 1:43:13 PM GMT+5:30, Bogdan-Andrei Iancu <bogdan@opensips.org> wrote:
</div>
<div><br></div>
<div><br></div>
<div><div id="yiv7515405395"><div>
<tt>Hi Pasan,<br clear="none">
<br clear="none">
I doubt that fix_route_dialog() is doing something wrong :D. Maybe
there is something wrong with the signaling / cfg. After the call
is established, do a "opensipsctl fifo dlg_list <callid>" to
see the dialog details as learned by OpenSIPS.<br clear="none">
<br clear="none">
Also post the incoming BYE, to see how does it "fit" to the dialog
and what should be the effect of the "fixing".<br clear="none">
<br clear="none">
Regards,<br clear="none">
</tt>
<pre class="yiv7515405395moz-signature">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a rel="nofollow" shape="rect" class="yiv7515405395moz-txt-link-freetext" target="_blank" href="https://www.opensips-solutions.com">https://www.opensips-solutions.com</a>
OpenSIPS Summit 2019
<a rel="nofollow" shape="rect" class="yiv7515405395moz-txt-link-freetext" target="_blank" href="https://www.opensips.org/events/Summit-2019Amsterdam/">https://www.opensips.org/events/Summit-2019Amsterdam/</a>
</pre>
<div class="yiv7515405395yqt1999212786" id="yiv7515405395yqt33411"><div class="yiv7515405395moz-cite-prefix">On 03/08/2019 11:28 AM, Pasan Meemaduma
wrote:<br clear="none">
</div>
<blockquote type="cite">
<div class="yiv7515405395ydp1a9ae1dcyahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;">
<div>Hi Bogdan,</div>
<div><br clear="none">
</div>
<div>Yes, that was the theory I had, And after I remove the
fix_route_dialog function it</div>
<div>didn't reoccur yet, so I believe fix_route_dialog caused
the bad routing in my script I think.</div>
<div><br clear="none">
</div>
<div><br clear="none">
</div>
</div>
<div class="yiv7515405395yahoo_quoted" id="yiv7515405395yahoo_quoted_2694016622">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div> On Friday, 8 March 2019, 1:11:38 PM GMT+5:30,
Bogdan-Andrei Iancu <a rel="nofollow" shape="rect" class="yiv7515405395moz-txt-link-rfc2396E" ymailto="mailto:bogdan@opensips.org" target="_blank" href="mailto:bogdan@opensips.org"><bogdan@opensips.org></a> wrote: </div>
<div><br clear="none">
</div>
<div><br clear="none">
</div>
<div>
<div dir="ltr">Hi Pasan,<br clear="none">
<br clear="none">
Have you checked if there is traffic on looping on your
OpenSIPS ? maybe <br clear="none">
due bad routing, OpenSIPS is keep sending to itself some
traffic, <br clear="none">
causing the loops and the load.<br clear="none">
<br clear="none">
Regards,<br clear="none">
<br clear="none">
Bogdan-Andrei Iancu<br clear="none">
<br clear="none">
OpenSIPS Founder and Developer<br clear="none">
<a rel="nofollow" shape="rect" target="_blank" href="https://www.opensips-solutions.com">https://www.opensips-solutions.com</a><br clear="none">
OpenSIPS Summit 2019<br clear="none">
<a rel="nofollow" shape="rect" target="_blank" href="https://www.opensips.org/events/Summit-2019Amsterdam/">https://www.opensips.org/events/Summit-2019Amsterdam/</a><br clear="none">
<div class="yiv7515405395yqt3089660754" id="yiv7515405395yqtfd95079"><br clear="none">
On 03/07/2019 03:17 PM, Pasan Meemaduma wrote:<br clear="none">
> Hi Bogdan,<br clear="none">
><br clear="none">
> Thanks for the reply. writing inline replies<br clear="none">
><br clear="none">
><br clear="none">
> "Using t_on_reply() is harmless as it simply set a
holder in the msg/transaction, nothing more. And a
locally generated reply does NOT trigger on_reply_route
- this route is triggered only by *RECEIVED* replies."<br clear="none">
><br clear="none">
> My problem was that server received 407 replies
from its own source ip :/. I couldn't figure out what
triggered it. Anyhow issue resolved after I removed
fix_dialog_route() function which causes BYE to send to
a private ip of a NATed device. I have
fix_nated_contact() before create_dialog() function but
dialog data seems to have unmodified contact data which
I believe is fixed in 2.4 as you mentioned.<br clear="none">
><br clear="none">
> "So the bottom problem for you is why the
processes stuck ? do they stuck like consuming cpu
(doing some crazy looping) or blocking in some I/O (no
CPU usage) ?"<br clear="none">
><br clear="none">
> All traffic processing workers were stuck in a loop
and consume 100% CPU. I couldn't get much debug info
like running opensipsctl trap when issue occured :/<br clear="none">
><br clear="none">
> Anyhow now I'm planning to upgrade thee system to
2.4 this year which has support till 2021.<br clear="none">
> my sip cluster is now stable without
fix_dialog_route() function.<br clear="none">
><br clear="none">
> On 02/13/2019 09:36 AM, Pasan Meemaduma via Users
wrote:<br clear="none">
><br clear="none">
><br clear="none">
>> <br clear="none">
>> Hi Guys,<br clear="none">
>><br clear="none">
>><br clear="none">
>><br clear="none">
>><br clear="none">
>> How's it possible locally generated replied
triggering on_reply_route ? I ran in to issue where all
opensips process gets stuck in processing same call
replies and causing other traffic to get drop.<br clear="none">
>><br clear="none">
>><br clear="none">
>><br clear="none">
>><br clear="none">
>><br clear="none">
>><br clear="none">
>><br clear="none">
>> <info> /usr/sbin/opensips[27464]: Call:
Reply from a NAT endpoint - S=408 D=Request Timeout
F=sip:<a rel="nofollow" shape="rect" ymailto="mailto:xxx@xxx" target="_blank" href="mailto:xxx@xxx">xxx@xxx</a>
T=<a rel="nofollow" shape="rect" class="yiv7515405395moz-txt-link-freetext">sip:yyy</a><br clear="none">
>> <br clear="none">
>> <a rel="nofollow" shape="rect" ymailto="mailto:yy@x" target="_blank" href="mailto:yy@x">yy@x</a>
IP=a.b.c.d ID=asgasgasgas<br clear="none">
>><br clear="none">
>><br clear="none">
>><br clear="none">
>> Request process by opensips before this is an
ACK request belong to the call where I don't think It'll
expect a reply. Could it be an issue If I call
t_on_reply on an ACK msg ?<br clear="none">
>><br clear="none">
>><br clear="none">
>><br clear="none">
>><br clear="none">
>> I'm trying to figure out where the bug in my
opensips routing script. It causes all sip listerner
processes to get stuck in a loop causing to generate
above message. IP a.b.c.d is the sip server IP which
confuse me as locally generated replies shouldn't
trigger on_reply_route as per docs.<br clear="none">
>><br clear="none">
>><br clear="none">
>><br clear="none">
>><br clear="none">
>><br clear="none">
>> Any clue is welcome.<br clear="none">
>><br clear="none">
>><br clear="none">
>><br clear="none">
>><br clear="none">
>> I'm using opensips 2.3.6<br clear="none">
>><br clear="none">
>><br clear="none">
>><br clear="none">
>><br clear="none">
>><br clear="none">
>><br clear="none">
>><br clear="none">
>> _______________________________________________<br clear="none">
>> Users mailing list<br clear="none">
>> <a rel="nofollow" shape="rect" ymailto="mailto:Users@lists.opensips.org" target="_blank" href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br clear="none">
>> <a rel="nofollow" shape="rect" target="_blank" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br clear="none">
>> <br clear="none">
><br clear="none">
<br clear="none">
</div>
</div>
</div>
</div>
</div>
</blockquote></div>
<br clear="none">
</div></div></div>
</div>
</div></body></html>