Re: [Sip] Canceling REFER

[Robert Sparks <rsparks@dynamicsoft.com>]

There is no defined "Stop trying to access the resource I've REFERed
you to" mechanism. REFER is not designed to be a remote-control for
a peer endpoint.

CANCELing the REFER won't make sense - the REFER is accepted or
rejected immediately and processing the reference happens after
that - the REFER transaction is already gone.

Attempting to construct a REFER to a CANCEL that would match an
INVITE triggered by a previous REFER is difficult. You don't have
the appropriate Call-ID/tags handy and even if you could get them,
there's language in the REFER draft that encourages an agent accepting
a REFER to ignore them.

So - if this functionality is something that we have a real need for,
its a new method (NEVERMIND perhaps?).

RjS

On Thu, 2003-09-04 at 14:30, Mark Eastman (meastman) wrote:
> Hello,
> 
> I have a question about how to deal with canceling a REFER.  Let's say I 
> REFER Bob to Betty, but then decide I want to REFER Bob to someone else 
> before the transfer is complete.  Are there existing call flows describing 
> such behavior?  I know the REFER rfc states handling multiple refers is 
> valid, but is that how one would handle this situation (Sending a new REFER 
> with either a new target or perhaps method=CANCEL).  If so, call flows 
> describing such behavior would be nice.
> 
> Thanks,
> Mark
> 
> 
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip


_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip