<div dir="ltr">I think you can relay the message to the client, as you are probably doing already. <div><br></div><div>But as far I know, you shouldn't reply the BYE but just relay it to the customer and account the transaction, even if response wasn't 200 OK, by setting this parameter on ACC module:</div><div><h3 class="" style="color:rgb(0,0,0);font-family:Helvetica,Arial"><code class="">failed_transaction_flag</code> </h3><div><br></div><div>Saudações paulistanas!</div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Mar 17, 2016 at 11:20 AM, Daniel Moreira Yokoyama <span dir="ltr"><<a href="mailto:moreira.yokoyama@gmail.com" target="_blank">moreira.yokoyama@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi Daniel.<div><br></div><div>Thanks for the advice.</div><div><br></div><div>I wonder, once opensips sends the 200 to the UAC, how should it deal with the BYE to the UAS from now on?</div><div><br></div><div><br></div><div>Thanks again.</div></div><div class="gmail_extra"><span class=""><br clear="all"><div><div><div dir="ltr"><div><div dir="ltr"><div><br></div><div><div style="font-size:small">Atenciosamente,<br><br>Daniel Moreira Yokoyama.</div><div style="font-size:small">@dmyoko</div><div style="font-size:small"><a href="http://twitter.com/dmyoko" style="color:rgb(17,85,204)" target="_blank">http://twitter.com/dmyoko</a></div><div style="font-size:small"> </div><div style="font-size:small">TrafficTalks<br>Um podcast sobre cinema feito a partir de conversas de trânsito.</div><div style="font-size:small"><a href="http://traffictalks.com.br" target="_blank">http://traffictalks.com.br</a></div></div><div><br></div></div></div></div></div></div>
<br></span><div><div class="h5"><div class="gmail_quote">2016-03-17 10:55 GMT-03:00 Daniel Zanutti <span dir="ltr"><<a href="mailto:daniel.zanutti@gmail.com" target="_blank">daniel.zanutti@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi Daniel<div><br></div><div>SIPP is a litte tricky to work with proxies, you need to double check routes and Via headers.</div><div><br></div><div>Here is what I'm using on BYE:</div><div><br></div><div><div> BYE [next_url] SIP/2.0</div><div> Via: SIP/2.0/[transport] [local_ip]:[local_port];branch=[branch]</div><div> [routes]</div><div> From: <sip:[$1]@[$2]:[local_port]>;tag=[pid]SIPpTag00[call_number]</div><div> To: <sip:[field0]@[$2]:[remote_port]>[peer_tag_param]</div><div> Call-ID: [call_id]</div><div> CSeq: 2 BYE</div><div> Contact: sip:sipp@[local_ip]:[local_port]</div><div> Max-Forwards: 70</div><div> Subject: Performance Test</div><div> Content-Length: 0</div></div><div><br></div><div>Using these vars:</div><div><div> <assignstr assign_to="1" value="fromuser" /><br></div><div> <assignstr assign_to="2" value="fromdomain" /></div></div><div><br></div><div>About Opensips, you can manipulate the BYE on loose_route and send anything you want, but you have to make sure you don't break something else. Like this:</div><div><br></div><div><div>if(loose_route())</div><div>{</div><div> ...</div><div><span style="white-space:pre-wrap">        </span>if (is_method("BYE"))</div><div><span style="white-space:pre-wrap">        </span>{</div><div><span style="white-space:pre-wrap">                        </span>xlog("L_NOTICE", "LOG BYE -> SEND 200 OK");</div><div><span style="white-space:pre-wrap">                        </span>sl_send_reply("200", "OK");</div><div><span style="white-space:pre-wrap">        </span>}</div><div> ...</div><div>}</div></div></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div>On Thu, Mar 17, 2016 at 10:35 AM, Daniel Moreira Yokoyama <span dir="ltr"><<a href="mailto:moreira.yokoyama@gmail.com" target="_blank">moreira.yokoyama@gmail.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div dir="ltr">Hi.<div><br></div><div>During stress tests (using SIPP as UAC and UAS) Opensips receives a BYE request from UAC and relays it to UAS.</div><div><br></div><div>The problem is, when the UAS responds 200 to it, Opensips seems to be ignore it (may it be because of it misses it among the thousands of other messages being exchanged, may it be for any other reason I can't figure out).</div><div><br></div><div>The RFC says that on BYE, in case of a 4xx or a timeout, the dialog should be considered terminated... but what opensips does in this scenario is to retry the BYE a couple of times (and SIPP seems to ignore it, once it consider the dialog finished, i guess) and finally opensips sends a 408 to the UAC.</div><div><br></div><div>The way I see it, unless I'm missing something, I should be able to react to a BYE by immediately send a 200 to the UAC despite of what happens between opensips and UAS (accodingly to what I learn from the RFC). And, concerning to the UAS, Opensips also should send the BYE and consider the dialog finished regardless of receiving the 200 or not (it should not try to send the BYE again).</div><div><br></div><div>If I'm right, how should I set opensips to behave this way?</div><div><br></div><div>If I'm wrong, what should be the way to handle this scenario?</div><div><div><div><div dir="ltr"><div><div dir="ltr"><div><br></div><div><div style="font-size:small">Atenciosamente,<br><br>Daniel Moreira Yokoyama.</div><div style="font-size:small">@dmyoko</div><div style="font-size:small"><a href="http://twitter.com/dmyoko" style="color:rgb(17,85,204)" target="_blank">http://twitter.com/dmyoko</a></div><div style="font-size:small"> </div><div style="font-size:small">TrafficTalks<br>Um podcast sobre cinema feito a partir de conversas de trânsito.</div><div style="font-size:small"><a href="http://traffictalks.com.br" target="_blank">http://traffictalks.com.br</a></div></div><div><br></div></div></div></div></div></div>
</div></div>
<br></div></div>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br></blockquote></div><br></div>
<br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br></blockquote></div><br></div></div></div>
<br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br></blockquote></div><br></div>