< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index Next in Thread >

Re: [reSIProcate] 200 OK for SUBSCRIBE


There's a lot of background that led to this design decision, and the code _is_ doing this on purpose.

Here's an attempt to capture that background in a nutshell:

Because proxies can only return one final response to a non-INVITE request, RFC3265 mandates an initial NOTIFY to each subscription. If a SUBSCRIBE forks, the NOTIFYs are the only way the subscribing client finds out about all the places the subscription was accepted. Further, even in the scenario where there is no forking, or even no proxies, the NOTIFY is enough to let you know the subscription has been created. So to unify the code, DUM only pays attention to the NOTIFYs for creating subscription usages. The 2xx to the SUBSCRIBE itself is ignored (it will always be redundant with the immediate NOTIFY from
one branch).

RjS

On Nov 29, 2005, at 6:14 PM, Suresh Rangaswamy wrote:

Hi



In the response handling in Dialog::dispatch, I see a code which ignores the 2XX response for SUBSCRIBE. Is there a reason why? In this case, how does the application get to know about successful (200 OK) for SUBSCRIBE.



Case SUBSCRIBE:

int code = response.header (h_StatusLine).statusCode();

                        if ( code < 300)

                        {

                                    return;

                        }





Any thoughts on this



Regards

Suresh



_______________________________________________
resiprocate-devel mailing list
resiprocate-devel@xxxxxxxxxxxxxxxxxxx
https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel