THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#468 - CANCEL sent shortly after '100 trying' response to INVITE does not always end the call User who did this - Daniel-Constantin Mierla (miconda)

---------- I pushed a patch to detect if the transaction was canceled during execution of branch_route and skip forwarding the branches.

- http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=b66033d0...

If you can test and report back the results, then I will backport, provided all is ok.

On the other hand, this INVITE-CANCEL-1xx race can happen even later. Like the process is losing the CPU just before writing the branch to the socket and the one that gets the CPU gets the CANCEL and processes it. In such case, the race will be caught later by one of the nodes (proxy, or even UA).

The UA should be prepared to handle CANCEL races anyhow, a 200ok can be on the wire towards it at the moment it sends CANCEL. Due to network transmission delays, it is impossible to avoid such races.

----------

More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=468#comment16...

You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.