Folks, Just a few questions on RFC4235 [1]: An INVITE-Initiated Dialog Event Package for the Session Initiation Protocol (SIP)
#Subscription to a specific dialog The subscriber constructs a SUBSCRIBE request: -The Event header contains a token which indicates the type of state for which a subscription is being requested: dialog -The Event header contains parameters: call-id, to-tag and from-tag The notifier checks that the event package specified in the Event header (dialog) is understood but the event header parameters (call-id, to-tag and from-tag) don't match to any existing dialog. Which is the proper behavior for the notifier: a) Return a "489 Bad Event" response to indicate that the specified event/event class is not understood b) Accept the subscription and trigger a NOTIFY message including: -Subscription-State header field set to noresource -A body containing an error message c) Other? #Section 3.3. SUBSCRIBE Bodies, says: A SUBSCRIBE request for a dialog package MAY contain a body. This body defines a filter to be applied to the subscription. Filter documents are not specified in this document, and at the time of writing, they are expected to be the subject of future standardization activity. Is there any further work on it? [1] ftp://ftp.rfc-editor.org/in-notes/rfc4235.txt Cheers, -- Victor Pascual Ávila _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
