THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#136 - tcp_async=yes breaks connect_timeout (no effect) and TCP reject detection User who did this - Iñaki Baz Castillo (ibc) ---------- I assume what is happening: When tcp_async=no, the worker itself open the TCP connection (which of course is bad as it gets blocked for a while) and can detect TCP failures or timeouts. When tcp_async=yes, the worker just sends the message to some TCP process and inmediately returns so can handle other TCP requests. Then it just expects a SIP response associated to the client transaction from the transactiin layer, and it's not aware of TCP rejection or timeouts. If I'm not wrong in the above, could the tcp_async=yes mode be improved so some worker is notified about TCP rejection or timeout? ---------- More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=136#comment2… You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.