THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#122 - Kamailio 3.1.3 crash User who did this - Jasmin Schnatterbeck (jasmin) ---------- Hi Timo, thanks for your message regarding the sip-spirals! Regarding dlg_manage(); it created a new dialog, despite the BYE request was in-dialog. I think that using the event-route for locally generated requests could be the problem, because it's may unusual to call functions of the dialog module in that case. May it would not be even possible without the change Daniel proposed (see above) regarding fork_process. As you mentioned, the availability of $dlg is a bit complex. There is dlg_get(), dlg_manage() and the tracking flag. In my opinion it is important to define when we should be able to decide, whether the dialog module should process the request or not. Before the first route for a request is started (event route and other "special routes") the module could check, if there is a dialog or not. For loose-routed requests that's easy, because of did=, but as there are different ways to trigger a request, it gets more and more complicated. I think besides the existing methods (enable/disable automatic processing of did= ) there should be a way to load a dialog manually. A request can be triggered in different ways through mi or other modules - it seems impossible to write a automatic dialog-detection-routine for every possible case. For example dlg_end_dlg sends hash_entry and hash_id as mi params in a specific order. If these x params are available (maybe $miparams(0-x)) it would be possible to load the dialog with an exported dialog-module function, that can load dialogs based on h_id and h_entry. Of course $dlg working every time without having to load something manually etc. would be perfect, but I think there are some limits for many special cases.... Regarding time machines, there are some disussions again http://arxiv.org/pdf/1103.1373v1 :-) Cheers Jasmin ---------- More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=122#comment1… 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.