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.