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.comhttp://miconda.eu
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.comhttp://miconda.eu
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
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
