Just to be sure there is no confusion:

Target refresh requests are any request that updates the Remote URI. Could you point to where
you saw "only the Remote URI"? That's not right and I'll put a bug against whatever text led you to
that.


The currently defined target refresh requests are INVITE, UPDATE, SUBSCRIBE, NOTIFY, and REFER.

RjS

On Feb 2, 2005, at 2:27 PM, Paul Kyzivat wrote:

One example is when a UA in a call wants to mutate into a conference mixer. So maybe it changes from
Contact: <sip:[EMAIL PROTECTED]>
to
Contact: <sip:[EMAIL PROTECTED]>;isfocus


Another case is when you have some sort of cluster and want to hand off the call from one cluster member to another for load balancing or fault recovery.

        Paul

Baniel Uri-CUB001 wrote:
The SIP RFC (3261) defines Target refresh requests as requests that are sent within a dialog and update only the Remote URI. Does anyone have an good use case example for such a request?
-uri _______________________________________________
Sip-implementors mailing list
[email protected]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
_______________________________________________
Sip-implementors mailing list
[email protected]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors

_______________________________________________ Sip-implementors mailing list [email protected] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors

Reply via email to