Hi,
Section 3.2 of RFC 3265 says:
NOTIFY messages are sent to inform subscribers of changes in state to which the subscriber has a subscription. Subscriptions are typically put in place using the SUBSCRIBE method; however, it is possible that other means have been used.
Let's assume a "other means" can include mechanisms unrelated to SIP.
What does that mean for the form of the NOTIFY, specifically the dialog id?
Can it not have a dialog id? (Can it be a request outside of a dialog?)
Can it have a dialog id unknown to to the receiver (and be valid)?
Can the dialog id be determined (dialog be established?) by the non-SIP mechanism that "put in place" a subscription?
Some implementations support "unsolicited NOTIFYs". Do they typically meet the RFC via the above means or do they break the RFC? How so?
Thanks, -troy _______________________________________________ Sip-implementors mailing list [email protected] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
