Re: [reSIProcate] Receiving response to CANCEL, using DUM
Thanks for the response! I now have some follow up questions about
CANCELing an INVITE:
1. If I need to CANCEL an INVITE before an early dialog has been
created, should I call end() on the AppDialogSet?
2. If so, I'm noticing in my remote peer timeout test scenario, that a
subsequent 408-INVITE is 'thrown away as stray response' and
onTerminate() is never called. Is this expected, or is the culprit
likely to be an issue with the format of the 408-INVITE?
3. If this is expected, should I consider my call 'hung up' as soon as I
attempt to CANCEL an INVITE, in the case that an early dialog has not
yet been created?
Thanks again,
David Hogan
> -----Original Message-----
> From: Robert Sparks [mailto:rjsparks@xxxxxxxxxxx]
> Sent: Tuesday, 9 January 2007 12:58 AM
> To: David Hogan
> Cc: resiprocate-devel@xxxxxxxxxxxxxxxxxxxx
> Subject: Re: [reSIProcate] Receiving response to CANCEL, using DUM
>
> 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