Hi, >Correct. It is entirely possible to do 3pcc without INVITE. However, >the phone must support out of dialog REFER. This poses a security risk >which can be mitigated by authentication of the REFER.
I don't see why REFER can't do following. *) Target phone gets REFER and rings *) Phone displays refer info to user *) user can accept or reject refer Also current normal invite + refer, should stay. This is also usefully, but just for click to dial it's too much overhead. M. Ranganathan wrote: > On Wed, Jan 28, 2009 at 12:56 PM, Iñaki Baz Castillo <i...@aliax.net> wrote: > >> 2009/1/28 Iñaki Baz Castillo <i...@aliax.net>: >> >>> Hi, that's not necessary at all as it's already documented in the same >>> RFC 3515 (REFER method): >>> >>> http://tools.ietf.org/html/rfc3515#section-4.1 >>> >> And it's also fully explained and documented in RFC 5359 "Session >> Initiation Protocol Service Examples": >> > > >> ringback tone or possible clipping. Suitable authorization of the >> REFER and explicit authorization of the triggered INVITE by Bob are >> necessary. >> >> > > Correct. It is entirely possible to do 3pcc without INVITE. However, > the phone must support out of dialog REFER. This poses a security risk > which can be mitigated by authentication of the REFER. > > > >> -- >> Iñaki Baz Castillo >> <i...@aliax.net> >> >> _______________________________________________ >> Sip-implementors mailing list >> Sip-implementors@lists.cs.columbia.edu >> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors >> > > > > _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
