As per RFC 3265, subscribers need to refresh subscriptions on a periodic basis using a new SUBSCRIBE message on the same dialog as defined in RFC 3261.
Chapter 12.2 'Requests within a Dialog' in RFC 3261 states, The UAC uses the remote target and route set to build the Request-URI and Route header field of the request. If the route set is empty, the UAC MUST place the remote target URI into the Request-URI. In essence, subscription is established with a UA instance and refresh should also reach the same instance. That means, use the remote target URI(obtained from Contact) to refresh the subscription. -Ramakrishna -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Goutham V. Jain Sent: Monday, November 14, 2005 1:01 PM To: [email protected] Subject: [Sip-implementors] Request Uri in Subscribe Referesh Hi, When an watcher refreshes the Subscribe in a dialog, what the request URI must be 1. The contact header SIP URI received in the 200 Ok of Initial SUBSCRIBE OR 2. The Presentity or Resource SIP URI. Note: If no route header is present. Thanks, Goutham V Jain _______________________________________________ Sip-implementors mailing list [email protected] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors Confidentiality Notice The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain confidential or privileged information. If you are not the intended recipient, please notify the sender at Wipro or [EMAIL PROTECTED] immediately and destroy all copies of this message and any attachments. _______________________________________________ Sip-implementors mailing list [email protected] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
