THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - Hugh Waite (hugh.waite)
Attached to Project - sip-router
Summary - Crash in kamailio core - timeout on forked destinations
Task Type - Bug Report
Category - Core
Status - Unconfirmed
Assigned To -
Operating System - All
Severity - Critical
Priority - Normal
Reported Version - Development
Due in Version - Undecided
Due Date - Undecided
Details - I am seeing a crash in the response forwarding part of kamailio core. This system is an IMS core, but I think this applies to any kamailio system. The scenario is this:
An INVITE is forked to a set of 5 registered locations. The next hop is over UDP and sends 100 Trying for all of them, but four of them cannot be routed onwards due to lost TCP connections.
The working connection sends a 603 Decline and receives an ACK
Kamailio sends a CANCEL to the remaining 4 branches and gets 200 OK for them.
After a delay, the next hop sends a 408 Timeout for the 4 pending INVITE transactions.
It appears that Kamailio tries to forward the 603 Decline for more than one branch and this causes a crash when building the subsequent response buffers - (maybe the response is in shared memory and is being freed by another process).
One or more files have been attached.
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=384
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#383 - htable $sht() not returning $null anymore
User who did this - Daniel-Constantin Mierla (miconda)
----------
Actually, the thing is that $var(...) cannot hold $null, it was always set to 0 when a null value was assigned to it.
See some more details at:
* http://www.kamailio.org/wiki/install/upgrade/4.0.x-to-4.1.0#behaviour
The right way is to check $sht(did=>$rU) against $null.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=383#comment1242
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
Hello,
yesterday we experienced an unusual segmentation fault in
Kamailio-4.0.2. We tried to do some troubleshooting but didn't really
get anywhere:
root@server:~# gdb /usr/local/kamailio/sbin/kamailio /var/log/core
(...)
output of bt full command in this link:
http://pastebin.com/kS1SQJWe
We'd be grateful if anybody could take a look.
Regards
Javi
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#383 - htable $sht() not returning $null anymore
User who did this - i (takeshi)
----------
Here is how it is being used:
modparam("htable", "htable", "did=>size=20;dbtable=htable_did;")
$var(domain) = $sht(did=>$rU);
if($var(domain) == $null) {
sl_send_reply("480", "Unresolved");
exit;
}
I assign the return value of $sht() to a variable ($var(domain)) because I will need it further down the road.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=383#comment1241
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#383 - htable $sht() not returning $null anymore
User who did this - Daniel-Constantin Mierla (miconda)
----------
First, you should use stable branch 4.1 instead of master for production - here is a tutorial for it:
- http://www.kamailio.org/wiki/install/4.1.x/git
Then, for the issue, returning 0 if the key does not exist is not good. Can you put here the definition of the hash table -- the htable parameter for the htable module?
Do you use the $sht() in a comparison expression or do you assign it to some variable? Perhaps is good to put here how you use it in the config as well.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=383#comment1240
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - i (takeshi)
Attached to Project - sip-router
Summary - htable $sht() not returning $null anymore
Task Type - Bug Report
Category - Module
Status - Unconfirmed
Assigned To -
Operating System - All
Severity - Low
Priority - Normal
Reported Version - Development
Due in Version - Undecided
Due Date - Undecided
Details - Hello,
I am tasked with updating a machine running this kamailio commit:
commit e9a61dd16dffb6e6e74810431741a297b62524c1
Author: Elena-Ramona Modroiu <ramona(a)asipto.com>
Date: Tue Jul 19 09:46:35 2011 +0200
to latest release.
I got this one:
commit ef66bf4ce961a7379bb21e848f70d03defb8864c
Author: Richard Good <richard.good(a)smilecoms.com>
Date: Fri Dec 20 10:09:35 2013 +0200
Doing tests, i verified that behavior of htable pseudo-variable $sht() has changed:
before, if a key was not found, $null would be returned.
But the latest commit returns 0 (zero) instead.
I don't believe this change was intentional as I consider 0 to be a valid value to be returned for a lookup.
Regards,
Takeshi.
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=383
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
Hello,
Kamailio SIP Server v4.0.5 stable release is out.
This is a maintenance release of the stable branch 4.0, that includes
fixes since release of v4.0.4. There is no change to database schema or
configuration language structure that you have to do on installations of
v4.0.x. Deployments running previous v4.0.x versions are strongly
recommended to be upgraded to v4.0.5.
For more details about version 4.0.5 (including links and guidelines to
download the tarball or from GIT repository), visit:
* http://www.kamailio.org/w/2013/12/kamailio-v4-0-5-released/
Note that 4.0.x is previous stable release series, the latest one is now
4.1.x, with v4.1.0 released about two weeks ago.
Cheers,
Daniel
--
Daniel-Constantin Mierla - http://www.asipto.comhttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda