THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added:
FS#296 - tm:branch-failure event_route is not executed on all branch failures User who did this - Daniel-Constantin Mierla (miconda) ---------- Just checked a bit and variants can be: 1) execute branch failure route immediately it is discovered a tcp connection is not available, but this means kind of blocking to execute the actions from the branch failure route and then the next branch will be generated 2) add the branch in a dummy timer mode that will trigger a timeout event - there will be no attempt to send it, the branch will be put in a "suspended" state, the rest of the branches will be generated and the timer will end up firing at some point The 2nd is more like what would happen if the request is sent over udp, from the point of view of timings. This option might be easier to do and should also end up in failure_route execution if all branches fail. Again, just few thought on quick check, it may need more than that, though. ---------- More information can be found at the following URL: https://sip-router.org/tracker/index.php?do=details&task_id=296#comment867 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. _______________________________________________ sr-dev mailing list [email protected] http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
