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] < [1]
https://www.opensips.org/Documentation/Tutorials-B2BUA-3-2#toc10> 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
<https://www.opensips.org/Documentation/Tutorials-B2BUA-3-2#toc10>
[2] https://datatracker.ietf.org/doc/html/rfc3515#section-2.4.4
<https://datatracker.ietf.org/doc/html/rfc3515#section-2.4.4>
- Jeff
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
