[sr-dev] executing tm:branch-failure event_route also when t_relay() fails?

Juha Heinanen jh at tutpro.com
Mon May 13 17:15:27 CEST 2013


Daniel-Constantin Mierla writes:

> just thinking of it -- if you do t_newtran() before t_relay(), isn't it 
> getting to failure route?

yes, i do t_newtran() before t_relay, but still tm:branch-failure is not
executed.  here is an example with some debug xlog statements when
t_relay() is called on dead contact:

May 13 18:10:59 siika /usr/sbin/sip-proxy[23826]: INFO: Creating new transaction
May 13 18:10:59 siika /usr/sbin/sip-proxy[23826]: INFO: calling t_on_branch_failure("contact")
May 13 18:10:59 siika /usr/sbin/sip-proxy[23826]: INFO: Routing INVITE <sip:jh at 192.98.102.10:5044;transport=tcp> to contact via <sip:192.98.102.10:42590;transport=TCP>
May 13 18:10:59 siika /usr/sbin/sip-proxy[23826]: ERROR: tm [../../forward.h:216]: msg_send: ERROR: tcp_send failed
May 13 18:10:59 siika /usr/sbin/sip-proxy[23826]: ERROR: tm [t_fwd.c:1520]: ERROR: t_send_branch: sending request on branch 0 failed

my tm:branch-failure starts like this and the syslog message is not
printed meaning that the event_route is never executed:

event_route[tm:branch-failure:contact] {
    xlog("L_INFO", "event_route[tm:branch-failure:contact]\n");

it would be a big help, if it would be executed.

-- juha



More information about the sr-dev mailing list