[sr-dev] [tracker] Task opened: Dialog module: dlg_terminate_dlg and register_dlgcb function

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Eduardo Lejarreta (lejarreta.e) Attached to Project - sip-router Summary - [sr-dev] Dialog module: dlg_terminate_dlg and register_dlgcb function Task Type - Improvement Category - dialog Status - Unconfirmed Assigned To - Operating System - Linux Severity - High Priority - Normal Reported Version - 3.2 Due in Version - Undecided Due Date - Undecided Details - Hi Daniel (I've been in the wrong site for weeks) I put this issue here just no to be forgotten, thanks and best regards ... Dialog, tm, rr and acc: 3.2.1 modules version When you finish externally a dialog, vía FIFO command with “dlg_terminate_dlg: callid, from_tag” the callback register function “register_dlgcb” on “DLGCB_TERMINATED” event returns a: dlg_cb_params * params->req with (NIL) value. the request does not exist in this case, going to be generated locally. This callback register function is used by “acc” module with acc_cdr accounting enabled to track the end of the call. In this scenario acc module can not account the end of the call. -> ERROR: acc [acc_cdr.c:480]: invalid values#012! If you try this scenario over TCP and with “RR” module with “enable_double_rr” enabled you will see that the “acc” module is able to track the end of the call because a double “Record-route” header is inserted by proxy. Do you think this could be an issue that it can be resolved in future? Or may be we’re forgetting something. Any help, any idea?, Maybe you can solve it by storing dialog hash and id -- see the $dlg(...) class of variables. It should be solved in a way or another, to become useful, please open an issue on the tracker not to forget about it. I plan to look a bit at cdr accounting with dialog before the next major release. Thanks. More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=256 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.