sr-dev July 2011

sr-dev@lists.kamailio.org

28 participants
199 discussions

issue tracking system
by Daniel-Constantin Mierla 19 Jul '11

19 Jul '11

Hello, sightly off-topic and cc-ed to users mailing lists, but hopefully there will be people giving valuable feedback based on their experience. When we started the integration of source code for kamailio and ser, we went for FlySpray as issue tracking system (aka bug tracker). The project seems to be dead, nothing happened to it for long time, no updates and there are warnings using latest php versions, that may result in malfunctionality or no-functionality with future versions. Therefore maybe it is the time to make a decision, rather soon than later, but this time we should look a bit more carefully to available options, to avoid ending up (in short time) to the same issue. I see two major options: A) going to use a source code hosting portal for bug traker (like sourceforge, berlios, github, a.s.o.) B) going to use an existing software to be installed on our server and managed by us I tend to go for A) as the maintenance of the software will not be done by us. I do not know which would be the best choice to go for. Of course, we should consider possible down times (like it happened in the past) or slow connection to their servers. B) will give us full control, but then it is about the time to maintain it (upgrades, security patches, a.s.o.). More than that, it is about selecting the right software to go with. Since SEMS code is now hosted in GIT repo of sip-router.org, maybe the tracker can be used by them as well, eventually by future related projects hosted in our git. Opinions? Thanks, Daniel -- Daniel-Constantin Mierla -- http://www.asipto.com Kamailio Advanced Training, Oct 10-13, Berlin: http://asipto.com/u/kat http://linkedin.com/in/miconda -- http://twitter.com/miconda

4 3

[tracker] Task closed: t_check_trans is not allowed in onreply_route
by sip-router 19 Jul '11

19 Jul '11

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#117 - t_check_trans is not allowed in onreply_route User who did this - Daniel-Constantin Mierla (miconda) Reason for closing: Fixed Additional comments about closing: Patch committed on master, backports to follow. Please reopen if there is any issue. More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=117 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.

1 0

[tracker] Comment added: t_check_trans is not allowed in onreply_route
by sip-router 19 Jul '11

19 Jul '11

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#117 - t_check_trans is not allowed in onreply_route User who did this - Daniel-Constantin Mierla (miconda) ---------- Added safety set of T branch PV when using t_check_trans() for replies. If you can test and report the results, would be great. Thanks. ---------- More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=117#comment242 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.

1 0

git:master: tm: be sure branch PV is set when t_check_trans() is used for reply
by Daniel-Constantin Mierla 19 Jul '11

19 Jul '11

Module: sip-router Branch: master Commit: 2e426419ab2f3f15adc4a50de6efe3bb06dc77b8 URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=2e42641… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: Tue Jul 19 19:41:20 2011 +0200 tm: be sure branch PV is set when t_check_trans() is used for reply - reported by Alex Hermann, FS#117 --- modules/tm/tm.c | 13 +++++++++---- 1 files changed, 9 insertions(+), 4 deletions(-) diff --git a/modules/tm/tm.c b/modules/tm/tm.c index 096e30c..baf2d81 100644 --- a/modules/tm/tm.c +++ b/modules/tm/tm.c @@ -1937,12 +1937,17 @@ int w_t_reply_wrp(struct sip_msg *m, unsigned int code, char *txt) int t_check_trans(struct sip_msg* msg) { struct cell* t; + int branch; + int ret; - if (msg->first_line.type==SIP_REPLY) - return w_t_check(msg, 0 ,0); - else if (msg->REQ_METHOD==METHOD_CANCEL) + if (msg->first_line.type==SIP_REPLY) { + branch = 0; + ret = (t_check_msg( msg , &branch)==1) ? 1 : -1; + tm_ctx_set_branch_index(branch); + return ret; + } else if (msg->REQ_METHOD==METHOD_CANCEL) { return w_t_lookup_cancel(msg, 0, 0); - else{ + } else { switch(t_check_msg(msg, 0)){ case -2: /* possible e2e ack */ return 1;

1 0

[tracker] Comment added: Add additional tm callbacks
by sip-router 19 Jul '11

19 Jul '11

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#124 - Add additional tm callbacks User who did this - Daniel-Constantin Mierla (miconda) ---------- Do you have a patch for it? Should not be hard to add, just point where such events should be triggered. ---------- More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=124#comment241 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.

1 0

[tracker] User took ownership: Add additional tm callbacks
by sip-router 19 Jul '11

19 Jul '11

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. Daniel-Constantin Mierla has taken ownership of the following task: FS#124 - Add additional tm callbacks 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.

1 0

[tracker] Task closed: app_python doesn't work
by sip-router 19 Jul '11

19 Jul '11

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#137 - app_python doesn't work User who did this - Daniel-Constantin Mierla (miconda) Reason for closing: Fixed Additional comments about closing: Patch committed on master branch. Backports to follow upon confirmation that issue was fixed. More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=137 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.

1 0

[tracker] User took ownership: app_python doesn't work
by sip-router 19 Jul '11

19 Jul '11

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. Daniel-Constantin Mierla has taken ownership of the following task: FS#137 - app_python doesn't work More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=137 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.

1 0

[tracker] Comment added: app_python doesn't work
by sip-router 19 Jul '11

19 Jul '11

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#137 - app_python doesn't work User who did this - Daniel-Constantin Mierla (miconda) ---------- I committed a fix to master branch in order to provide a clone for dirname and basename functions. If you can test it, then we can backport. If the patch is not working, just reopen this issue. Thanks ---------- More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=137#comment240 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.

1 0

[tracker] Task closed: bug in $snd and $sndto pseudo variable
by sip-router 19 Jul '11

19 Jul '11

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#140 - bug in $snd and $sndto pseudo variable User who did this - Daniel-Constantin Mierla (miconda) Reason for closing: Fixed Additional comments about closing: Fixed in master branch, backports to follow. More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=140 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.

1 0

← Newer
1
...
8
9
10
11
12
13
14
...
20
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev July 2011