for the help.
From: Users [mailto:users-boun...@lists.opensips.org] On Behalf Of Liviu Chircu
Sent: Friday, January 19, 2018 7:16 AM
To: users@lists.opensips.org
Subject: Re: [OpenSIPS-Users] tcp_async timeouts confusion
Hi Steve,
I've opened a GitHub issue for this report so we can better keep track
.
Thanks,
steve
*From:*Users [mailto:users-boun...@lists.opensips.org] *On Behalf Of
*Steve Brisson
*Sent:* Thursday, January 11, 2018 11:56 AM
*To:* OpenSIPS users mailling list <users@lists.opensips.org>
*Subject:* Re: [OpenSIPS-Users] tcp_async timeouts confusion
TCP scenario
users@lists.opensips.org<mailto:users@lists.opensips.org>
Subject: Re: [OpenSIPS-Users] tcp_async timeouts confusion
Answers below,
On 09.01.2018 22:25, Steve Brisson wrote:
*** Using TCP ***
After the invite is sent to the vcs, tcpdump at the opensips server showed 100,
180, and 200
.@lists.opensips.org] On Behalf Of Liviu Chircu
Sent: Tuesday, January 9, 2018 3:20 AM
To: users@lists.opensips.org
Subject: Re: [OpenSIPS-Users] tcp_async timeouts confusion
Hi, Steve!
The transport layer was heavily refactored roughly three years ago, see [1],
[2] and [3] for the relevant
Hi, Steve!
The transport layer was heavily refactored roughly three years ago, see
[1], [2] and [3] for the relevant commits which, indeed, bumped the
default connect timeout down a lot, to a much lower value (10s ->
100ms). Although 100ms might seem unnecessary (it's async! let it sleep
as
Hi,
I've run into some issues related to tcp_async and tcp/tls timeouts since
upgrading opensips from v1.8 to v2.3.
Based on my v1.8 config, I had the tcp_connect_timeout set to 3 secs but this
gets ignored in v2.3 because tcp_async is enabled by default. As a result,
calls made from a local
