<html><head></head><body><div class="ydp61686982yahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;">Hi Guys,</div><div class="ydp61686982yahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;"><br></div><div class="ydp61686982yahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;">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.</div><div class="ydp61686982yahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;"><br></div><div class="ydp61686982yahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;"><br></div><div class="ydp61686982yahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;"><span><info> /usr/sbin/opensips[27464]: Call: Reply from a NAT endpoint - S=408 D=Request Timeout F=sip:xxx@xxx T=sip:yyy<br></span><div><span>yy@x IP=a.b.c.d ID=asgasgasgas</span></div><div><span><br></span></div><div>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 ?</div><div><br></div><div>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></div><div><br></div><div>Any clue is welcome.</div><div><br></div><div>I'm using opensips 2.3.6<br></div></div></body></html>