Paul, my conclusion comes from RFC 3261 (�8.1.1 about the Contact Header): ... the Contact header field value contains the URI at which the UA would like to receive requests, and this URI MUST be valid even if used in subsequent requests outside of any dialogs.
Franz -----Original Message----- From: Paul Kyzivat [mailto:[EMAIL PROTECTED] Sent: Freitag, 11. Juli 2003 17:35 To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Franz Edler wrote: > Hi all, > > can anybody please confirm my following assumptions on some URIs in > SUBSCRIBE/NOTIFY messages: > > SUBSCRIBE is a dialog creating method and therefore the addresses sent in > the Contact-header of the request and the response should be used as request > URIs in subsequent requests. Therefore > > 1. A NOTIFY-request should use the URI of the Contact-header of > SUBSCRIBE-request as Request URI. > > 2. SUBSCRIPTION refresh requests should use the URI of the Contact-header of > the 200-response to SUBSCRIBE as Request URI. The above all seems right. > 3. If the same UA also uses PUBLISH-requests, it should also adhere to the > above rules and use the URIs exchanged in the Contact-headers of existing > SUBSCRIPTION based dialogs. How do you draw this conclusion? PUBLISH isn't dialog creating, and isn't required (or expected) to be sent in the context of a dialog. Paul _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
