27 Jul
2017
27 Jul
'17
2:37 p.m.
Ohh, misinterpreted tcp_no_connect=no is tcp_no_connect=0, which is the
default.
My other remark related to user location was for the case of
tcp_no_connect=yes, which I thought is what was meant initially.
Cheers,
Daniel
On 27.07.17 13:30, Daniel-Constantin Mierla wrote:
Hello,
do you have tcp_no_connect=no in your config? Because I think the
default value is 0.
It is useful when you have client behind the nat that closed the
connection, but the contact record is still valid in location table.
Cheers,
Daniel
On 27.07.17 13:09, Vik Killa wrote:
--
Daniel-Constantin Mierla
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training - www.asipto.com
Kamailio World Conference - www.kamailioworld.com
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?
Thanks
_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users(a)lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training - www.asipto.com
Kamailio World Conference - www.kamailioworld.com