2009/7/20 Dushyant Dhalia <dushyant.dha...@rancoretech.com>: > I need to know what should be the request-uri for re-subscription?
Is it a question? :) > The RequestURI in initial/first SUBSCRIBE is set to the resource to which > the subscriber wants to be subscribed to. Yes. > In NOTIFY the notifier sends its > contact. Now my question is - is it okay for the subscriber to send > re-subscribe with RequestURI set to the contact it received in NOTIFY? No. The RURI of re-SUBSCRIBE should be the Contact received in the 200 OK to the initial SUBSCRIBE, that's all. Of course, the Contact in the NOTIFY from the server are equal. > Secondly, regarding routeing of re-subscribe. If first SUBSCRIBE was routed > through outbound proxy but the notifier and other nodes in the path included > the Record-Route in Notify, is it okay for the subscriber to send > re-subscribe through Route (by inserting route-header) it derived from > Record-Route? Record-Route should be ignored in *any* in-dialog request (as NOTIFY in a subscription dialog). The flow is: - The client sends SUBSCRIBE. - The proxy desiring to do loose-routing add Record-Route and routes it to the presence server. - The presence server mirrors the Record-Route in the 200 OK. - Any re-SUBSCRIBE from the client or NOTIFY from the server should contain "Route" header with that value. Just it. -- Iñaki Baz Castillo <i...@aliax.net> _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
