Re: Route header in NOTIFY
"DRAGE, Keith \(Keith\)" <[email protected]>
| Newsgroups | gmane.ietf.sip,gmane.ietf.sip-implementors |
|---|---|
| Message-ID | <[email protected]> |
I am unsure where you see a problem. RFC 3265 clearly provides for the Route header to appear in the NOTIFY request if you need to do this, and has text explicitly talking about the record route mechanism working as normal in SUBSCRIBE dialogs. regards Keith ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Thursday, November 06, 2008 12:44 PM To: [email protected] Cc: [email protected] Subject: [Sip] Route header in NOTIFY Hi, If SUBSCRIBE request and response has record route header, then should NOTIFY messages need to have ROUTE header to follow the same route as created in the dialog for SUBSCRIBE. Regards, Udit CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is being sent by 3Com for the sole use of the intended recipient(s) and may contain confidential, proprietary and/or privileged information. Any unauthorized review, use, disclosure and/or distribution by any recipient is prohibited. If you are not the intended recipient, please delete and/or destroy all copies of this message regardless of form and any included attachments and notify 3Com immediately by contacting the sender via reply e-mail or forwarding to 3Com at [email protected]. _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use [email protected] for questions on current sip Use [email protected] for new developments on the application of sip