[SR-Users] why is tcp_no_connect disabled by default

[Juha Heinanen]

Vik Killa writes:

> I'm trying to understand the scenario when `tcp_no_connect` should ever be
> set to `no`.
> Kamailio comes with `tcp_no_connect=no` by default which means it will try
> (and seemingly always fail) to create an outbound tcp connection when a
> UAC's tcp connection is lost. This in-turn could start building up the tcp
> write queue and can be disastrous at scale.
> So why would this setting (`tcp_no_connect=no`) ever be useful?

For example, if K connects to another K over TCP and the connection does
not exists, it makes sense to create one.

-- Juha