section 3.2 of rfc 3265 says -
If any non-SUBSCRIBE mechanisms are defined to create subscriptions,it is
the responsibility of the parties defining those mechanisms to ensure that
correlation of a NOTIFY message to the corresponding subscription is possible.
Designers of such
On Dec 11, 2007 12:42 PM, Brett Tate [EMAIL PROTECTED] wrote:
Please confirm my understanding of subscribe for MWI. NOTIFY
should not be sent to a UA unless a SUBSCRIBE has been sent to it.
RFC3265 allows for non-SUBSCRIBE mechanisms to create subscriptions.
Some vendors use the concept to
Vikram Chhibber wrote:
On Dec 11, 2007 12:42 PM, Brett Tate [EMAIL PROTECTED] wrote:
Please confirm my understanding of subscribe for MWI. NOTIFY
should not be sent to a UA unless a SUBSCRIBE has been sent to it.
RFC3265 allows for non-SUBSCRIBE mechanisms to create subscriptions.
Some
On Dec 11, 2007 12:42 PM, Brett Tate [EMAIL PROTECTED] wrote:
Please confirm my understanding of subscribe for MWI.
NOTIFY should
not be sent to a UA unless a SUBSCRIBE has been sent to it.
RFC3265 allows for non-SUBSCRIBE mechanisms to create subscriptions.
Some vendors use the
Certainly the motivation for the existing wording was to
accommodate REFER, and I suppose similar arrangements.
Yes; and subscriptions created through configuration (section 3.2.2).
NOTIFYs that don't contain a to-tag don't identify an
expected dialog, so I don't think they are consistent
