THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#424 - zombie dialogs in state 5 User who did this - Daniel-Constantin Mierla (miconda) ---------- What do you mean by: "If we want to just enforce the workaround (pre-create the transaction) it would be helpful to somehow notify in the logs that callbacks registration will be lost." ? Specific to this case or in general? This situation could be seen also as the common case of any retransmission coming fast enough that previous request doesn't get to a transaction. Normally, same processing is happening for both requests, the second will be dropped by tm at relay time. In such scenarios all should go fine, because both request should have same set of callbacks set independently, no matter which one gets through first to create the transaction. So here is more a dialog problem that skips processing the second bye internally because of no change to dlg state. There can be added a log message to print when the retransmission is detected that the process has callbacks in the local list, which will be no longer linked to transaction. But that could fill the log files, with logs for each late-detected retransmission. ---------- More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=424#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.