[reSIProcate] Receiving response to CANCEL, using DUM

[Robert Sparks]

You need to look at the final response to the INVITE to determine  
whether or not it was cancelled.
The response to the CANCEL itself doesn't tell you anything about the  
invite - just that the CANCEL
was received. (This is because the CANCEL may cross the INVITE-200OK  
on the wire - the UAS
must still send a 200-CANCEL even if its already sent a 200-INVITE).

If the INVITE is actually cancelled, you'll get a 487-INVITE. If it  
wasn't, you'll get something else.

RjS

On Jan 8, 2007, at 2:12 AM, David Hogan wrote:

> Hi List,
>
> Using dum, is there a way to be notified when a proxy responds to my
> CANCEL of a previous INVITE? I've noticed that none of the event
> handlers I've registered are being invoked in this case.
>
> I had a look a the dum source and found that
> DialogUsageManager::processResponse() directly avoids processing
> responses to a CANCEL. Should I consider that my 'call' is in a
> 'disconnected' state after having sent a CANCEL, and relying that any
> subsequent responses to my initial INVITE will be thrown away by dum?
>
> Any clarification or tips will be much appreciated!
>
> Cheers,
> David Hogan
>
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel at list.resiprocate.org
> https://list.resiprocate.org/mailman/listinfo/resiprocate-devel