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 - Juha Heinanen (jh) ---------- i re-build kamailio from latest master and still in my test branch and normal failure route is not executed by t_relay() to dead tcp destination. i get May 20 08:05:21 siika /usr/sbin/sip-proxy[14415]: INFO: activating contact_failure failure route May 20 08:05:21 siika /usr/sbin/sip-proxy[14415]: INFO: activating contact branch_failure route May 20 08:05:21 siika /usr/sbin/sip-proxy[14415]: INFO: Routing INVITE <sip:jh@192.98.102.10:5044;transport=tcp> to contact via <sip:192.98.102.10:43368;transport=TCP> May 20 08:05:21 siika /usr/sbin/sip-proxy[14415]: ERROR: tm [../../forward.h:216]: msg_send(): msg_send: ERROR: tcp_send failed May 20 08:05:21 siika /usr/sbin/sip-proxy[14415]: ERROR: tm [t_fwd.c:1592]: t_send_branch(): ERROR: t_send_branch: sending request on branch 0 failed May 20 08:05:21 siika /usr/sbin/sip-proxy[14415]: ERROR: tm [t_fwd.c:1595]: t_send_branch(): putting branch 0 on hold the branch is put on hold, but never released from there. using the same config and same destination that registered over udp and then died, both branch and normal failure routes do get executed after fr_timer fires. in tcp case, calling party gets 408 immediately, i.e., kamailio does not wait for fr_timer to fire. i don't know what the difference could be. i call t_on_failure(), t_on_branch() and "if (t_relay()) exit;" in route block and t_on_branch_failure() in branch route block. ---------- More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=296#comment8… 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.