sr-dev April 2011

sr-dev@lists.kamailio.org

27 participants
271 discussions

[tracker] Task closed: 1.5.3 dialog module: dialogs stay in database when in "shutdown only" mode

by sip-router

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#36 - 1.5.3 dialog module: dialogs stay in database when in "shutdown only" mode User who did this - Timo Reimann (tr) Reason for closing: Won't fix More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=36 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.

13 years, 7 months

[tracker] Comment added: 1.5.3 dialog module: dialogs stay in database when in "shutdown only" mode

by sip-router

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#36 - 1.5.3 dialog module: dialogs stay in database when in "shutdown only" mode User who did this - Timo Reimann (tr) ---------- Following the OP's (Nathan's) suggestion, I'll close this bug as 1.5 is way too outdated to be concerned. If Nathan discovers the issue to persist in 3.x, I'll file another report or fix the bug right away, depending on the complexity of the bug. ---------- More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=36#comment202 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.

13 years, 7 months

[tracker] Comment added: 1.5.3 dialog module: dialogs stay in database when in "shutdown only" mode

by sip-router

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#36 - 1.5.3 dialog module: dialogs stay in database when in "shutdown only" mode User who did this - Timo Reimann (tr) ---------- Please report whether this is still an issue in the master branch. ---------- More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=36#comment201 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.

13 years, 7 months

[tracker] Task changed: 1.5.3 dialog module: dialogs stay in database when in "shutdown only" mode

by sip-router

13 years, 7 months

[tracker] Task changed: 1.5.3 dialog module: dialogs stay in database when in "shutdown only" mode

by sip-router

13 years, 7 months

[tracker] User took ownership: 1.5.3 dialog module: dialogs stay in database when in "shutdown only" mode

by sip-router

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. Timo Reimann has taken ownership of the following task: FS#36 - 1.5.3 dialog module: dialogs stay in database when in "shutdown only" mode More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=36 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.

13 years, 7 months

[tracker] Task opened: Add additional tm callbacks

by sip-router

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Timo Reimann (tr) Attached to Project - sip-router Summary - Add additional tm callbacks Task Type - Feature Request Category - tm Status - Assigned Assigned To - Andrei Pelinescu-Onciul Operating System - All Severity - Low Priority - Normal Reported Version - Development Due in Version - Undecided Due Date - Undecided Details - Please add the following callbacks to the tm module: (1) TMCB_REQUEST_OUT Kamailio 1.5 used to have it although it's name TMCB_REQUEST_BUILT was a slightly misleading. In my opinion, it should be labeled TMCB_REQUEST_OUT instead. (2) TMCB_REQUEST_READY Kamailio 1.5 lacked it, would be great to have. More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=124 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.

13 years, 7 months

[tracker] Assignee added: Add additional tm callbacks

by sip-router

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A user has added themself to the list of users assigned to this task. FS#124 - Add additional tm callbacks User who did this - Timo Reimann (tr) http://sip-router.org/tracker/index.php?do=details&task_id=124 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.

13 years, 7 months

[tracker] Task changed: Provide processed message in tm callbacks whenever possible

by sip-router

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has been changed. The changes are listed below. For full information about what has changed, visit the URL and click the History tab. FS#123 - Provide processed message in tm callbacks whenever possible User who did this: Timo Reimann (tr) Task details edited: ------- In Kamailio 1.5, certain callbacks (namely TMCB_RESPONSE_PRE_OUT, TMCB_RESPONSE_OUT, and TMCB_REQUEST_BUILT) provided the entire processed message (i.e., after headers were modified) in tmcb_params->extra1 as *str. AFAICS, sr's equivalent to that parameter is send_buf in the tmcb_params structure. However, the only sr callbacks that do provide the processed messages are TMCB_REQUEST_SENT and TMCB_RESPONSE_SENT which, had no perfect correspondency in Kamailio (*_OUT callbacks would not be called for retransmissions). Technically, this makes complete sense because the two *_SENT callbacks and the send_buf variable are available only when WITH_ONSEND is defined. Also, I noticed that these callbacks are handled through run_onsend_callbacks2() instead of run_trans_callbacks(). Only the former fill send_buf and hence pass processed messages as part of the callback. Please pass processed messages for all callbacks where a processed message is supposed to be available, i.e., all *_OUT and *_READY callbacks. (An email on the sr-dev list was originally posted by me on 28.7.2010. See [[http://lists.sip-router.org/pipermail/sr-dev/2010-July/008351.html|the archived mail]].) ------- More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=123 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.

13 years, 7 months

[tracker] Task changed: Provide processed message in tm callbacks whenever possible

by sip-router

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has been changed. The changes are listed below. For full information about what has changed, visit the URL and click the History tab. FS#123 - Provide processed message in tm callbacks whenever possible User who did this: Timo Reimann (tr) Task details edited: ------- In Kamailio 1.5, certain callbacks (namely TMCB_RESPONSE_PRE_OUT, TMCB_RESPONSE_OUT, and TMCB_REQUEST_BUILT) provided the entire processed message (i.e., after headers were modified) in tmcb_params->extra1 as *str. AFAICS, sr's equivalent to that parameter is send_buf in the tmcb_params structure. However, the only sr callbacks that do provide the processed messages are TMCB_REQUEST_SENT and TMCB_RESPONSE_SENT which, had no perfect correspondency in Kamailio (*_OUT callbacks would not be called for retransmissions). Technically, this makes complete sense because the two *_SENT callbacks and the send_buf variable are available only when WITH_ONSEND is defined. Also, I noticed that these callbacks are handled through run_onsend_callbacks2() instead of run_trans_callbacks(). Only the former fill send_buf and hence pass processed messages as part of the callback. Please pass processed messages for all callbacks where a processed message is supposed to be available, i.e., all *_OUT and *_READY callbacks. (An email on the sr-dev list was originally posted by me on 28.7.2010. See [[]]) ------- More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=123 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.

13 years, 7 months

← Newer
1
...
10
11
12
13
14
15
16
...
28
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev April 2011