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 added xlog info after t_relay() and got:
May 20 09:08:02 siika /usr/sbin/sip-proxy[15173]: INFO: activating contact_failure failure
route
May 20 09:08:02 siika /usr/sbin/sip-proxy[15173]: INFO: activating contact branch_failure
route
May 20 09:08:02 siika /usr/sbin/sip-proxy[15173]: INFO: Routing INVITE
<sip:jh@192.98.102.10:5044;transport=tcp> to contact via
<sip:192.98.102.10:43560;transport=TCP>
May 20 09:08:02 siika /usr/sbin/sip-proxy[15173]: ERROR: tm [../../forward.h:216]:
msg_send(): msg_send: ERROR: tcp_send failed
May 20 09:08:02 siika /usr/sbin/sip-proxy[15173]: ERROR: tm [t_fwd.c:1592]:
t_send_branch(): ERROR: t_send_branch: sending request on branch 0 failed
May 20 09:08:02 siika /usr/sbin/sip-proxy[15173]: ERROR: tm [t_fwd.c:1595]:
t_send_branch(): putting branch 0 on hold
May 20 09:08:02 siika /usr/sbin/sip-proxy[15173]: INFO: t_relay() failed
that explains why 408 comes immediately, because i send it from script if t_relay() fails
and there are no more contacts left.
what i understood from this commit. t_relay() should not anymore fail if failure and
branch failure routes are set when tcp destination is dead, but it does.
----------
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.