On Fri, 2008-12-05 at 10:34 +0100, Ian Elz wrote: > For the Call pick up I was not referring to the headers in the SUBSCRIBE > but to the Event header specifically. > > RFC 4235 which defines the dialog event requires that the dialog event > has the call-id and at least the to-tag for the dialog on which the > subscription is to act (RFC 4235 Section 3.3): > > E.g. > > Event: dialog;call-id=536829AF35;to-tag=98153284afer
You mean "the Event header of a dialog event SUBSCRIBE". A "dialog event" (as people use the term) is the XML document described by RFC 4235. > I was asking if there has been any change to the dialog event definition > which allows you to SUBSCRIBE for all dialogs on a UA. To the extent that "a UA" can be identified by a single contact URI, if you send a SUBSCRIBE to that URI with the header "Event: dialog", then you should receive dialog events that contain all dialogs that involve that contact. The problem is practice is "multi-line phones", where each line has a different AOR and contact URI. In that case, a SUBSCRIBE directed to one contact URI receives dialog events for dialogs "on that one line". There is no standardized mechanism for obtaining dialog events for all dialogs active on a physical phone with multiple contact URIs. Dale _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use [EMAIL PROTECTED] for questions on current sip Use [EMAIL PROTECTED] for new developments on the application of sip
