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@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
Dmitry,
if you have a t_relay_xxx() and non of the branches succeeded, an error reply will be internally generated (statefully) "Unfortunately error on sending to next hop occurred". If at least one branches succeeded, no error will be reported in script. At a fist look, I would say that the internal reply doesn't trigger the failure route.....I still have to investigate some strange issues...give me some time..
regarding the second problem....I'm not sure what you mean by 2nd and 3rd attempt.... are this serial forks? or...can you explain a little bit?.. anyhow sounds like for some reasons time-out is internally generated and in this case failure route is triggered.
regards, bogdan
Dmitry Isakbayev wrote:
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 <mailto:isakdim@gmail.com> *To:* serusers@lists.iptel.org <mailto:serusers@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
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Bogdan,
Thank you for looking into the issues. In both cases I am doing serial forking. For the 1st attempt, I am setting on-failure route, rewriting uri, and calling t_relay. For the following attempts, I am setting on-failure route, appending one branch, and calling t_relay. Similar to the example described @ http://www.voip-info.org/tiki-index.php?page=SER+example+forking only all attempts are serial.
Thank You, Dmitry
----- Original Message ----- From: "Bogdan-Andrei Iancu" bogdan@voice-system.ro To: "Dmitry Isakbayev" isakdim@gmail.com Cc: serusers@lists.iptel.org; devel@openser.org Sent: Thursday, June 16, 2005 3:15 PM Subject: Re: [Serusers] Re: How to execute failure_route block on tcp connect failure.
Dmitry,
if you have a t_relay_xxx() and non of the branches succeeded, an error reply will be internally generated (statefully) "Unfortunately error on sending to next hop occurred". If at least one branches succeeded, no error will be reported in script. At a fist look, I would say that the internal reply doesn't trigger the failure route.....I still have to investigate some strange issues...give me some time..
regarding the second problem....I'm not sure what you mean by 2nd and 3rd attempt.... are this serial forks? or...can you explain a little bit?.. anyhow sounds like for some reasons time-out is internally generated and in this case failure route is triggered.
regards, bogdan
Dmitry Isakbayev wrote:
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 <mailto:isakdim@gmail.com> *To:* serusers@lists.iptel.org <mailto:serusers@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
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Bogdan,
Thank you for looking into the issues. In both cases I am doing serial forking. For the 1st attempt, I am setting on-failure route, rewriting uri, and calling t_relay. For the following attempts, I am setting on-failure route, appending one branch, and calling t_relay. Similar to the example described @ http://www.voip-info.org/tiki-index.php?page=SER+example+forking only all attempts are serial.
Thank You, Dmitry
----- Original Message ----- From: "Bogdan-Andrei Iancu" bogdan@voice-system.ro To: "Dmitry Isakbayev" isakdim@gmail.com Cc: serusers@lists.iptel.org; devel@openser.org Sent: Thursday, June 16, 2005 3:15 PM Subject: Re: [Serusers] Re: How to execute failure_route block on tcp connect failure.
Dmitry,
if you have a t_relay_xxx() and non of the branches succeeded, an error reply will be internally generated (statefully) "Unfortunately error on sending to next hop occurred". If at least one branches succeeded, no error will be reported in script. At a fist look, I would say that the internal reply doesn't trigger the failure route.....I still have to investigate some strange issues...give me some time..
regarding the second problem....I'm not sure what you mean by 2nd and 3rd attempt.... are this serial forks? or...can you explain a little bit?.. anyhow sounds like for some reasons time-out is internally generated and in this case failure route is triggered.
regards, bogdan
Dmitry Isakbayev wrote:
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 <mailto:isakdim@gmail.com> *To:* serusers@lists.iptel.org <mailto:serusers@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
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
-
Bogdan-Andrei Iancu -
Dmitry Isakbayev