sr-dev January 2016

sr-dev@lists.kamailio.org

34 participants
295 discussions

[kamailio] fixed correlation_id (#474)
by Alexandr Dubovikov 08 Jan '16

08 Jan '16

You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/474 -- Commit Summary -- * fixed correlation_id -- File Changes -- M modules/sipcapture/hep.c (2) -- Patch Links -- https://github.com/kamailio/kamailio/pull/474.patch https://github.com/kamailio/kamailio/pull/474.diff --- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/474

1 1

[kamailio] fixed correlation_id issue. (#472)
by Alexandr Dubovikov 08 Jan '16

08 Jan '16

patch fix the issue with uninitialized correlation_id. You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/472 -- Commit Summary -- * fixed correlation_id issue. -- File Changes -- M modules/sipcapture/hep.c (2) -- Patch Links -- https://github.com/kamailio/kamailio/pull/472.patch https://github.com/kamailio/kamailio/pull/472.diff --- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/472

1 1

Panning next major release - v4.4
by Daniel-Constantin Mierla 08 Jan '16

08 Jan '16

Hello, sketching the road to the next major release, so people can plan their goals for it and discuss, if needed, before the start of winter holidays: - development freezing by end of January 2016 - test for one to one and a half month - release in the first part of March 2016 If there are important topics to decide on, we can organize an IRC meeting sometime in January 2016. Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Book: SIP Routing With Kamailio - http://www.asipto.com http://miconda.eu

3 5

git:master:46d3a3ef: db_text: fix bug in raw query where clause
by lazedo 08 Jan '16

08 Jan '16

Module: kamailio Branch: master Commit: 46d3a3ef2314f3177d64beab466401104d3ff887 URL: https://github.com/kamailio/kamailio/commit/46d3a3ef2314f3177d64beab4664011… Author: lazedo <luis.azedo(a)factorlusitano.com> Committer: lazedo <luis.azedo(a)factorlusitano.com> Date: 2016-01-08T02:52:04Z db_text: fix bug in raw query where clause wrong type was allocated --- Modified: modules/db_text/dbt_raw_util.c --- Diff: https://github.com/kamailio/kamailio/commit/46d3a3ef2314f3177d64beab4664011… Patch: https://github.com/kamailio/kamailio/commit/46d3a3ef2314f3177d64beab4664011… --- diff --git a/modules/db_text/dbt_raw_util.c b/modules/db_text/dbt_raw_util.c index ffbfa3b..9b0e2d7 100644 --- a/modules/db_text/dbt_raw_util.c +++ b/modules/db_text/dbt_raw_util.c @@ -216,7 +216,7 @@ int dbt_build_where(char* where, db_key_t** _k, db_op_t** _o, db_val_t** _v) // needs changes in dbt_query / dbt_row_match l = matches[2].rm_eo - matches[2].rm_so; - _k1[idx] = pkg_malloc(sizeof(db_key_t)); + _k1[idx] = pkg_malloc(sizeof(str)); _k1[idx]->len = l; _k1[idx]->s = pkg_malloc(sizeof(char) * (l+1)); strncpy(_k1[idx]->s, buffer+matches[2].rm_so, l);

1 0

Fosdem 2016
by Daniel-Constantin Mierla 07 Jan '16

07 Jan '16

Hello, anyone going to Fosdem? If no unexpected weather conditions messing the transport system, I am going to be there. It would be good to know who else we can meet there. If there are enough people interested, we can try organizing a social event (dinner/drinks) on Saturday evening. Last year we did it together with Jitsi team, but they are not coming this year. Perhaps there are other folks around the RTC dev room we can ask. On the other hand, it is harder to find a place if it is a large group, even harder to put all together if there are different groups/coordinators. Also, it is not easy to discuss withing a large group, as typically for a dinner we were seated to tables. Therefore organizing for a smaller group just for Kamailio friends could be a good alternative. Let's see first the number of participant and the level of interest for various options. This being an announcement, was crossposted to few mailing lists, but as most of the people are on sr-users, I think it would be good to reply and follow up on this discussion only there. Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Book: SIP Routing With Kamailio - http://www.asipto.com http://miconda.eu

3 2

Authentication failed, stale nonce
by Peter Villeneuve 07 Jan '16

07 Jan '16

Hi all, I'm getting sporadic stale nonce messages in spce which prevent the UAs from registering. I see in spce logs this: proxy[20381]: NOTICE: <script>: Authentication failed, stale nonce And in the UA clients' logs I see these error messages: First response from SPCE is "SIP/2.0 100 Trying", then "SIP/2.0 403 Try again later" and then after the UA resends the proper creds I'm getting "SIP/2.0 401 Unauthorized". After a few minutes (10 I think) the UA is able to register OK. My question is why am I getting these stale nonce error messages and how can I fix it? Thanks, Peter

1 1

git:master:53263a2d: tm: Reset socket variable while forking
by Hugh Waite 07 Jan '16

07 Jan '16

Module: kamailio Branch: master Commit: 53263a2ddad9bb118763516bcd7995652c4fb070 URL: https://github.com/kamailio/kamailio/commit/53263a2ddad9bb118763516bcd79956… Author: Hugh Waite <hugh.waite(a)xura.com> Committer: Hugh Waite <hugh.waite(a)xura.com> Date: 2016-01-07T12:17:03Z tm: Reset socket variable while forking - Reset sock_str variable so values from previous forks are not stored in contact_flows AVP --- Modified: modules/tm/t_serial.c --- Diff: https://github.com/kamailio/kamailio/commit/53263a2ddad9bb118763516bcd79956… Patch: https://github.com/kamailio/kamailio/commit/53263a2ddad9bb118763516bcd79956… --- diff --git a/modules/tm/t_serial.c b/modules/tm/t_serial.c index b278924..2fb734f 100644 --- a/modules/tm/t_serial.c +++ b/modules/tm/t_serial.c @@ -626,6 +626,8 @@ int t_next_contacts(struct sip_msg* msg, char* key, char* value) } } else { sock = NULL; + sock_str.s = 0; + sock_str.len = 0; } vavp = xavp_get(&flags_name, xavp->val.v.xavp);

1 0

git:4.2:72774645: tm: Reset socket variable while forking
by Hugh Waite 07 Jan '16

07 Jan '16

Module: kamailio Branch: 4.2 Commit: 727746451baaf0a59225cbdf45474df6eaba2bcc URL: https://github.com/kamailio/kamailio/commit/727746451baaf0a59225cbdf45474df… Author: Hugh Waite <hugh.waite(a)xura.com> Committer: Hugh Waite <hugh.waite(a)xura.com> Date: 2016-01-07T12:21:51Z tm: Reset socket variable while forking - Reset sock_str variable so values from previous forks are not stored in contact_flows AVP (cherry picked from commit 53263a2ddad9bb118763516bcd7995652c4fb070) --- Modified: modules/tm/t_serial.c --- Diff: https://github.com/kamailio/kamailio/commit/727746451baaf0a59225cbdf45474df… Patch: https://github.com/kamailio/kamailio/commit/727746451baaf0a59225cbdf45474df… --- diff --git a/modules/tm/t_serial.c b/modules/tm/t_serial.c index 63d3bb7..12dc332 100644 --- a/modules/tm/t_serial.c +++ b/modules/tm/t_serial.c @@ -598,6 +598,8 @@ int t_next_contacts(struct sip_msg* msg, char* key, char* value) } } else { sock = NULL; + sock_str.s = 0; + sock_str.len = 0; } vavp = xavp_get(&flags_name, xavp->val.v.xavp);

1 0

git:4.3:e393ad5e: tm: Reset socket variable while forking
by Hugh Waite 07 Jan '16

07 Jan '16

Module: kamailio Branch: 4.3 Commit: e393ad5e9a7e52f830b4155a42a63eef6b0dc057 URL: https://github.com/kamailio/kamailio/commit/e393ad5e9a7e52f830b4155a42a63ee… Author: Hugh Waite <hugh.waite(a)xura.com> Committer: Hugh Waite <hugh.waite(a)xura.com> Date: 2016-01-07T12:19:18Z tm: Reset socket variable while forking - Reset sock_str variable so values from previous forks are not stored in contact_flows AVP (cherry picked from commit 53263a2ddad9bb118763516bcd7995652c4fb070) --- Modified: modules/tm/t_serial.c --- Diff: https://github.com/kamailio/kamailio/commit/e393ad5e9a7e52f830b4155a42a63ee… Patch: https://github.com/kamailio/kamailio/commit/e393ad5e9a7e52f830b4155a42a63ee… --- diff --git a/modules/tm/t_serial.c b/modules/tm/t_serial.c index b278924..2fb734f 100644 --- a/modules/tm/t_serial.c +++ b/modules/tm/t_serial.c @@ -626,6 +626,8 @@ int t_next_contacts(struct sip_msg* msg, char* key, char* value) } } else { sock = NULL; + sock_str.s = 0; + sock_str.len = 0; } vavp = xavp_get(&flags_name, xavp->val.v.xavp);

1 0

[kamailio] debugger: kamailio freezes when dynamically setting module level(using fifo/rpc), if the module level is not previously set in config file: ```modparam("debugger", "mod_level", "core=2")``` (#463)
by Stefan Mititelu 07 Jan '16

07 Jan '16

This **is not** happening when setting the module facility, for the above, same conditions. This **is** happening also before pull-request [1] using "kamcmd dbg.mod_level core 1". After some debugging I've noticed that this **is** happening when trying to set a level for a module name whose ```idx = hid&(_dbg_mod_table_size-1);``` is even number?! (i.e. module name "core" reduces to an even index); the idx is always in the range ```_dbg_mod_table_size-1``` as it should be. Trying to solve this, I commented the lock_get/release in ```dbg_set_mod_debug_level()``` and saw it's working; kamailio doesn't freeze anymore. Thus, I tried to refactor the locks in ```struct _dbg_mod_slot``` to be dynamically allocated/deallocated using lock_alloc()/destroy() without success. I'm out of ideas. Do you have any idea what might lead to this strange deadlock? [1] https://github.com/kamailio/kamailio/pull/462 --- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/463

2 7

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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev January 2016