<!--
Kamailio Project uses GitHub Issues only for bugs in the code or feature requests.
If you have questions about using Kamailio or related to its configuration file,
ask on sr-users mailing list:
* http://lists.sip-router.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.sip-router.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 you submit a feature request (or enhancement), you can delete the text of
the template and only add the description of what you would like to be added.
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).
-->
### Description
<!--
Explain what you did, what you expected to happen, and what actually happened.
-->
We are using lua base routing with app_lua. We are seeing that our memory-utilization on that system continuously getting increase. our route.lua will have all routing logic same as
https://github.com/kamailio/kamailio/blob/master/misc/examples/kemi/kamaili…
we are using following set of modules
loadmodule "tm.so"
loadmodule "rr.so"
loadmodule "pv.so"
loadmodule "tmx.so"
loadmodule "sl.so"
loadmodule "maxfwd.so"
loadmodule "nathelper.so"
loadmodule "textops.so"
loadmodule "siputils.so"
loadmodule "xlog.so"
loadmodule "sanity.so"
loadmodule "path.so"
loadmodule "jsonrpcs.so"
loadmodule "app_lua.so"
loadmodule "dispatcher.so"
loadmodule "json.so"
loadmodule "cfg_rpc.so"
loadmodule "ctl.so"
loadmodule "ipops.so"
loadmodule "http_async_client.so"
loadmodule "dialog.so"
# ----------------- setting module-specific parameters ---------------
# ----- rr params -----
# set next param to 1 to add value to ;lr param (helps with some UAs)
modparam("rr", "enable_full_lr", 0)
# do not append from tag to the RR (no need for this script)
modparam("rr", "append_fromtag", 1)
# ----- dispatcher params -----
modparam("dispatcher", "list_file", DISPATCHER_FILE)
modparam("dispatcher", "ds_probing_mode", 1)
modparam("dispatcher", "flags", 2)
modparam("dispatcher", "ds_ping_interval", 10)
modparam("dispatcher", "ds_ping_from", "sip:ping@test.com")
# ----- nathelper params ----
modparam("nathelper", "received_avp", "$avp(s:rcv)")
# ----- http_async_client -------
# ---- number of worker process for async req and res
modparam("http_async_client", "workers", 4)
# ----- ctl ------
modparam("ctl", "binrpc", "tcp:MY_IP_ADDR:2086")
# ----- app_lua params ----
modparam("app_lua", "reload", 1)
modparam("app_lua", "load", ROUTE_LUA)
# ---- dialog params ----
modparam("dialog", "enable_stats", 1)
modparam("dialog", "dlg_flag", 4)
modparam("dialog", "event_callback", "ksr_dialog_event")
cfgengine "lua"
### Troubleshooting
#### Reproduction
We can easily reproduce by loading app_lua with kamailio-basic-kemi-lua.lua
https://github.com/kamailio/kamailio/blob/master/misc/examples/kemi/kamaili…
<!--
If the issue can be reproduced, describe how it can be done.
-->
#### Debugging Data
root@ip-172-31-4-160:~# kamcmd -s tcp:172.31.4.160:2046 tm.stats
{
current: 2220
waiting: 2198
total: 6113169
total_local: 1371
rpl_received: 11958486
rpl_generated: 6111711
rpl_sent: 12224635
6xx: 0
5xx: 6104789
4xx: 6831
3xx: 0
2xx: 1483
created: 6113169
freed: 6110949
delayed_free: 0
}
transaction are getting free as they are created so no transaction memory leak.
<!--
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.
-->
```
U 54.183.198.87:5060 -> 172.31.4.160:5060
INVITE sip:919980950111@13.57.122.212:5060 SIP/2.0.
Record-Route: <sip:54.183.198.87;lr;ftag=2186327>.
Via: SIP/2.0/UDP 54.183.198.87:5060;branch=z9hG4bK62f3.22dfb9a43503cc12dafdcdbc9ab1e17d.0.
Via: SIP/2.0/UDP 172.31.13.202:5060;rport=5060;received=13.232.78.75;branch=z9hG4bK-20254-2186327-0.
From: <sip:919980950111@21979254854757081.zt.plivo.com>;tag=2186327.
To: <sip:919980950111@21979254854757081.zt.plivo.com>.
Call-ID: 2186327-20254(a)172.31.13.202.
CSeq: 1 INVITE.
Contact: <sip:sipp@13.126.252.148:5060;transport=UDP;alias=13.232.78.75~5060~1>.
Max-Forwards: 69.
User-Agent: Sipp/Linux.
Supported: replaces, outbound.
Content-Type: application/sdp.
Content-Length: 139.
X-ZT-Cust-IP: 13.232.78.75.
X-ZT-Trunk: 21979254854757081.zt.plivo.com.
.
v=0.
o=user1 53655765 2353687637 IN IP4 13.126.252.148.
s=-.
c=IN IP4 13.126.252.148.
t=0 0.
m=audio 6000 RTP/AVP 0.
a=rtpmap:0 PCMU/8000.
#
U 172.31.4.160:5060 -> 54.183.198.87:5060
SIP/2.0 100 trying -- your call is important to us.
Via: SIP/2.0/UDP 54.183.198.87:5060;branch=z9hG4bK62f3.22dfb9a43503cc12dafdcdbc9ab1e17d.0;rport=5060.
Via: SIP/2.0/UDP 172.31.13.202:5060;rport=5060;received=13.232.78.75;branch=z9hG4bK-20254-2186327-0.
From: <sip:919980950111@21979254854757081.zt.plivo.com>;tag=2186327.
To: <sip:919980950111@21979254854757081.zt.plivo.com>.
Call-ID: 2186327-20254(a)172.31.13.202.
CSeq: 1 INVITE.
Server: kamailio (5.1.3 (x86_64/linux)).
Content-Length: 0.
.
#
U 172.31.4.160:5060 -> 54.183.198.87:5060
SIP/2.0 408 Request Timeout.
Via: SIP/2.0/UDP 54.183.198.87:5060;branch=z9hG4bK223b.cd9c3cb1d2dc6adc346e6fb7acdee708.0;rport=5060.
Via: SIP/2.0/UDP 172.31.13.202:5060;rport=5060;received=13.232.78.75;branch=z9hG4bK-20254-2185727-0.
From: <sip:919980950111@21979254854757081.zt.plivo.com>;tag=2185727.
To: <sip:919980950111@21979254854757081.zt.plivo.com>;tag=c99e9820d9036d36e5541ff825b95248-8c22.
Call-ID: 2185727-20254(a)172.31.13.202.
CSeq: 1 INVITE.
Server: kamailio (5.1.3 (x86_64/linux)).
Content-Length: 0.
.
```
#### 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).
-->
```
Jun 29 19:18:14 ip-172-31-4-160 kamailio[8119]: ERROR: <core> [core/mem/q_malloc.c:287]: qm_find_free(): qm_find_free(0x7fe974b24000, 35992); Free fragment not found!
Jun 29 19:18:14 ip-172-31-4-160 kamailio[8119]: ERROR: <core> [core/mem/q_malloc.c:421]: qm_malloc(): qm_malloc(0x7fe974b24000, 35992) called from http_async_client: http_multi.c: curl_shm_calloc(346), module: http_async_client; Free fragment not found!
Jun 29 19:18:14 ip-172-31-4-160 kamailio[8119]: ERROR: http_async_client [http_multi.c:437]: new_request(): curl_easy_init() failed!
```
#### 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`)
-->
```
root@ip-172-31-4-160:/etc/kamailio# uname -a
Linux ip-172-31-4-160 3.13.0-143-generic #192-Ubuntu SMP Tue Feb 27 10:45:36 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
```
--
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/1577
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/1086
-- Commit Summary --
* pkg/kamailio: Fix of ticket 1085
-- File Changes --
M pkg/kamailio/centos/7/kamailio.service (2)
M pkg/kamailio/deb/debian/kamailio.service (2)
M pkg/kamailio/deb/jessie/kamailio.service (2)
M pkg/kamailio/deb/sid/kamailio.service (2)
M pkg/kamailio/deb/stretch/kamailio.service (2)
M pkg/kamailio/deb/xenial/kamailio.service (2)
M pkg/kamailio/fedora/17/kamailio.service (2)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/1086.patchhttps://github.com/kamailio/kamailio/pull/1086.diff
--
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/pull/1086
(Feature request)
be able to recover data from htable variable when kamailio starts, from another kamailio instances through dmq module.
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/260
Hello,
as it was discussed during our last IRC devel meeting before the summer,
the time to release a new major version should be this autumn.
With the Kamailio Developers Meeting planned for September 27-28, 2018,
I think it is better to freeze the code couple of days after that event.
So I propose the following milestones:
* on Thursday, October 4, 2018 - last development day, code for 5.2.0
will be frozen at the end of the day
* 4 to 6 weeks of testing
* release sometime in November, to be decided more precisely after the
first weeks of testing, some rough candidates being within the weeks of
Nov 5 or Nov 19
If anyone has something to add or adjust, let's discuss on sr-users
mailing list.
Cheers,
Daniel
--
Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference -- www.kamailioworld.com
Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com
Hello,
a matter of the schedule to be agreed in the morning and the
availability during the Kamailio Developers Meeting, we may do a new
stable release from branch 5.1.6 on Thursday, Sep 27, 2018, in the
afternoon. Given that several of us will be in the same room, the
special goal would be to try to automate the process as much as possible.
If the time doesn't allow it, then the release will be done next week, a
specific day to be decided by the end of this week.
Anyhow, this is the informal notification to report as soon as possible
any issues you are aware of and not yet in bug tracker, so they get a
chance to be fixed.
Cheers,
Daniel
--
Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference -- www.kamailioworld.com
Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com
#### 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 for modules
#### Type Of Change
- [X] New feature (non-breaking change which adds new functionality)
#### Checklist:
- [X] Tested changes locally
#### Description
Add PV $sdp(sess_version) for reading and writing SDP o= -line attribute sess-version.
Special integer value -1 increments current value.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/1659
-- Commit Summary --
* core: parse SDP origin line sess-version field
* sdpops: fetch and manipulate origin line sess-version through pseudo-variable
-- File Changes --
M src/core/parser/sdp/sdp.c (8)
M src/core/parser/sdp/sdp.h (1)
M src/core/parser/sdp/sdp_helpr_funcs.c (68)
M src/core/parser/sdp/sdp_helpr_funcs.h (1)
M src/modules/sdpops/sdpops_mod.c (168)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/1659.patchhttps://github.com/kamailio/kamailio/pull/1659.diff
--
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/pull/1659
I have one local module and updated its module interface to the new
one. Then I build K, started it and got a crash. I thought that it
must my mistake in the module interface update, but when I looked at the
core dump, it did point to another module:
(gdb) where
#0 0x00005643e66fd349 in register_module (e=0x7f494a5cb4a0 <exports>,
path=0x7f494ce1a9d0 "/usr/lib/x86_64-linux-gnu/sip-proxy/modules/cfg_rpc.so",
handle=0x5643e8151500) at core/sr_module.c:230
#1 0x00005643e670341d in load_module (mod_path=0x7f494ce1a930 "cfg_rpc")
at core/sr_module.c:567
#2 0x00005643e6918741 in yyparse () at core/cfg.y:1704
#3 0x00005643e65ca49e in main (argc=18, argv=0x7ffd36a27948) at main.c:2141
-- Juha
Module: kamailio
Branch: master
Commit: bf5be06f9b6b3ec6ad68c57f4075af5ba3aa23c4
URL: https://github.com/kamailio/kamailio/commit/bf5be06f9b6b3ec6ad68c57f4075af5…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2018-09-29T09:01:41+02:00
modules: readme files regenerated - tls ... [skip ci]
---
Modified: src/modules/tls/README
---
Diff: https://github.com/kamailio/kamailio/commit/bf5be06f9b6b3ec6ad68c57f4075af5…
Patch: https://github.com/kamailio/kamailio/commit/bf5be06f9b6b3ec6ad68c57f4075af5…
---
diff --git a/src/modules/tls/README b/src/modules/tls/README
index 3ea60f8949..20b08cfa4a 100644
--- a/src/modules/tls/README
+++ b/src/modules/tls/README
@@ -89,6 +89,8 @@ Olle E. Johansson
14.1. event_route[tls:connection-out]
+ 15. TLS With Database Backend
+
List of Examples
1.1. Quick Start Basic Config
@@ -210,6 +212,8 @@ Chapter 1. Admin Guide
14.1. event_route[tls:connection-out]
+ 15. TLS With Database Backend
+
1. Overview
This module implements the TLS transport for Kamailio using the OpenSSL
@@ -1550,3 +1554,32 @@ event_route[tls:connection-out] {
}
}
...
+
+15. TLS With Database Backend
+
+ The module does not connect to database to fetch the values for the TLS
+ profile attributes. However the 'kamcli' tool can generate the tls.cfg
+ from a database table. Once generated, the 'tls.cfg' can be reloaded
+ with an RPC command.
+
+ The kamcli tool can be found at https://github.com/kamailio/kamcli.
+
+ The schema to create the database table can be seen with the command:
+ "kamcli tls sqlprint". The default name for database table is 'tlscfg'.
+
+ The most of the column names matches the corresponding attribute names
+ from a TLS profile.
+
+ The profile id in 'tls.cfg' is generated from
+ '[profile_type:profile_name]'. The 'profile_type' has to be 'server' or
+ 'client'. The 'profile_name' can be 'default', 'any' or the pair of IP
+ address and port like 'ipaddr:port'.
+
+ The 'file_type' is specifying if the values for 'certificate',
+ 'private_key', 'ca_list' and 'crl' are path to files on disc (when is
+ set to 0) or the content of the files (when set to 1). If 'file_type'
+ is 1, then 'kamcli' will create new files on disc and store the values
+ from the database in them. The target folder for 'tls.cfg' and the
+ certificates related files can be set via command options for 'kamcli
+ tls', for more details see the output of 'kamcli tls --help' and
+ 'kamcli tls cfgprint --help'.