<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<tt>Yup :)</tt><br>
<pre class="moz-signature" cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a class="moz-txt-link-freetext" href="https://www.opensips-solutions.com">https://www.opensips-solutions.com</a>
OpenSIPS Summit, Amsterdam, May 2020
<a class="moz-txt-link-freetext" href="https://www.opensips.org/events/Summit-2020Amsterdam/">https://www.opensips.org/events/Summit-2020Amsterdam/</a>
</pre>
<div class="moz-cite-prefix">On 4/7/20 2:43 PM, Johan De Clercq
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:AM0PR06MB62264B01DA2E726E9E15BA83A7C30@AM0PR06MB6226.eurprd06.prod.outlook.com">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<div>
<div>
<div style="direction: ltr;">But where should I then check? In
the reply-route?</div>
</div>
<div><br>
</div>
<div class="ms-outlook-ios-signature"><a
href="https://aka.ms/o0ukef" moz-do-not-send="true">Outlook
voor iOS</a> downloaden</div>
</div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font style="font-size:11pt"
face="Calibri, sans-serif" color="#000000"><b>Van:</b>
Bogdan-Andrei Iancu <a class="moz-txt-link-rfc2396E" href="mailto:bogdan@opensips.org"><bogdan@opensips.org></a><br>
<b>Verzonden:</b> Tuesday, April 7, 2020 12:34:29 PM<br>
<b>Aan:</b> OpenSIPS users mailling list
<a class="moz-txt-link-rfc2396E" href="mailto:users@lists.opensips.org"><users@lists.opensips.org></a>; johan
<a class="moz-txt-link-rfc2396E" href="mailto:johan@democon.be"><johan@democon.be></a><br>
<b>Onderwerp:</b> Re: [OpenSIPS-Users] t_check_trans</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span
style="font-size:11pt;">
<div class="PlainText">The t_check_trans() is performing a
matching of the current request
<br>
against the known transaction. Such matching, for relies,
doesn't make <br>
too much of a sense as:<br>
<br>
1) if you use an onreply_route[], it means your reply
already <br>
matched the transaction<br>
<br>
2) for replies, there is no special handling for
retransmissions, <br>
they are handled in the same way as the first reply.
(unlikely for the <br>
requests)<br>
<br>
If you want to "catch" the 200 OK retransmission, simply
use a bflag - <br>
set it on first 200OK and test it for the next 200 OKs :)<br>
<br>
Regards,<br>
<br>
Bogdan-Andrei Iancu<br>
<br>
OpenSIPS Founder and Developer<br>
<a href="https://www.opensips-solutions.com"
moz-do-not-send="true">https://www.opensips-solutions.com</a><br>
<br>
<br>
On 4/6/20 6:56 PM, johan wrote:<br>
> Is there a specific reason why t_check_trans can't be
called in a <br>
> reply route ?<br>
><br>
> To me this seems handy to see if a 200 OK is a
retransmission.<br>
><br>
><br>
> BR,<br>
><br>
><br>
> _______________________________________________<br>
> Users mailing list<br>
> <a class="moz-txt-link-abbreviated" href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
> <a
href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users"
moz-do-not-send="true">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br>
</div>
</span></font></div>
</blockquote>
<br>
</body>
</html>