Section 2.19 in the ID draft-ietf-sipping-service-examples-10.txt uses REFER to suggest a click-to-dial implementation.
Also, section 2 in RFC 3515 says: A REFER request MAY be placed outside the scope of a dialog created with an INVITE. REFER creates a dialog... -Vishal -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Kyzivat Sent: Friday, March 24, 2006 9:12 AM To: Matthew Gardiner Cc: Sip-Implementors Subject: Re: [Sip-implementors] Multiple definitions of call transfer with in theIETF documentation I forget which draft, but I have seen proposals to use REFER with message=BYE to (IIRC) delete someone from a conference. Paul Matthew Gardiner wrote: >>>Primitives like >>>REFER scare me because it is hard to understand how the node receiving a >>>REFER can know in all cases what, if anything, to do with it. > > >>IMHO, REFER is under-specified in this way. If I remember correctly, I >>once tallied 5 distinctly different meanings for a REFER. IMHO, >>something needs to be done to enumerate and distinguish these meanings >>in order to finish specifying REFER. > > > Yes, as I stated earlier, my company's system, currently, only maps receipt > of REFER to a transfer request. What other meanings might receipt of REFER > have? > > Matt > > _______________________________________________ > Sip-implementors mailing list > [email protected] > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
