[Serusers] Re: How to execute failure_route block on tcp connect failure.

Hello, I have some more information about this issue. There are actually two problems. First - When the 1st attempt fails because connection was refused, connection timed out, or there was no route to host, an error message as logged and the failure_route block is never executed. Second - When the 2nd or 3rd, etc attempt fails due to a connection problem, an error is logged and only 30 seconds later the failure_route block is executed. I would really appreciate if some body could explain what is going on or point me in the right direction. Thank You, Dmitry ----- Original Message ----- From: Dmitry Isakbayev To: serusers(a)lists.iptel.org Sent: Wednesday, June 15, 2005 9:12 PM Subject: How to execute failure_route block on tcp connect failure. Hello, I am having a problem executing a failure_route block when t_relay fails to establish a tcp connection. Everything works as expected when t_relay connects to a proxy and receives back an error like 501. Is there a way to configure t_relay to execute a failure_route block an a tcp connection error? Thank You in advance. Dmitry Here are the logs from connection failure - Jun 15 20:52:14 localhost ser[21870]: ERROR: tcp_blocking_connect: SO_ERROR (111) Connection refused Jun 15 20:52:14 localhost ser[21870]: ERROR: tcpconn_connect: tcp_blocking_connect failed Jun 15 20:52:14 localhost ser[21870]: ERROR: tcp_send: connect failed Jun 15 20:52:14 localhost ser[21870]: msg_send: ERROR: tcp_send failed Jun 15 20:52:14 localhost ser[21870]: ERROR: t_forward_nonack: sending request failed