Adrian Georgescu schrieb:
> This is why we talk about new design. Exactly for this reason.
> 
> Just disable TCP in the server configuration, no xSER variant can work 
> reliable with TCP today because of the blocking design.

FYI: ser 2.0 supports asynch TCP connection setup and sending - but I 
have not tried it yet

regards
klaus


> 
> Adrian
> 
> 
> On Jan 12, 2009, at 6:50 PM, Iñaki Baz Castillo wrote:
> 
>> 2009/1/12 Adrian Georgescu <[email protected] 
>> <mailto:[email protected]>>:
>>> Use UDP transport, it works reliable.
>>
>> Ops, does it mean that UDP is more suitable in a SIP proxy/server than 
>> TCP?
>> I really would like SIP to migrate to TCP asap.
>>
>> So, if OpenSIPS tries to do a TCP connection and it takes some time
>> (some seconds) until a timeout occurs, then that process is unable to
>> handle other SIP requests. an attacker could send just 100 SIP request
>> with ";transport=TCP" in the RURI and a RURI host which drops the TCP
>> connections.
>> This would cause all the OpenSIPS TCP processes being blocked !! is it?
>>
>>
>> -- 
>> Iñaki Baz Castillo
>> <[email protected] <mailto:[email protected]>>
>> _______________________________________________
>> Users mailing list
>> [email protected] <mailto:[email protected]>
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Users mailing list
> [email protected]
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users

_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Reply via email to