Hi Pasan,
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.
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) ?
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
https://www.opensips-solutions.com
OpenSIPS Summit 2019
https://www.opensips.org/events/Summit-2019Amsterdam/
On 02/13/2019 09:36 AM, Pasan Meemaduma via Users wrote:
Hi Guys,
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.
<info> /usr/sbin/opensips[27464]: Call: Reply from a NAT endpoint -
S=408 D=Request Timeout F=sip:xxx@xxx T=sip:yyy
yy@x IP=a.b.c.d ID=asgasgasgas
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 ?
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.
Any clue is welcome.
I'm using opensips 2.3.6
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users