[OpenSIPS-Users] Managing the implicit subscription and its NOTIFYs within B2BUA REFER handling

[Vlad Patrascu]

Hi Jeff,

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.

Regards,

Vlad

.--
Vlad Patrascu
OpenSIPS Core Developer
http://www.opensips-solutions.com

On 28.01.2022 17:30, Jeff Pyle wrote:
> 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?
>
>
> - Jeff
>
>
> On Wed, Jan 26, 2022 at 9:50 AM Vlad Patrascu <vladp at opensips.org> wrote:
>
>     Hi Jeff,
>
>     Sending NOTIFYs is supported by using the "n" flag for the
>     b2b_bridge() [1] function. Just note that some mechanisms from RFC
>     3515 2.4.4
>     <https://datatracker.ietf.org/doc/html/rfc3515#section-2.4.4> are
>     not implemented though, such as the ability to terminate the
>     subscription prematurely by unsubscribing or refreshing the
>     subscription.
>
>     [1]
>     https://opensips.org/docs/modules/3.2.x/b2b_logic.html#func_b2b_bridge
>
>     Regards,
>
>     -- 
>     Vlad Patrascu
>     OpenSIPS Core Developer
>     http://www.opensips-solutions.com
>
>     On 24.01.2022 17:38, Jeff Pyle wrote:
>>     OpenSIPS 3.2 supports some slick in-script B2B functions,
>>     documented here [1] with an example for handling REFER.  Does
>>     this approach include support for the subscription and the
>>     subsequent NOTIFYs required by RFC 3515 2.4.4 [2]
>>     <https://datatracker.ietf.org/doc/html/rfc3515#section-2.4.4>?
>>
>>     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.
>>
>>       [1]
>>     https://www.opensips.org/Documentation/Tutorials-B2BUA-3-2#toc10
>>       [2] https://datatracker.ietf.org/doc/html/rfc3515#section-2.4.4
>>
>>
>>     - Jeff
>>
>>
>>     _______________________________________________
>>     Users mailing list
>>     Users at lists.opensips.org
>>     http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>     _______________________________________________
>     Users mailing list
>     Users at lists.opensips.org
>     http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20220128/ac9615db/attachment.html>