<div dir="ltr">Hi Stephan!<div><br></div><div>Nice to year about you ;)</div><div><br></div><div>I have just tried:</div><div>

<span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">set_forward_no_connect()</span></div><div><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">t_set_disable_internal_reply(1)</span><br></div><div><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><br></span></div><div>I wasn't aware that the code located</div><div>after the t_relay failure would run after</div><div>the branch failure.</div><div><br></div><div>

<div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial">Great to know about this.</div></div><div><br></div>I will experiment t_suspend and t_continue<div>in this use-case!</div><div><br></div><div>Tks a lot for the tip!</div><div>Aymeric<br><div><br></div><div><br></div><div><br></div><div><br></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">2018-02-09 20:31 GMT+01:00 Stefan Sayer <span dir="ltr"><<a href="mailto:stefan.sayer@googlemail.com" target="_blank">stefan.sayer@googlemail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">Aymeric Moizard wrote on 09.02.2018 13:49:<br>
> I understand your warning about TCP: If I have only on TCP branch and<br>
> it fails<br>
> I guess I will have a fast " I'm terribly sorry, server error occurred<br>
> (7/SL)" answer<br>
> and no time for my "pushed" app to be already registered. However, I<br>
think<br>
<br>
</span>usrloc's handle_lost_tcp is a good tip. we're using these in a push<br>
notification config for webrtc [0]:<br>
<br>
set_forward_no_connect();<br>
t_set_disable_internal_reply(<wbr>1);<br>
<br>
and then if t_relay() fails ts_store and t_suspend the transaction<br>
which I believe works.<br>
<br>
Stefan<br>
<br>
[0]<br>
<a href="https://github.com/saycel/kamailio-config/blob/fc17b58369af5a487d131dd67ac3c6a8628d1b29/kamailio.cfg#L695" rel="noreferrer" target="_blank">https://github.com/saycel/<wbr>kamailio-config/blob/<wbr>fc17b58369af5a487d131dd67ac3c6<wbr>a8628d1b29/kamailio.cfg#L695</a><br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><img src="http://sip.antisip.com/am48.png">Antisip - <a href="http://www.antisip.com" target="_blank">http://www.antisip.com</a><br></div>
</div>