[sr-dev] [tracker] Task opened: tm:branch-failure event_route is not executed on all branch failures

[sip-router]

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

A new Flyspray task has been opened.  Details are below. 

User who did this - Juha Heinanen (jh) 

Attached to Project - sip-router
Summary -  tm:branch-failure event_route is not executed on all branch failures
Task Type - Bug Report
Category - tm
Status - New
Assigned To - 
Operating System - All
Severity - Medium
Priority - Normal
Reported Version - Development
Due in Version - Undecided
Due Date - Undecided
Details - when t_relay() fails due to unreachable tcp destination, [t_fwd.c:1520] generates error message

LOG(L_ERR, "ERROR: t_send_branch: sending request on branch %d "
				"failed\n", branch);

and immediately sends back SIP/2.0 477 Unfortunately error on sending to next hop occurred (477/TM) response. 

tm:branch-failure event_route is not executed although it has been activated for the branch. instead, this makes is difficult to act on the failing branch in the config script, for example, by unregistering the unresponsive contact.

currently tm:branch-failure event_route is executed only from t_reply.c when reply is processed. one possibility to fix this might be generating a fake reply from t_fwd.c so that t_reply.c could do its job.  another one might be calling the activated tm:branch-failure event_route directly from t_fwd.c.

i would appreciate if someone who is familiar with internals of tm module could fix this bug.

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

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.