- URL:
https://github.com/kamailio/kamailio/commit/d44cf2168b45ec24926ca9a4bc5d2558b2b85f8c
Author: Daniel-Constantin Mierla
Date: 2019-03-06T08:20:06+01:00
doc/tutorials/tcp_tunning: note about network buffers size
- they may need tunning when dealing with large data
(cherry picked from co
Module: kamailio
Branch: master
Commit: b6b91a6d517675e9891e83b57dcdf90d7db0673d
URL:
https://github.com/kamailio/kamailio/commit/b6b91a6d517675e9891e83b57dcdf90d7db0673d
Author: Daniel-Constantin Mierla
Committer: Daniel-Constantin Mierla
Date: 2019-03-06T08:16:59+01:00
rtjson: reuse r-uri if
Module: kamailio
Branch: master
Commit: 649687fd8dd5a3d9b6b04d75d4e0d129f14e91d6
URL:
https://github.com/kamailio/kamailio/commit/649687fd8dd5a3d9b6b04d75d4e0d129f14e91d6
Author: Daniel-Constantin Mierla
Committer: Daniel-Constantin Mierla
Date: 2019-03-06T08:16:59+01:00
rtjson: more debug mes
Module: kamailio
Branch: master
Commit: 138172a388bc8b23035a7a422b97fc0276ed1462
URL:
https://github.com/kamailio/kamailio/commit/138172a388bc8b23035a7a422b97fc0276ed1462
Author: Daniel-Constantin Mierla
Committer: Daniel-Constantin Mierla
Date: 2019-03-06T08:16:59+01:00
rtjson: user wrapper f
> Try by setting this core parameter:
>
> * https://www.kamailio.org/wiki/cookbooks/devel/core#tcp_linger2
Tried out just now with "tcp_linger2=5" and restarted Kamailio. No effect. Also
documentation say it for FIN_WAIT2 not for CLOSE_WAIT state.
--
You are receiving this because you are
Try by setting this core parameter:
* https://www.kamailio.org/wiki/cookbooks/devel/core#tcp_linger2
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/1881#issuecomment-469716054__
> I have see similar behavior on CentOS with default network initialization
> subsystem.
> After I reconfigured to use `systemd-networkd` instead default network
> initialization, then i not see more "CLOSE_WAIT".
>
> Could you reconfigure network using `systemd-networkd` and then retest.
Hey s
Hello,
failure_route was designed to work only for incoming requests that are
routed out, not for local generated requests. What you can do, is to
loop the local requests back to kamailio and then sending out.
Enabling failure route for local requests may require a lot of code
review, because of
Hi,
i have a use case where i need to use failure_route for local transactions
like this.
route[TIMER_ROUTE]
{
... do sql
while rows
t_uac_send ...
}
event_route[tm:local-request]
{
if this is my request
t_on_reply("MY_REPLY");
t_on_failure("MY_FAULT");
t_s
@lazedo pushed 1 commit.
5fad824a716e9a5ecece30e5ba5830d566e83743 tmx: use t_release_transaction for
t_drop
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://github.com/kamailio/kamailio/pull/1882/files/b4696169e8b464da01774b1e40af677f941c803b..5f
Pre-Submission Checklist
- [X] Commit message has the format required by CONTRIBUTING guide
- [X] Commits are split per component (core, individual modules, libs, utils,
...)
- [X] Each component has a single commit (if not, squash them into one commit)
- [X] No commits to README files
I have see similar behavior on CentOS with default network initialization
subsystem.
After I reconfigured to use `systemd-networkd` instead default network
initialization, then i not see more "CLOSE_WAIT".
Could you reconfigure network using `systemd-networkd` and then retest.
--
You are recei
### Description
On our setup with Kamailio 5.2.1 with users connected via TLS. i see frequently
TCP/TLS sessions remain in CLOSE_WAIT:
netstat -ntp |grep CLOSE
tcp 238 0 172.17.217.10:5061 xxx.xxx.xxx.218:52613
CLOSE_WAIT 117912/kamailio
tcp 4681 0 172.17.2
### Description
If an EVAPI client drops dead and silently closes its TCP connection, EVAPI is
not notified in an acceptable time frame. The default OS TCP keep-alive
parameters are generally far too long to be effective, and there is no way to
override these using module or runtime configurati
14 matches
Mail list logo
