<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi Jeff,</p>
<p>You can use proxy commands for different traffic flows but keep
in mind that once you trigger a B2B session in the main request
route (with the b2b_init_request() function), you will only see
the rest of the B2B related traffic in the dedicated routes. In
those routes it is recommended to not use proxy-like signaling
functions.</p>
<p>Regards,</p>
<p>Vlad<br>
</p>
<pre class="moz-signature" cols="72">.--
Vlad Patrascu
OpenSIPS Core Developer
<a class="moz-txt-link-freetext" href="http://www.opensips-solutions.com">http://www.opensips-solutions.com</a></pre>
<div class="moz-cite-prefix">On 28.01.2022 17:30, Jeff Pyle wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAPhW+0K7w-v9EPGc3EyEKJt650t58HXz6iQdw8PjBh+10upZHw@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div>Great. Is it still recommended to keep a particular
OpenSIPS instance either all proxy commands or all B2B
commands? Or, do we have some flexibility to mix them since
B2B commands live in the script now?</div>
<div><br>
</div>
<div><br>
</div>
<div>- Jeff</div>
<div><br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Wed, Jan 26, 2022 at 9:50
AM Vlad Patrascu <<a href="mailto:vladp@opensips.org"
moz-do-not-send="true" class="moz-txt-link-freetext">vladp@opensips.org</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<p>Hi Jeff,</p>
<p>Sending NOTIFYs is supported by using the "n" flag for
the b2b_bridge() [1] function. Just note that some
mechanisms from <a
href="https://datatracker.ietf.org/doc/html/rfc3515#section-2.4.4"
target="_blank" moz-do-not-send="true">RFC 3515 2.4.4</a>
are not implemented though, such as the ability to
terminate the subscription prematurely by unsubscribing or
refreshing the subscription.</p>
<p>[1] <a
href="https://opensips.org/docs/modules/3.2.x/b2b_logic.html#func_b2b_bridge"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://opensips.org/docs/modules/3.2.x/b2b_logic.html#func_b2b_bridge</a></p>
<p>Regards,</p>
<pre cols="72">--
Vlad Patrascu
OpenSIPS Core Developer
<a href="http://www.opensips-solutions.com" target="_blank" moz-do-not-send="true" class="moz-txt-link-freetext">http://www.opensips-solutions.com</a></pre>
<div>On 24.01.2022 17:38, Jeff Pyle wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>OpenSIPS 3.2 supports some slick in-script B2B
functions, documented <a moz-do-not-send="true">here
[1]</a> with an example for handling REFER. Does
this approach include support for the subscription and
the subsequent NOTIFYs required by <a
href="https://datatracker.ietf.org/doc/html/rfc3515#section-2.4.4"
target="_blank" moz-do-not-send="true">RFC 3515
2.4.4 [2]</a>? <br>
</div>
<div><br>
</div>
<div>I have a need to write some REFER handling
functions into an existing OpenSIPS SBC stack, and I
need to send accurate NOTIFYs back to the REFER-er.
Terminating the subscription with the first NOTIFY
isn't good enough, sadly. I'm hoping this is the
right way to do it.</div>
<div><br>
</div>
<div> [1] <a
href="https://www.opensips.org/Documentation/Tutorials-B2BUA-3-2#toc10"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://www.opensips.org/Documentation/Tutorials-B2BUA-3-2#toc10</a></div>
<div> [2] <a
href="https://datatracker.ietf.org/doc/html/rfc3515#section-2.4.4"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://datatracker.ietf.org/doc/html/rfc3515#section-2.4.4</a></div>
<div><br>
</div>
<div><br>
</div>
<div>- Jeff</div>
<div><br>
</div>
</div>
<br>
<fieldset></fieldset>
<pre>_______________________________________________
Users mailing list
<a href="mailto:Users@lists.opensips.org" target="_blank" moz-do-not-send="true" class="moz-txt-link-freetext">Users@lists.opensips.org</a>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank" moz-do-not-send="true" class="moz-txt-link-freetext">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
</blockquote>
</div>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">Users@lists.opensips.org</a><br>
<a
href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
</blockquote>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a>
<a class="moz-txt-link-freetext" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
</blockquote>
</body>
</html>