Re: [sr-dev] [kamailio/kamailio] Segfault when trying to write to the DB when it can't (possibly on shutdown) (#1287)

Did it happen also when there was no reboot or no kamailio restart? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub:

Re: [sr-dev] [kamailio/kamailio] define flag_t as unsigned long (#1288)

My proposal is to change flag_t to unsigned long long after master is opened for new features. Then there is lots of time to fix code that might get broken. -- Juha -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub:

[sr-dev] git:master:9e5820f0: registrar: do not return 0 in some cases of failure for save()

Module: kamailio Branch: master Commit: 9e5820f0c98b86824fcafe128fbfe0d37173479a URL: https://github.com/kamailio/kamailio/commit/9e5820f0c98b86824fcafe128fbfe0d37173479a Author: Daniel-Constantin Mierla Committer: Daniel-Constantin Mierla Date:

[sr-dev] git:master:8ca3cede: tm: add RPC call tm.stats to documentation

Module: kamailio Branch: master Commit: 8ca3cede7429efb49efa2491ca733cf4e3fd8e16 URL: https://github.com/kamailio/kamailio/commit/8ca3cede7429efb49efa2491ca733cf4e3fd8e16 Author: Mikko Lehto Committer: Mikko Lehto Date: 2017-10-30T15:46:21+02:00 tm: add RPC

[sr-dev] git:master:e5b77a64: tm: fix documentation typos and changed or obsolete paths

Module: kamailio Branch: master Commit: e5b77a64f47dd103eebfe3dfe1208c050dd50a9d URL: https://github.com/kamailio/kamailio/commit/e5b77a64f47dd103eebfe3dfe1208c050dd50a9d Author: Mikko Lehto Committer: Mikko Lehto Date: 2017-10-30T15:46:04+02:00 tm: fix

[sr-dev] git:master:9ed210ad: auth|pua_reginfo: fix common documentation typo

Module: kamailio Branch: master Commit: 9ed210ad397d0ad36c020b960a799e918482765f URL: https://github.com/kamailio/kamailio/commit/9ed210ad397d0ad36c020b960a799e918482765f Author: Mikko Lehto Committer: Mikko Lehto Date: 2017-10-30T15:46:21+02:00

Re: [sr-dev] [kamailio/kamailio] Segfault when trying to write to the DB when it can't (possibly on shutdown) (#1287)

What is the order of loaded modules: registrar, usrloc, pua* and presence*? Wondering if a module alreadly destroyed its structures and another one tries to access... -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub:

Re: [sr-dev] [kamailio/kamailio] define flag_t as unsigned long (#1288)

I wish that changing a structure is something simple, but is not. The main constraint is having the config interpreter able to deal only with integer numbers as values (static or via variables), and flags field stay behind a variable. But there could be also memory alignment problems when

[sr-dev] git:master:1b38ad5e: modules: readme files regenerated - auth ... [skip ci]

Module: kamailio Branch: master Commit: 1b38ad5ea0a17ea63d0319919ebeceaa043d8e0f URL: https://github.com/kamailio/kamailio/commit/1b38ad5ea0a17ea63d0319919ebeceaa043d8e0f Author: Kamailio Dev Committer: Kamailio Dev Date:

[sr-dev] git:5.0:a6acbf20: registrar: do not return 0 in some cases of failure for save()

Module: kamailio Branch: 5.0 Commit: a6acbf20d943bec39d4e09b5e0b3fd3ca9a72966 URL: https://github.com/kamailio/kamailio/commit/a6acbf20d943bec39d4e09b5e0b3fd3ca9a72966 Author: Daniel-Constantin Mierla Committer: Daniel-Constantin Mierla Date:

Re: [sr-dev] [kamailio/kamailio] define flag_t as unsigned long (#1288)

This has implications on other parts, such as variables where they can be accessed and set via $mf (iirc). On the other hand, I don't think having a variable with different lengths is a good approach, because it can break easily config behaviour when moving from one server to another. It

Re: [sr-dev] [kamailio/kamailio] define flag_t as unsigned long (#1288)

Daniel-Constantin Mierla writes: > This has implications on other parts, such as variables where they can > be accessed and set via $mf (iirc). Other parts of the code should not assume anything about the actual length of flag_t. If they do, that code needs to be fixed. > As an alternative for

Re: [sr-dev] [kamailio/kamailio] Segfault when trying to write to the DB when it can't (possibly on shutdown) (#1287)

I have not seen this any other time than when Kamailio is shutting down or restarting. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub:

Re: [sr-dev] [kamailio/kamailio] nathelper: correct Contact received param (#1203)

After testing, I see that the contact header is malformed-- missing the `>` at the end, e.g.: add_rcv_param("1"); *Contact:

Re: [sr-dev] [kamailio/kamailio] Segfault when trying to write to the DB when it can't (possibly on shutdown) (#1287)

``` loadmodule "log_systemd.so" loadmodule "tls.so" loadmodule "db_postgres.so" loadmodule "jsonrpcs.so" loadmodule "kex.so" loadmodule "corex.so" loadmodule "tm.so" loadmodule "tmx.so" loadmodule "sl.so" loadmodule "rr.so" loadmodule "pv.so" loadmodule "maxfwd.so" loadmodule "usrloc.so"

[sr-dev] git:master:47f27315: cfg_rpc: cfg.list rpc command returns an array of string values

Module: kamailio Branch: master Commit: 47f2731503faf84b1e666753bcb2db03772224b4 URL: https://github.com/kamailio/kamailio/commit/47f2731503faf84b1e666753bcb2db03772224b4 Author: Daniel-Constantin Mierla Committer: Daniel-Constantin Mierla Date:

Re: [sr-dev] [kamailio/kamailio] nathelper: correct Contact received param (#1203)

I have run into this issue too. Thanks for the patch. -- 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/1203#issuecomment-340532685___

Re: [sr-dev] cherry pick to 5.0 branch

Hello, just did it, thanks for noticing it! Cheers, Daniel On 30.10.17 18:01, Vitaliy Aleksandrov wrote: > Hi kamailio dev team. > > Recently master branch accepted a patch that fixes usrloc mutexes usage. > Would be nice to see it backported to 5.0 branch. > > commit 

[sr-dev] git:5.0:7649fa6b: cfg_rpc: cfg.list rpc command returns an array of string values

Module: kamailio Branch: 5.0 Commit: 7649fa6b3b14426ace8b2ec63975d4274c296d67 URL: https://github.com/kamailio/kamailio/commit/7649fa6b3b14426ace8b2ec63975d4274c296d67 Author: Daniel-Constantin Mierla Committer: Daniel-Constantin Mierla Date:

Re: [sr-dev] RPC command for changing debug log level

On maandag 30 oktober 2017 18:23:09 CET Daniel-Constantin Mierla wrote: > On 30.10.17 18:14, Alex Hermann wrote: > > Now that MI is gone, how do i change the debug log level at run-time? > via rpc command cfg.seti exported by cfg_rpc module: > > kamctl rpc cfg.seti core debug VALUE Thanks. >

[sr-dev] git:master:c15249cd: msrp: functions exported to kemi framework

Module: kamailio Branch: master Commit: c15249cd9aa1756262d20636e5b12a3a1ebcf1b2 URL: https://github.com/kamailio/kamailio/commit/c15249cd9aa1756262d20636e5b12a3a1ebcf1b2 Author: Daniel-Constantin Mierla Committer: Daniel-Constantin Mierla Date:

[sr-dev] RPC command for changing debug log level

Hi, Now that MI is gone, how do i change the debug log level at run-time? I can't find an appropriate function in http://www.kamailio.org/docs/docbooks/ devel/rpc_list/rpc_list.html -- Alex Hermann ___ Kamailio (SER) - Development Mailing List

[sr-dev] git:5.0:a18cef3b: usrloc: fix usrloc slot lock in ul.dump rpc procedure

Module: kamailio Branch: 5.0 Commit: a18cef3bbcc80004d4e013cb7ce08c0b20d8fc8c URL: https://github.com/kamailio/kamailio/commit/a18cef3bbcc80004d4e013cb7ce08c0b20d8fc8c Author: Vitaliy Aleksandrov Committer: Daniel-Constantin Mierla Date: