sr-dev May 2022

sr-dev@lists.kamailio.org

12 participants
285 discussions

by Henning Westerholt

Module: kamailio Branch: master Commit: 5497d15766d25625b4704a3bd3e884ef2f1149da URL: https://github.com/kamailio/kamailio/commit/5497d15766d25625b4704a3bd3e884e… Author: Bastian Triller <bastian.triller(a)gmail.com> Committer: Henning Westerholt <hw(a)gilawa.com> Date: 2022-05-08T17:30:14+02:00 doc: Fix typos --- Modified: doc/misc/NEWS Modified: doc/tutorials/locking.txt --- Diff: https://github.com/kamailio/kamailio/commit/5497d15766d25625b4704a3bd3e884e… Patch: https://github.com/kamailio/kamailio/commit/5497d15766d25625b4704a3bd3e884e… --- diff --git a/doc/misc/NEWS b/doc/misc/NEWS index 9b62dd39c1..09b63a72b4 100644 --- a/doc/misc/NEWS +++ b/doc/misc/NEWS @@ -338,7 +338,7 @@ modules: the retransmissions which would otherwise be challenged). The major advantage is greatly enhanced security (extremely small probability of - a succesfull replay attack) combine with support + a successful replay attack) combine with support for cached credentials (if the UAs do support qop and auth) - nc_array_size - size of the array used for storing diff --git a/doc/tutorials/locking.txt b/doc/tutorials/locking.txt index 7507a5d002..3ff12f6c85 100644 --- a/doc/tutorials/locking.txt +++ b/doc/tutorials/locking.txt @@ -109,7 +109,7 @@ Locking & unlocking: void lock_get(gen_lock_t* lock); - lock (mutex down) void lock_release(gen_lock_t* lock); - unlock (mutex up) int lock_try(gen_lock_t* lock); - tries to lock and returns 0 - if succesfull, -1 if not (this is + if successful, -1 if not (this is a non-blocking lock_get()) @@ -164,7 +164,7 @@ Locking & unlocking: void lock_set_get(lock_set_t* s, int i); void lock_set_release(lock_set_t* s, int i); int lock_set_try(lock_set_t* s, int i); - tries to lock the i-th lock - from the set. If succesfull + from the set. If successful returns 0, if not -1. Example:

2 years, 7 months

git:master:543cd8f8: ipops: add dns container in dns_update_pv() if not created before

by Daniel-Constantin Mierla

Module: kamailio Branch: master Commit: 543cd8f897bc43d5fe1eb4c562d8351b32778209 URL: https://github.com/kamailio/kamailio/commit/543cd8f897bc43d5fe1eb4c562d8351… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: 2022-05-06T13:50:13+02:00 ipops: add dns container in dns_update_pv() if not created before - dns context creation relied on using the dns variable in some way, the main purpose of dns_update_pv() being to fill the variable, but one may want to use it for testing only --- Modified: src/modules/ipops/ipops_pv.c --- Diff: https://github.com/kamailio/kamailio/commit/543cd8f897bc43d5fe1eb4c562d8351… Patch: https://github.com/kamailio/kamailio/commit/543cd8f897bc43d5fe1eb4c562d8351… --- diff --git a/src/modules/ipops/ipops_pv.c b/src/modules/ipops/ipops_pv.c index 1afc806541..9ee6f5879a 100644 --- a/src/modules/ipops/ipops_pv.c +++ b/src/modules/ipops/ipops_pv.c @@ -373,7 +373,7 @@ int dns_update_pv(str *hostname, str *name) return -2; } - dr = sr_dns_get_item(name); + dr = sr_dns_add_item(name); if(dr==NULL) { LM_DBG("container not found: %s\n", name->s);

2 years, 7 months

git:master:0f9a833f: ipops: warning when too many dns containers are created

by Daniel-Constantin Mierla

Module: kamailio Branch: master Commit: 0f9a833fcc7cbc306a5d47413f6449ccc5a37f59 URL: https://github.com/kamailio/kamailio/commit/0f9a833fcc7cbc306a5d47413f6449c… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: 2022-05-06T12:46:28+02:00 ipops: warning when too many dns containers are created --- Modified: src/modules/ipops/ipops_pv.c --- Diff: https://github.com/kamailio/kamailio/commit/0f9a833fcc7cbc306a5d47413f6449c… Patch: https://github.com/kamailio/kamailio/commit/0f9a833fcc7cbc306a5d47413f6449c… --- diff --git a/src/modules/ipops/ipops_pv.c b/src/modules/ipops/ipops_pv.c index 6e9d86b5a6..1afc806541 100644 --- a/src/modules/ipops/ipops_pv.c +++ b/src/modules/ipops/ipops_pv.c @@ -95,6 +95,7 @@ sr_dns_item_t *sr_dns_add_item(str *name) { sr_dns_item_t *it = NULL; unsigned int hashid = 0; + int n = 0; hashid = get_hash1_raw(name->s, name->len); @@ -105,7 +106,13 @@ sr_dns_item_t *sr_dns_add_item(str *name) && strncmp(it->name.s, name->s, name->len)==0) return it; it = it->next; + n++; } + if(n > 20) { + LM_WARN("too many dns containers - adding nunmber %d - can fill memory\n", + n); + } + /* add new */ it = (sr_dns_item_t*)pkg_malloc(sizeof(sr_dns_item_t)); if(it==NULL)

2 years, 7 months

Re: [sr-dev] sr-dev Digest, Vol 162, Issue 61

by Luis Azedo

Hello, seeing some weirdness in kamailio logs while testing kamailio under docker/kubernetes and logging to stderr, not sure if its related to kamailio or the infrastructure itself. running in 8 core host, it looks like the write to stderr has some race condition if that's even possible. the breaks happen with different processes and i wonder if the LOG_FX and DPRINT_NON_CRIT macros are responsible for that. it looks like 2 different processes could evaluate to true and try to write to stderr at same time. two examples real output 116(354) INFO: 2022-04-28T18:08:14.476102048Z 3ebe6ff3-1799-4798-baa3-a109df32711d registrar-role.cfg:745 (route_to_external_aor) 117(355) INFO: 2022-04-28T18:08:14.473375226Z 5f2567bf-25bb-4cb1-a306-dc28711d9fcb default.cfg:305 (log_request) to sip:1117@1.sip-stress.com 117(355) INFO: 2022-04-28T18:08:14.476592352Z 5f2567bf-25bb-4cb1-a306-dc28711d9fcb default.cfg:324 (classify_source) end - routing to contact sip:1104@10.23.0.2:9181 originated from internal sources should be 116(354) INFO: 2022-04-28T18:08:14.476102048Z 3ebe6ff3-1799-4798-baa3-a109df32711d registrar-role.cfg:745 (route_to_external_aor) end - routing to contact sip:1104@10.23.0.2:9181 117(355) INFO: 2022-04-28T18:08:14.473375226Z 5f2567bf-25bb-4cb1-a306-dc28711d9fcb default.cfg:305 (log_request) to sip:1117@1.sip-stress.com 117(355) INFO: 2022-04-28T18:08:14.476592352Z 5f2567bf-25bb-4cb1-a306-dc28711d9fcb default.cfg:324 (classify_source) originated from internal sources second example real output 71(309) INFO: 2022-04-28T18:08:14.514892167Z cid-10440-3(a)10.21.0.1 default.cfg:304 (log_request) 116(354) INFO: 2022-04-28T18:08:14.521506921Z cid-10440-26(a)10.21.0.1 default.cfg:751 (internal_reply) 200 OK from sip:1002@1.sip-stress.com should be 71(309) INFO: 2022-04-28T18:08:14.514892167Z cid-10440-3(a)10.21.0.1 default.cfg:304 (log_request) from sip:1002@1.sip-stress.com 116(354) INFO: 2022-04-28T18:08:14.521506921Z cid-10440-26(a)10.21.0.1 default.cfg:751 (internal_reply) 200 OK Any hints/thoughts ? should we try to have a better way to handle this inb dprint.c/dprint.h ? Thanks

2 years, 7 months

[kamailio/kamailio] LCR function from_gw (Issue #3077)

by Antoineb2s

Hi, Kamailio 5.5.4 from deb packages I tried to use the lcr function from_gw(lcr_id[, ip_addr, proto]) I've declared several gws with different lcr_id Unfortunately from_gw doesn't work with lcr_ids > 1 For example : if (from_gw(2,$si,1)) { .... } ... ki_from_gw(): invalid lcr_id parameter value 2 -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3077 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3077(a)github.com>

2 years, 7 months

[kamailio/kamailio] htable Module Crash in Kamailio 5.5 (Issue #3082)

by surabhigarg

**Issue Description:** Kamailio is running with htable module having following parameter configuration: `modparam("htable", "htable", "flags=>size=6;dbtable=htable;autoexpire=0;dbmode=1") ` So, If there is an error in kamailio cfg then crash is observed in htable module. Here, I believe when kamailio goes to sync in memory htable content to the DB it crashes. **Troubleshooting** with dbmode=0 crash is not observed. **Steps to Reproduce** 1. Add entries in htable(DB) of mariadb. 2. Intentionally add some error in kamailio.cfg (i.e. remove colon at the end of any line) 3. start kamailio 4. kamailio wont come up as there is an error in kamailio.cfg 5. And while kamailio is shutting down there is a crash in htable 6. Now, check entries in htable(DB)of mariadb which gets empty **Kamailio Cfg** ``` modparam("htable", "htable", "flags=>size=6;dbtable=htable;autoexpire=0;dbmode=1") modparam("htable", "db_url", DBURL) # HTable Init event_route[htable:mod-init] { $sht(flags=>disable_sip_message_processing) = 0; xlog("L_INFO", "Init: disable_sip_message_processing $sht(flags=>disable_sip_message_processing)\n"); } ``` **Debugging Data:** ``` $ gdb /usr/local/kamailio-5.5/sbin/kamailio /tmp/core.kamailio.103011.N1VL-PA-SIP01.1649823318 GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-120.el7 Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /usr/local/kamailio-5.5/sbin/kamailio...done. warning: exec file is newer than core file. [New LWP 103011] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `/usr/local/kamailio-5.5/sbin/kamailio -D -P /run/kamailio/kamailio.pid -f /usr/'. Program terminated with signal 11, Segmentation fault. #0 0x00007f5b54995755 in atomic_get (v=0x14) at ../../core/mem/../atomic/atomic_common.h:66 66 return atomic_get_int(&(v->val)); Missing separate debuginfos, use: debuginfo-install glibc-2.17-324.el7_9.x86_64 keyutils-libs-1.5.8-3.el7.x86_64 krb5-libs-1.15.1-50.el7.x86_64 libcom_err-1.42.9-19.el7.x86_64 libgcc-4.8.5-44.el7.x86_64 libselinux-2.5-15.el7.x86_64 libstdc++-4.8.5-44.el7.x86_64 mariadb-libs-5.5.68-1.el7.x86_64 openssl-libs-1.0.2k-21.el7_9.x86_64 pcre-8.32-17.el7.x86_64 zlib-1.2.7-19.el7_9.x86_64 (gdb) bt full #0 0x00007f5b54995755 in atomic_get (v=0x14) at ../../core/mem/../atomic/atomic_common.h:66 No locals. #1 0x00007f5b54996d51 in ht_slot_lock (ht=0x7f5b504de738, idx=0) at ht_api.c:153 mypid = 103011 #2 0x00007f5b5498e3fb in ht_db_save_table (ht=0x7f5b504de738, dbtable=0x7f5b504de750) at ht_db.c:577 db_cols = {0x7f5b54bd83f0 <ht_db_name_column>, 0x7f5b54bd8400 <ht_db_ktype_column>, 0x7f5b54bd8410 <ht_db_vtype_column>, 0x7f5b54bd8420 <ht_db_value_column>, 0x7f5b54bd8430 <ht_db_expires_column>} db_vals = {{type = 8527368, nul = 0, free = 6, val = {int_val = -874111776, ll_val = 140723729341664, double_val = 6.9526760222378001e-310, time_val = 140723729341664, string_val = 0x7ffccbe61ce0 "\300\035\346\313\374\177", str_val = {s = 0x7ffccbe61ce0 "\300\035\346\313\374\177", len = 1532402903}, blob_val = { s = 0x7ffccbe61ce0 "\300\035\346\313\374\177", len = 1532402903}, bitmap_val = 3420855520, uint_val = 3420855520, ull_val = 140723729341664}}, { type = 1532380141, nul = 32603, free = 6, val = {int_val = 0, ll_val = 0, double_val = 0, time_val = 0, string_val = 0x0, str_val = {s = 0x0, len = 0}, blob_val = { s = 0x0, len = 0}, bitmap_val = 0, uint_val = 0, ull_val = 0}}, {type = DB1_INT, nul = 0, free = 1535278736, val = {int_val = -874111552, ll_val = 140723729341888, double_val = 6.9526760222488671e-310, time_val = 140723729341888, string_val = 0x7ffccbe61dc0 "\260\036\346\313\374\177", str_val = { s = 0x7ffccbe61dc0 "\260\036\346\313\374\177", len = 1419312224}, blob_val = {s = 0x7ffccbe61dc0 "\260\036\346\313\374\177", len = 1419312224}, bitmap_val = 3420855744, uint_val = 3420855744, ull_val = 140723729341888}}, {type = 1532429419, nul = 32603, free = 48, val = {int_val = -874111488, ll_val = 140723729341952, double_val = 6.9526760222520291e-310, time_val = 140723729341952, string_val = 0x7ffccbe61e00 "\260\036\346\313\374\177", str_val = { s = 0x7ffccbe61e00 "\260\036\346\313\374\177", len = -874111728}, blob_val = {s = 0x7ffccbe61e00 "\260\036\346\313\374\177", len = -874111728}, bitmap_val = 3420855808, uint_val = 3420855808, ull_val = 140723729341952}}, {type = 1544071712, nul = 32603, free = 8527368, val = {int_val = 8527368, ll_val = 8527368, double_val = 4.2130795782459789e-317, time_val = 8527368, string_val = 0x821e08 "DEBUG", str_val = {s = 0x821e08 "DEBUG", len = 0}, blob_val = { s = 0x821e08 "DEBUG", len = 0}, bitmap_val = 8527368, uint_val = 8527368, ull_val = 8527368}}} it = 0x0 tmp = {s = 0x7f5b549cdfcb "lid parameters\n", len = 1544071712} i = 0 now = 1649823318 ncols = 3 __FUNCTION__ = "ht_db_save_table" #3 0x00007f5b549a3c7d in ht_db_sync_tables () at ht_api.c:1078 ht = 0x7f5b504de738 __FUNCTION__ = "ht_db_sync_tables" #4 0x00007f5b549ac4cc in destroy () at htable.c:321 No locals. #5 0x0000000000590523 in destroy_modules () at core/sr_module.c:839 t = 0x7f5b5b83bd08 foo = 0x7f5b5b83b520 __FUNCTION__ = "destroy_modules" #6 0x000000000041d7da in cleanup (show_status=0) at main.c:575 memlog = 0 __FUNCTION__ = "cleanup" #7 0x000000000041f0b5 in shutdown_children (sig=15, show_status=0) at main.c:718 __FUNCTION__ = "shutdown_children" #8 0x0000000000436825 in main (argc=12, argv=0x7ffccbe62688) at main.c:3068 cfg_stream = 0xba2050 c = -1 r = 0 ---Type <return> to continue, or q <return> to quit--- tmp = 0x7ffccbe6466c "" tmp_len = 1408 port = 896 proto = 32603 ahost = 0x0 aport = 0 options = 0x7df0f8 ":f:cm:M:dVIhEeb:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:x:X:Y:" ret = -1 seed = 513568880 rfd = 4 debug_save = 0 debug_flag = 0 dont_fork_cnt = 0 n_lst = 0x7ffccbe62540 p = 0xf0b5ff <Address 0xf0b5ff out of bounds> st = {st_dev = 0, st_ino = 0, st_nlink = 0, st_mode = 0, st_uid = 0, st_gid = 0, __pad0 = 0, st_rdev = 0, st_size = 0, st_blksize = 0, st_blocks = 0, st_atim = { tv_sec = 0, tv_nsec = 0}, st_mtim = {tv_sec = 0, tv_nsec = 0}, st_ctim = {tv_sec = 0, tv_nsec = 0}, __unused = {0, 0, 0}} tbuf = '\000' <repeats 392 times>... option_index = 0 long_options = {{name = 0x7e150f "help", has_arg = 0, flag = 0x0, val = 104}, {name = 0x7dc584 "version", has_arg = 0, flag = 0x0, val = 118}, {name = 0x7e1514 "alias", has_arg = 1, flag = 0x0, val = 1024}, {name = 0x7e151a "subst", has_arg = 1, flag = 0x0, val = 1025}, {name = 0x7e1520 "substdef", has_arg = 1, flag = 0x0, val = 1026}, {name = 0x7e1529 "substdefs", has_arg = 1, flag = 0x0, val = 1027}, {name = 0x7e1533 "server-id", has_arg = 1, flag = 0x0, val = 1028}, { name = 0x7e153d "loadmodule", has_arg = 1, flag = 0x0, val = 1029}, {name = 0x7e1548 "modparam", has_arg = 1, flag = 0x0, val = 1030}, { name = 0x7e1551 "log-engine", has_arg = 1, flag = 0x0, val = 1031}, {name = 0x7e155c "debug", has_arg = 1, flag = 0x0, val = 1032}, {name = 0x7e1562 "cfg-print", has_arg = 0, flag = 0x0, val = 1033}, {name = 0x7e156c "atexit", has_arg = 1, flag = 0x0, val = 1034}, {name = 0x0, has_arg = 0, flag = 0x0, val = 0}} __FUNCTION__ = "main" (gdb) ``` **Additional Information** - Kamailio Version: ``` [root@N1VL-PA-SIP01 kamailio]# /usr/local/kamailio-5.5/sbin/kamailio -V version: kamailio 5.5.2 (x86_64/linux) e5f5a8 flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLOCKLIST, HAVE_RESOLV_RES ADAPTIVE_WAIT_LOOPS 1024, MAX_RECV_BUFFER_SIZE 262144, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: e5f5a8 compiled on 19:07:54 Apr 12 2022 with gcc 4.8.5 ``` - Operating System: ``` $ cat /etc/os-release NAME="Red Hat Enterprise Linux Server" VERSION="7.9 (Maipo)" ID="rhel" ID_LIKE="fedora" VARIANT="Server" VARIANT_ID="server" VERSION_ID="7.9" PRETTY_NAME="Red Hat Enterprise Linux Server 7.9 (Maipo)" ANSI_COLOR="0;31" CPE_NAME="cpe:/o:redhat:enterprise_linux:7.9:GA:server" HOME_URL="https://www.redhat.com/" BUG_REPORT_URL="https://bugzilla.redhat.com/" REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 7" REDHAT_BUGZILLA_PRODUCT_VERSION=7.9 REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux" REDHAT_SUPPORT_PRODUCT_VERSION="7.9" ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3082 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3082(a)github.com>

2 years, 7 months

git:master:33228bba: db_berkeley: reset lkey to avoid double free

by Daniel-Constantin Mierla

Module: kamailio Branch: master Commit: 33228bba33a6ea2e2d9a7acd9a240929223b9d39 URL: https://github.com/kamailio/kamailio/commit/33228bba33a6ea2e2d9a7acd9a24092… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: 2022-05-05T19:52:11+02:00 db_berkeley: reset lkey to avoid double free --- Modified: src/modules/db_berkeley/db_berkeley.c --- Diff: https://github.com/kamailio/kamailio/commit/33228bba33a6ea2e2d9a7acd9a24092… Patch: https://github.com/kamailio/kamailio/commit/33228bba33a6ea2e2d9a7acd9a24092… --- diff --git a/src/modules/db_berkeley/db_berkeley.c b/src/modules/db_berkeley/db_berkeley.c index 80c9aefac0..a8fe812c50 100644 --- a/src/modules/db_berkeley/db_berkeley.c +++ b/src/modules/db_berkeley/db_berkeley.c @@ -1055,8 +1055,10 @@ int bdb_update(db1_con_t *_con, db_key_t *_k, db_op_t *_op, db_val_t *_v, goto cleanup; } - if(lkey) + if(lkey) { pkg_free(lkey); + lkey = NULL; + } key.data = kbuf; key.ulen = MAX_ROW_SIZE;

2 years, 7 months

git:5.6:532cef75: pkg/kamailio/deb: version set 5.6.0~rc0 [skip ci]

by Victor Seva

Module: kamailio Branch: 5.6 Commit: 532cef75a2fda7725e869776fe8faa83ded33dd3 URL: https://github.com/kamailio/kamailio/commit/532cef75a2fda7725e869776fe8faa8… Author: Victor Seva <linuxmaniac(a)torreviejawireless.org> Committer: Victor Seva <linuxmaniac(a)torreviejawireless.org> Date: 2022-05-05T12:53:05+02:00 pkg/kamailio/deb: version set 5.6.0~rc0 [skip ci] --- Modified: pkg/kamailio/deb/bionic/changelog Modified: pkg/kamailio/deb/bookworm/changelog Modified: pkg/kamailio/deb/bullseye/changelog Modified: pkg/kamailio/deb/buster/changelog Modified: pkg/kamailio/deb/debian/changelog Modified: pkg/kamailio/deb/focal/changelog Modified: pkg/kamailio/deb/jessie/changelog Modified: pkg/kamailio/deb/precise/changelog Modified: pkg/kamailio/deb/sid/changelog Modified: pkg/kamailio/deb/stretch/changelog Modified: pkg/kamailio/deb/trusty/changelog Modified: pkg/kamailio/deb/wheezy/changelog Modified: pkg/kamailio/deb/xenial/changelog --- Diff: https://github.com/kamailio/kamailio/commit/532cef75a2fda7725e869776fe8faa8… Patch: https://github.com/kamailio/kamailio/commit/532cef75a2fda7725e869776fe8faa8…

2 years, 7 months

git:master:e310166a: pkg/kamailio/deb: version set 5.7.0~dev0 [skip ci]

by Victor Seva

Module: kamailio Branch: master Commit: e310166a5c0c7d419e036315c1d105278db51e58 URL: https://github.com/kamailio/kamailio/commit/e310166a5c0c7d419e036315c1d1052… Author: Victor Seva <linuxmaniac(a)torreviejawireless.org> Committer: Victor Seva <linuxmaniac(a)torreviejawireless.org> Date: 2022-05-05T12:50:41+02:00 pkg/kamailio/deb: version set 5.7.0~dev0 [skip ci] --- Modified: pkg/kamailio/deb/bionic/changelog Modified: pkg/kamailio/deb/bookworm/changelog Modified: pkg/kamailio/deb/bullseye/changelog Modified: pkg/kamailio/deb/buster/changelog Modified: pkg/kamailio/deb/debian/changelog Modified: pkg/kamailio/deb/focal/changelog Modified: pkg/kamailio/deb/jessie/changelog Modified: pkg/kamailio/deb/precise/changelog Modified: pkg/kamailio/deb/sid/changelog Modified: pkg/kamailio/deb/stretch/changelog Modified: pkg/kamailio/deb/trusty/changelog Modified: pkg/kamailio/deb/wheezy/changelog Modified: pkg/kamailio/deb/xenial/changelog --- Diff: https://github.com/kamailio/kamailio/commit/e310166a5c0c7d419e036315c1d1052… Patch: https://github.com/kamailio/kamailio/commit/e310166a5c0c7d419e036315c1d1052…

2 years, 7 months

Development is open for future release of v5.7.x series

by Daniel-Constantin Mierla

Hello, the branch 5.6 was created, therefore the master branch is open for adding new features, to be part of future release series v5.7.x (or whatever version is decided for next series). Any bug fix committed to master that applies to 5.6.x or older stable branches should be backported as usual with "git cherry-pick -x ..." to appropriate branches like 5.6 or 5.5. Expect that v5.6.0 will be released in a few weeks from now. Based on the workflow used during the past years, the next future release v5.7.0 should be out after another 6-10 months of development, plus 1-2 months of testing, so sometime by end of 2022 or in the first part of 2023. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - Online * https://www.asipto.com/sw/kamailio-advanced-training-online/

2 years, 7 months

← Newer
1
...
22
23
24
25
26
27
28
29
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev May 2022