<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7652.24">
<TITLE>Error with parallel forking and TCP </TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>Hello,<BR>
I have a problem with parallel forking and TCP when one connection isn't available and the inv_timeout expires.<BR>
I have two clients registered with the same username and transport=TCP.<BR>
If I make a call to this number when one of them is not reachable, the INVITE goes to the phone reachable, if the call timeout expires (fr_inv_timer_avp) Openser sends the CANCEL, but doesn't send anything to the caller.<BR>
The failure_route doesn't hit.<BR>
<BR>
There is also a delay between the t_relay and the forwarding of the packet TCP on the net (around 3 seconds). The TCP packet is forwarded to the available connection only after Openser detects the failure for the closed TCP connection (the INVITE goes on the net only after the message ERROR:tm:t_forward_nonack: sending request failed).<BR>
<BR>
This is the trace (debug level 3, Openser version 1.3.2):<BR>
<BR>
Jun 25 16:30:01 SAM-IP ser[23888]: R1 t_relay R-uri: <sip:10240@10.45.10.63:2054;transport=tcp;line=zdhv6xi4><BR>
Jun 25 16:30:01 SAM-IP ser[23888]: Branch route <sip:10240@10.45.10.63:2054;transport=tcp;line=zdhv6xi4> 1<BR>
Jun 25 16:30:01 SAM-IP ser[23888]: Branch route <sip:10240@10.45.10.36:5064;transport=tcp> 2<BR>
<BR>
Jun 25 16:30:04 SAM-IP ser[23888]: ERROR:core:tcp_blocking_connect: poll error: flags 18<BR>
Jun 25 16:30:04 SAM-IP ser[23888]: ERROR:core:tcp_blocking_connect: failed to retrieve SO_ERROR (113) No route to host<BR>
Jun 25 16:30:04 SAM-IP ser[23888]: ERROR:core:tcpconn_connect: tcp_blocking_connect failed<BR>
Jun 25 16:30:04 SAM-IP ser[23888]: ERROR:core:tcp_send: connect failed<BR>
Jun 25 16:30:04 SAM-IP ser[23888]: ERROR:tm:msg_send: tcp_send failed<BR>
Jun 25 16:30:04 SAM-IP ser[23888]: ERROR:tm:t_forward_nonack: sending request failed<BR>
<BR>
Jun 25 16:30:04 SAM-IP ser[23890]: Reply Route: provision 180 - Ringing ip <10.45.10.36:33109> From <sip:10242@10.45.8.249> To <sip:10240@10.45.8.249><BR>
Jun 25 16:30:04 SAM-IP ser[23890]: ERROR:core:io_wait_loop_sigio_rt: ignoring event 41 on fd 24 (fm->fd=-1, fm->data=0x406e5488)<BR>
Jun 25 16:30:04 SAM-IP ser[23900]: ERROR:core:io_wait_loop_sigio_rt: ignoring event 41 on fd 25 (fm->fd=-1, fm->data=0x406c5258)<BR>
Jun 25 16:30:11 SAM-IP ser[23889]: Reply Route: 487 - <Request Terminated> ip <10.45.10.36:33110> From <sip:10242@10.45.8.249> To <sip:10240@10.45.8.249><BR>
Jun 25 16:30:11 SAM-IP ser[23890]: ERROR:core:io_wait_loop_sigio_rt: ignoring event 41 on fd 24 (fm->fd=-1, fm->data=0x406d5370)<BR>
Jun 25 16:30:11 SAM-IP ser[23891]: ERROR:core:tcp_read: error reading: Connection reset by peer<BR>
Jun 25 16:30:11 SAM-IP ser[23891]: ERROR:core:tcp_read_req: failed to read<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML><pre>**********************************************************************
The information in this message is confidential and may be legally
privileged. It is intended solely for the addressee. Access to this message
by anyone else is unauthorized. If you are not the intended recipient, any
disclosure, copying, or distribution of the message, or any action or
omission taken by you in reliance on it, is prohibited and may be unlawful.
Please immediately contact the sender if you have received this message inerror.
**********************************************************************</pre>