Module: kamailio
Branch: master
Commit: 38a696fff66f0a453e54c92c93e8c459a1b4e77d
URL: https://github.com/kamailio/kamailio/commit/38a696fff66f0a453e54c92c93e8c45…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2019-01-15T13:02:08+01:00
doc/tutorials/tcp_tunning: note about network buffers size
- they may need tunning when dealing with large data
---
Modified: doc/tutorials/tcp_tunning.txt
---
Diff: https://github.com/kamailio/kamailio/commit/38a696fff66f0a453e54c92c93e8c45…
Patch: https://github.com/kamailio/kamailio/commit/38a696fff66f0a453e54c92c93e8c45…
---
diff --git a/doc/tutorials/tcp_tunning.txt b/doc/tutorials/tcp_tunning.txt
index 39097d57b7..aca6a12449 100644
--- a/doc/tutorials/tcp_tunning.txt
+++ b/doc/tutorials/tcp_tunning.txt
@@ -19,22 +19,22 @@ For now it deals only with Linux specific optimizations.
net.core.somaxconn - limit of the listen() backlog, default 128
net.ipv4.tcp_max_syn_backlog - default 1024 or 128
-net.ipv4.tcp_timestamps - default on., should be on (along with
+net.ipv4.tcp_timestamps - default on., should be on (along with
tcp_tw_recycle and timestamp supporting
peers allows for fast connections rates)
-1.2 connection in close_wait
+1.2 Connection in close_wait
- Connection should stay as little as possible
- in close_wait to quickly free the fd/resources for new connections attempts
- WARNING: this could break normal TCP use, use it only if you know what you are
+ Connection should stay as little as possible
+ in close_wait to quickly free the fd/resources for new connections attempts
+ WARNING: this could break normal TCP use, use it only if you know what you are
doing
-
+
net.ipv4.tcp_max_tw_buckets - maximum number of timewait sockets
(the default seems to be ok)
net.ipv4.tcp_tw_recycle - enables fast time wait sockets recycling (default
off), should be enabled if you have lots of short
- lived connections
+ lived connections
WARNING: see the above warning
net.ipv4.tcp_tw_reuse - allows reusing of time-wait sockets (default off)
WARNING: see above
@@ -49,10 +49,26 @@ net.ipv4.ip_local_port_range - should be increased (e.g. 4096-65534)
1.4 Open file descriptors
fs.file-max - maximum number of fds that will be allocated
- (you probably need to increase it, default
+ (you probably need to increase it, default
depends on installed memory)
-1.5 other sysctl that might affect tcp connection rate or the maximum number
+1.5 Buffers size
+
+ When dealing with large data, check the values for network sockets buffers
+ to be sufficient, among them:
+
+net.core.rmem_max
+net.core.wmem_max
+net.core.rmem_default
+net.core.wmem_default
+net.ipv4.tcp_mem
+net.ipv4.tcp_rmem
+net.ipv4.tcp_wmem
+
+ Note: sysctl -w net.ipv4.route.flush=1 - enusre that immediatly subsequent
+ connections use the values
+
+1.6 Other sysctl that might affect tcp connection rate or the maximum number
of open connections
fs.epoll.max_user_instances - maximum number of devices - per user (2.6.27.8+)
<!--
Kamailio Project uses GitHub Issues only for bugs in the code or feature requests. Please use this template only for bug reports.
If you have questions about using Kamailio or related to its configuration file, ask on sr-users mailing list:
* http://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
If you have questions about developing extensions to Kamailio or its existing C code, ask on sr-dev mailing list:
* http://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev
Please try to fill this template as much as possible for any issue. It helps the developers to troubleshoot the issue.
If there is no content to be filled in a section, the entire section can be removed.
You can delete the comments from the template sections when filling.
You can delete next line and everything above before submitting (it is a comment).
-->
I am getting following error when ts_store() is called
Dec 21 12:50:57 ejabberd /usr/local/kamailio-5.1/sbin/kamailio[25676]: {1 2 INVITE 2d24732c962aa49859622eb9d214a115(a)192.168.2.7} DEBUG: tsilo [ts_store.c:80]: ts_store(): storing transaction 5967:208972607 for r-uri:
Dec 21 12:50:57 ejabberd /usr/local/kamailio-5.1/sbin/kamailio[25696]: DEBUG: <core> [core/tcp_main.c:3279]: handle_tcp_child(): dead tcp child 2 (pid 25676, no 19) (shutting down?)
Dec 21 12:50:57 ejabberd /usr/local/kamailio-5.1/sbin/kamailio[25696]: DEBUG: <core> [core/io_wait.h:602]: io_watch_del(): DBG: io_watch_del (0xa6cf40, 37, -1, 0x0) fd_no=37 called
Dec 21 12:50:57 ejabberd /usr/local/kamailio-5.1/sbin/kamailio[25696]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 34
Dec 21 12:50:57 ejabberd /usr/local/kamailio-5.1/sbin/kamailio[25696]: DEBUG: <core> [core/tcp_main.c:3512]: handle_ser_child(): dead child 19, pid 25676 (shutting down?)
<!--
Explain what you did, what you expected to happen, and what actually happened.
-->
```
if (lookup("location"))
{
xlog("L_INFO","PUSHASYNC: for new transaction [$T(id_index):$T(id_label)] $fU => $rU \n");
if(t_newtran()) {
xlog("L_INFO","PUSHASYNC: storing transaction [$T(id_index):$T(id_label)] fU=[$fU] => rU=[$rU] ru=[$ru] \n");
ts_store();
xlog("L_INFO","PUSHASYNC: stored transaction [$T(id_index):$T(id_label)] [$fU] => [$rU]\n");
}
$sht(vtp=>stored::$rU) = 1;
return;
}
```
### Troubleshooting
#### Reproduction
<!--
If the issue can be reproduced, describe how it can be done.
-->
#### Debugging Data
<!--
If you got a core dump, use gdb to extract troubleshooting data - full backtrace,
local variables and the list of the code at the issue location.
gdb /path/to/kamailio /path/to/corefile
bt full
info locals
list
If you are familiar with gdb, feel free to attach more of what you consider to
be relevant.
-->
```
(paste your debugging data here)
```
#### Log Messages
<!--
Check the syslog file and if there are relevant log messages printed by Kamailio, add them next, or attach to issue, or provide a link to download them (e.g., to a pastebin site).
-->
```
(paste your log messages here)
```
#### SIP Traffic
<!--
If the issue is exposed by processing specific SIP messages, grab them with ngrep or save in a pcap file, then add them next, or attach to issue, or provide a link to download them (e.g., to a pastebin site).
-->
```
(paste your sip traffic here)
```
### Possible Solutions
<!--
If you found a solution or workaround for the issue, describe it. Ideally, provide a pull request with a fix.
-->
### Additional Information
* **Kamailio Version** - output of `kamailio -v`
```
(paste your output here)
```
* **Operating System**:
<!--
Details about the operating system, the type: Linux (e.g.,: Debian 8.4, Ubuntu 16.04, CentOS 7.1, ...), MacOS, xBSD, Solaris, ...;
Kernel details (output of `uname -a`)
-->
```
(paste your output here)
```
--
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/1775
Module: kamailio
Branch: 5.2
Commit: 82d9703e619f765efcda8f37e45bfcfe4b22607e
URL: https://github.com/kamailio/kamailio/commit/82d9703e619f765efcda8f37e45bfcf…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2019-01-14T12:46:35+01:00
modules: readme files regenerated - modules ... [skip ci]
---
Modified: src/modules/dialog/README
Modified: src/modules/dispatcher/README
---
Diff: https://github.com/kamailio/kamailio/commit/82d9703e619f765efcda8f37e45bfcf…
Patch: https://github.com/kamailio/kamailio/commit/82d9703e619f765efcda8f37e45bfcf…
---
diff --git a/src/modules/dialog/README b/src/modules/dialog/README
index b1b63b8e30..05a1b531f8 100644
--- a/src/modules/dialog/README
+++ b/src/modules/dialog/README
@@ -426,9 +426,10 @@ Chapter 1. Admin Guide
2. How it works
- To create the dialog associated with an initial request, the flag
- “dlg_flag” (Section 6.4, “dlg_flag (integer)”) must be set before
- creating the corresponding transaction.
+ To create the dialog associated with an initial INVITE request, execute
+ the function “dlg_manage()” or set the flag specified by parameter
+ “dlg_flag” (Section 6.4, “dlg_flag (integer)”) before creating the
+ corresponding transaction.
The dialog is automatically destroyed when a “BYE” is received. In case
of no “BYE”, the dialog lifetime is controlled via the default timeout
@@ -611,6 +612,10 @@ modparam("dialog", "rr_param", "xyz")
Flag to be used for marking if a dialog should be constructed for the
current request (this make sense only for initial requests).
+ Note: it is not needed to set this parameter and its corresponding flag
+ for initial request in case the “dlg_manage()” function is used. In
+ other words, using “dlg_manage()” alone is enough.
+
Default value is “none”.
Example 1.4. Set dlg_flag parameter
diff --git a/src/modules/dispatcher/README b/src/modules/dispatcher/README
index 53a464d8ff..c788e393c8 100644
--- a/src/modules/dispatcher/README
+++ b/src/modules/dispatcher/README
@@ -697,10 +697,15 @@ Note
Controls what gateways are tested to see if they are reachable.
* Value 0: If set to 0, only the gateways with state PROBING are
tested. After a gateway is probed, the PROBING state is cleared in
- this mode.
+ this mode. This means that no probing will be executed at all only
+ if flag in config file is set to 8/PROBING (please check
+ destination list file syntaxis for more details), it will probe
+ only one time at startup or after dispatcher reload.
* Value 1: If set to 1, all gateways are tested. If set to 1 and
there is a failure of keepalive to an active gateway, then it is
- set to TRYING state.
+ set to TRYING state. This means that probing will be executed all
+ the time, but you can skip some servers with flag 4 in destination
+ list file, for example.
* Value 2: if set to 2, only gateways in inactive state with probing
mode set are tested.
* Value 3: If set to 3, any gateway with state PROBING is continually
@@ -1388,6 +1393,21 @@ kamcmd dispatcher.set_state ip 3 all
Example:
kamcmd dispatcher.list
+ ...
+DEST: {
+ URI: sip:192.168.0.1:5060
+ FLAGS: AP
+ PRIORITY: 12
+}
+ ...
+
+ FLAGS consist out of 2 letters. First letter describe status of
+ destination: A-active, I â inactive, T â trying, D â disabled.
+ Second letter might be P or X. P is for probing, so AP means
+ destination is active and it is tested by SIP options continuously. X
+ means that there are no probing or sip pinging. So AX means that
+ destination is assumed as active and it is not tested by SIP options.
+ DX respectively is disabled destination that is not tested, etc.
5.3. dispatcher.reload
Module: kamailio
Branch: 5.2
Commit: 57017b10d9a50385368324beb7eef9044d0b124a
URL: https://github.com/kamailio/kamailio/commit/57017b10d9a50385368324beb7eef90…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2019-01-14T12:30:18+01:00
presence: do not include presence.h in other header files
- it exports as extern the module parameter variables and other modules built on
top of presence can end up including this header file, overwriting
declaration of variables with same name
- renamed db_url to pres_db_url, this being a common variable name, to
avoid same situation with a mistaken include in the future
- GH #1809
(cherry picked from commit eb1bf9a69abad3d237c136750fe8cacea4cd0a31)
---
Modified: src/modules/presence/hash.h
Modified: src/modules/presence/presence.c
Modified: src/modules/presence/presence.h
Modified: src/modules/presence/presence_dmq.c
Modified: src/modules/presence/presence_dmq.h
Modified: src/modules/presence/presentity.h
Modified: src/modules/presence/subscribe.h
---
Diff: https://github.com/kamailio/kamailio/commit/57017b10d9a50385368324beb7eef90…
Patch: https://github.com/kamailio/kamailio/commit/57017b10d9a50385368324beb7eef90…
Module: kamailio
Branch: 5.2
Commit: e61ad10e62d427bd0a22e5621f798015630a1e3f
URL: https://github.com/kamailio/kamailio/commit/e61ad10e62d427bd0a22e5621f79801…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2019-01-14T12:29:19+01:00
dispatcher: docs - typo and indentation for the rpc flags paragraph
(cherry picked from commit 14b4d23a06fdc9b9f6b17781c50902beaff0cd94)
---
Modified: src/modules/dispatcher/doc/dispatcher_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/e61ad10e62d427bd0a22e5621f79801…
Patch: https://github.com/kamailio/kamailio/commit/e61ad10e62d427bd0a22e5621f79801…
---
diff --git a/src/modules/dispatcher/doc/dispatcher_admin.xml b/src/modules/dispatcher/doc/dispatcher_admin.xml
index c0a55b27ad..6092349cf7 100644
--- a/src/modules/dispatcher/doc/dispatcher_admin.xml
+++ b/src/modules/dispatcher/doc/dispatcher_admin.xml
@@ -1713,13 +1713,15 @@ DEST: {
}
...
</programlisting>
-<para>FLAGS consist out of 2 letters. First letter describe status of destination: A-active,
- I – inactive, T – trying, D – disabled. Second letter might be P or X. P is for probing,
- so AP means destination is active and it is tested by SIP options continuously.
- X means that there are no probing or sip pinging. So AX means that destination is assumed as active
- and it is not tested by SIP options. DX respectively is disabled destination what is not tested and etc.
-</para>
- </section>
+ <para>FLAGS consist out of 2 letters. First letter describe status of
+ destination: A-active, I – inactive, T – trying, D – disabled. Second
+ letter might be P or X. P is for probing, so AP means destination
+ is active and it is tested by SIP options continuously. X means that
+ there are no probing or sip pinging. So AX means that destination is
+ assumed as active and it is not tested by SIP options. DX
+ respectively is disabled destination that is not tested, etc.
+ </para>
+ </section>
<section id="dispatcher.r.reload">
<title>
<function moreinfo="none">dispatcher.reload</function>