[Devel] Re: TM failure route bug

[Juha Heinanen]

Klaus Darilion writes:

 > Bogdan-Andrei Iancu wrote:

 > >    1) a fast CANCEL happens and the CANCEL is processed by the proxy 
 > > prior to INVITE. So, no INVITE is matched by CANCEL.
 > >    2) CANCEL is is just forwarded statefully without any other info 
 > > regarding the INVITE
 > >    3) the INVITE is finally processed and, without any knowledge of 
 > > CANCEL, it's statefully forwarded.

when cancel is not matched by any existing transaction, it means that
cancel arrived earlier than the invite or the invite got lost.  would it
then make sense to create an (invite) transaction based on the cancel
and respond with 487 and start waiting for ack?  if matching invite
arrives when the transaction still exists in the proxy, it would be
silently discarded.

-- juha