Thanks for the quick response,

I agree that this is the right way to do things, but what I'm wondering is if there is any situation where NOTIFY requests could be validly received outside of a dialog? For instance, what about RFC2543 compliant proxies (was there even the concept of a dialog in those?) ..

Chris Boulton wrote:

David,

        Sounds good to me.  A 202 response is a 2xx class response and
creates the dialog - so the Notify messages would also be part of that
dialog.  I don't see receiving a 202 different from receiving a 200
response in terms of dialog creation.

Regards,

Chris.




-----Original Message-----
From: David Stuart [mailto:[EMAIL PROTECTED]
Sent: 10 July 2003 15:52
To: [EMAIL PROTECTED]
Subject: [Sip-implementors] RFC3265 question

Hi All,

I have a question regarding SUBSCRIBE and NOTIFY requests with a proxy
in between, relating mostly to Dialogs. Here is the situation:

1) One (registered) UA
2) One proxy/registrar

The UA registers to the proxy and immediately sends a SUBSCRIBE for a
resource (for argument's sake let's use presence as an example since it
is the most well known).

The first subscribe request is outside of a dialog, and I believe is
considered to be a dialog-creating request. As such, there is a CallId
and the From: "tag" is set (but there is no "To:" "tag" yet).

The proxy responds with a 202 Pending, and then sends a NOTIFY request
with subscription-state pending.

My question is, should this NOTIFY request be inside or outside of the
dialog (I am assuming inside, but want to check).. That is to say, are
the callId and both the From "tag" and To "tag" set at this point?

--
David Stuart, SIPQuest
phone: 254-8886 x234 web: http://www.sipquest.com/

_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors







_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors

Reply via email to