[Serdev] TCP Blocking Connect issue

Andrew Mee andrew at healthshare.net.au
Sun Aug 22 23:36:35 UTC 2004


The TCP connection is available on the UA, why would it not be on the 
SER, I have no idea...

Sorry I'll clarify, perhaps I have been unclear

There are no TCP issues with SER, we can make quite a lot of calls for 
hours on end no problem, until a client crashes.
this results in the following (see other emails for more depth):
11(14986) ERROR: tcp_read: error reading: Connection reset by peer
11(14986) ERROR: tcp_read_req: error reading
Ok, we now restart the client at both ends
 From this point in we have continual TCP issues that result in (see 
other email for more depth):
11(3048) ERROR: tcp_blocking_connect: SO_ERROR (111) Connection refused
11(3048) ERROR: tcpconn_connect: tcp_blocking_connect failed
11(3048) ERROR: tcp_send: connect failed
Now I then restart SER (and leave the clients running)
Relog the clients in again
And then we have no problems at all until the client crashes and then 
SER problems reoccur.
This is reproducible every time.

My theory is that the TCP connections in SER are not being cleaned up 
properly when they dropped from the client end.
This is SER 0.8.14 btw.

Thanks

Andrew

Jiri Kuthan wrote:

>My appologies -- I still don't understand what is wrong about not 
>sending packets to an unavailable TCP destination?
>
>-jiri
>
>At 01:08 AM 8/23/2004, Andrew Mee wrote:
>  
>
>>Please see the message titled " TCP Blocking Connect issue - further analysis" you will see it is definitely a problem with SER. So while the UA may cause it, the Proxy does not handle it well. This could be used as a DOS attack on any SER server using TCP. I am unsure yet if this is only in routed mode or all TCP modes.
>>
>>Andrew
>>
>>Jiri Kuthan wrote:
>>
>>    
>>
>>>I can't respond on th TCP parts with which I am not familiar but from what the error message tells I think it is not related to SER.
>>>It tells that a TCP connection was refused.
>>>
>>>-jiri
>>>
>>>At 12:40 AM 8/19/2004, Andrew Mee wrote:
>>>
>>>
>>>      
>>>
>>>>To fix this problem I have to restart SER.... Which is not what I want
>>>>to have to do obviously :)
>>>>I am using 0.8.14 on Gentoo.... any chance of fixing it?
>>>>
>>>>Andrew
>>>>
>>>>Jiri Kuthan wrote:
>>>>
>>>>  
>>>>
>>>>        
>>>>
>>>>>It appears to be an unresponsive TCP server downstream of SER.
>>>>>
>>>>>-jiri
>>>>>
>>>>>At 06:24 AM 8/18/2004, Andrew Mee wrote:
>>>>>
>>>>>
>>>>>    
>>>>>
>>>>>          
>>>>>
>>>>>>I get this in SER after the UA (yes the client :) crashes and I restart the client (and reboot the machine), then make a new invite...
>>>>>>
>>>>>>11(3048) check_via_address(192.168.2.11, 192.168.2.11, 0)
>>>>>>11(3048) Sending:
>>>>>>ACK sip:192.168.2.28:8727;transport=tcp SIP/2.0
>>>>>>Record-Route: <sip:test2 at 192.168.2.253;transport=tcp;ftag=d55c81a6d09346408fd6620a72401024;lr=on>
>>>>>>Via: SIP/2.0/TCP 192.168.2.253;branch=0;i=76
>>>>>>Via: SIP/2.0/TCP 192.168.2.11:9493
>>>>>>Max-Forwards: 69
>>>>>>From: "James West" <sip:support at 192.168.2.253>;tag=d55c81a6d09346408fd6620a72401024;epid=c001967d41
>>>>>>To: <sip:test2 at 192.168.2.253>;tag=01587e6c3efb47878b015161a575864b
>>>>>>Call-ID: 9c7f7f9b1b084b0bbf793be7fee2225d at 192.168.2.11
>>>>>>CSeq: 1 ACK
>>>>>>User-Agent: RTC/1.2
>>>>>>Content-Length: 0
>>>>>>.
>>>>>>11(3048) orig. len=501, new_len=528, proto=2
>>>>>>11(3048) tcp_send: no open tcp connection found, opening new one
>>>>>>11(3048) ERROR: tcp_blocking_connect: SO_ERROR (111) Connection refused
>>>>>>11(3048) ERROR: tcpconn_connect: tcp_blocking_connect failed
>>>>>>11(3048) ERROR: tcp_send: connect failed
>>>>>>11(3048) msg_send: ERROR: tcp_send failed
>>>>>>11(3048) Warning: sl_send_reply: I won't send a reply for ACK!!
>>>>>>11(3048) ERROR: sl_reply_error used: Unfortunately error on sending to next hop occured (477/SL)
>>>>>>11(3048) DEBUG:destroy_avp_list: destroing list (nil)
>>>>>>
>>>>>>I have yet to find out what is causing this in SER, but I thought maybe someone might have some more info.
>>>>>>I will in the meantime keep digging.
>>>>>>
>>>>>>-- Andrew Mee
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>_______________________________________________
>>>>>>Serdev mailing list
>>>>>>serdev at lists.iptel.org
>>>>>>http://lists.iptel.org/mailman/listinfo/serdev
>>>>>>
>>>>>>      
>>>>>>            
>>>>>>
>>>>>--
>>>>>Jiri Kuthan            http://iptel.org/~jiri/ 
>>>>>    
>>>>>          
>>>>>
>>>>-- Andrew Mee
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>_______________________________________________
>>>>Serdev mailing list
>>>>serdev at lists.iptel.org
>>>>http://lists.iptel.org/mailman/listinfo/serdev
>>>>  
>>>>        
>>>>
>>>--
>>>Jiri Kuthan            http://iptel.org/~jiri/ 
>>>
>>>      
>>>
>>_______________________________________________
>>Serdev mailing list
>>serdev at lists.iptel.org
>>http://lists.iptel.org/mailman/listinfo/serdev
>>    
>>
>
>--
>Jiri Kuthan            http://iptel.org/~jiri/ 
>
>  
>


-- 
Andrew Mee





More information about the Serdev mailing list