On Wed, Jan 28, 2009 at 12:59 PM, Avasarala Ranjit-A20990
<ran...@motorola.com> wrote:
> So based on this, now which would be the recommended approach for realizing a 
>  Click2Dial application? Using a B2BUA (3PCC) as explained in 3725 or the 
> refer example in 5359?
>
>

Depends upon whether the endpoint supports REFER based redirection.

> Regards
> Ranjit
>
> -----Original Message-----
> From: sip-implementors-boun...@lists.cs.columbia.edu 
> [mailto:sip-implementors-boun...@lists.cs.columbia.edu] On Behalf Of Iñaki 
> Baz Castillo
> Sent: Wednesday, January 28, 2009 11:26 PM
> To: Brett Tate
> Cc: sip-implementors
> Subject: Re: [Sip-implementors] Initial REFER vs RFC 3725 (Third 
> PartyCallControl)
>
> 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":
>
>  http://tools.ietf.org/html/rfc5359#section-2.18
>
> 2.18.  Click to Dial
>
>
>        Bob's PC                Bob                Carol
>            | REFER Refer-To:Carol F1                 |
>            |------------------->|                    |
>            |  202 Accepted F2   |                    |
>            |<-------------------|                    |
>            |                    |     INVITE F3      |
>            |                    |------------------->|
>            |                    |   180 Ringing F4   |
>            |                    |<-------------------|
>            |                    |     200 OK F5      |
>            |                    |<-------------------|
>            |                    |       ACK F6       |
>            |                    |------------------->|
>            |                    |         RTP        |
>            |                    |<==================>|
>            |                    |                    |
>
>   In this example, while browsing the web on his PC, Bob clicks on
>   Carol's SIP URI, intending to establish a session with Carol.  Bob's
>   web browser passes the SIP URI to the SIP client on Bob's PC.  The PC
>   client is configured with the URI of Bob's SIP phone.  A REFER is
>   sent to the SIP phone, which results in the establishment of the
>   session between Bob and Carol.
>
>   Note that Bob's PC requests that no REFER dialog be established by
>   the use of the Refer-Sub: false header field [RFC4488].
>
>   This flow is preferable to the 3pcc flow because the end-to-end SIP
>   signaling is not interrupted by the 3pcc controller, and because
>   Bob's experience of the call will not be marred by the lack of
>   ringback tone or possible clipping.  Suitable authorization of the
>   REFER and explicit authorization of the triggered INVITE by Bob are
>   necessary.
>
>
> --
> 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
>



-- 
M. Ranganathan

_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors

Reply via email to