Răzvan Crainea razvan at opensips.org
Tue Sep 26 12:30:36 EDT 2017

Hi, Royee!

There's no need for an actual dialog (from OpenSIPS pov) - you can 
simply route the NOTIFY messages as sequentials - route them according 
to the Record-Route headers.

Best regards,

Răzvan Crainea
OpenSIPS Developer

On 09/25/2017 07:06 PM, Royee Tichauer via Users wrote:
> Hi,
> I am using opensips 2.1 as a SIP proxy and I am trying to figure out 
> how to best handle SUBSCRIBE messages which need to be routed through 
> to another SIP component. As I read in the rfc3265 
> <https://tools.ietf.org/html/rfc3265#ref-1> an initial (out of call) 
> SUBSCRIBE creates a dialog which NOTIFYs and following SUBSCRIBE 
> messages are part of and are routed within the same dialog.
> From looking at the opensips code I see that when "create_dialog" is 
> called then the request is only handled if it is an INVITE request. So 
> I'm trying to understand what is the proper way of handling the 
> SUBSCRIBEs that come from the devices and the NOTIFYs that come from 
> the PBX after the SUBSCRIBE is accepted.
> If there are examples for handling such SUBSCRIBEs that would be great.
> Thanks,
> Royee
> _______________________________________________
> 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/20170926/8c0e9a08/attachment-0001.html>

More information about the Users mailing list