sr-dev October 2009

sr-dev@lists.kamailio.org

30 participants
468 discussions

git:sr_3.0: Implements function reset_path_vector.

by Jan Janak

Module: sip-router Branch: sr_3.0 Commit: ef2e4841537add1ef10ce93acff64c9a6a2b563b URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=ef2e484… Author: Jan Janak <jan(a)ryngle.com> Committer: Jan Janak <jan(a)ryngle.com> Date: Sat Oct 17 19:36:20 2009 +0200 Implements function reset_path_vector. This function can be used to reset the path_vec variable that stores the path vector for a SIP message. It can be used just like reset_dst_uri. --- parser/msg_parser.c | 11 +++++++++++ parser/msg_parser.h | 3 +++ 2 files changed, 14 insertions(+), 0 deletions(-) diff --git a/parser/msg_parser.c b/parser/msg_parser.c index c203e7a..0388bd4 100644 --- a/parser/msg_parser.c +++ b/parser/msg_parser.c @@ -783,6 +783,17 @@ int set_path_vector(struct sip_msg* msg, str* path) return 0; } + +void reset_path_vector(struct sip_msg* msg) +{ + if(msg->path_vec.s != 0) { + pkg_free(msg->path_vec.s); + } + msg->path_vec.s = 0; + msg->path_vec.len = 0; +} + + struct hdr_field* get_hdr(struct sip_msg *msg, enum _hdr_types_t ht) { struct hdr_field *hdr; diff --git a/parser/msg_parser.h b/parser/msg_parser.h index 22b3167..ce4c81d 100644 --- a/parser/msg_parser.h +++ b/parser/msg_parser.h @@ -464,4 +464,7 @@ struct hdr_field* get_hdr(struct sip_msg *msg, enum _hdr_types_t ht); struct hdr_field* next_sibling_hdr(struct hdr_field *hf); int set_path_vector(struct sip_msg* msg, str* path); + +void reset_path_vector(struct sip_msg* msg); + #endif

15 years, 1 month

git:master: Implements function reset_path_vector.

by Jan Janak

Module: sip-router Branch: master Commit: 9c2f5f658a597bb70a7f4250476c358294513cef URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=9c2f5f6… Author: Jan Janak <jan(a)ryngle.com> Committer: Jan Janak <jan(a)ryngle.com> Date: Sat Oct 17 19:36:20 2009 +0200 Implements function reset_path_vector. This function can be used to reset the path_vec variable that stores the path vector for a SIP message. It can be used just like reset_dst_uri. --- parser/msg_parser.c | 11 +++++++++++ parser/msg_parser.h | 3 +++ 2 files changed, 14 insertions(+), 0 deletions(-) diff --git a/parser/msg_parser.c b/parser/msg_parser.c index c203e7a..0388bd4 100644 --- a/parser/msg_parser.c +++ b/parser/msg_parser.c @@ -783,6 +783,17 @@ int set_path_vector(struct sip_msg* msg, str* path) return 0; } + +void reset_path_vector(struct sip_msg* msg) +{ + if(msg->path_vec.s != 0) { + pkg_free(msg->path_vec.s); + } + msg->path_vec.s = 0; + msg->path_vec.len = 0; +} + + struct hdr_field* get_hdr(struct sip_msg *msg, enum _hdr_types_t ht) { struct hdr_field *hdr; diff --git a/parser/msg_parser.h b/parser/msg_parser.h index 22b3167..ce4c81d 100644 --- a/parser/msg_parser.h +++ b/parser/msg_parser.h @@ -464,4 +464,7 @@ struct hdr_field* get_hdr(struct sip_msg *msg, enum _hdr_types_t ht); struct hdr_field* next_sibling_hdr(struct hdr_field *hf); int set_path_vector(struct sip_msg* msg, str* path); + +void reset_path_vector(struct sip_msg* msg); + #endif

15 years, 1 month

git:master: Merge branch 'master' of ssh://oej@git.sip-router.org/ sip-router

by Olle E. Johansson

Module: sip-router Branch: master Commit: 233fb5015484069f56f57f1a279c95288337d001 URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=233fb50… Author: oej <oej(a)edvina.net> Committer: oej <oej(a)edvina.net> Date: Thu Oct 15 02:02:50 2009 +0200 Merge branch 'master' of ssh://oej@git.sip-router.org/sip-router * 'master' of ssh://oej@git.sip-router.org/sip-router: tls(sr): fix define error introduced in 9accd256fdc80e6a6207cb7 ---

15 years, 1 month

serial forking and restart_fr_on_each_reply

by Jan Janak

Juha, There is the parameter restart_fr_on_each_reply, its documentation says: Setting it to 0 is especially useful when dealing with bad UAs that continuously retransmit 180s, not allowing the transaction to timeout (and thus making impossible the implementation of certain services, like automatic voicemail after x seconds). The parameter is enabled by default. Shouldn't we disable this when we do serial forking with t_next_contacts. To guarantee that UAs retransmitting 180s do not prevent serial forking from happening? -- Jan

15 years, 1 month

git:master: - Reinstating empty README files made by mistake

by Olle E. Johansson

Module: sip-router Branch: master Commit: 79141db20aad382abd5f423b43c655432285e024 URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=79141db… Author: oej <oej(a)edvina.net> Committer: oej <oej(a)edvina.net> Date: Sat Oct 17 17:25:04 2009 +0200 - Reinstating empty README files made by mistake - Updating XML docs for CTL module (please review) - Adding two new entities to our master catalog And yes, changing catalog.xml will create a commit... --- docbook/entities.xml | 2 + modules/ctl/README | 50 +- modules/ctl/doc/ctl.xml | 34 +- modules/ctl/doc/params.xml | 44 +- modules/ctl/doc/rpc.xml | 26 +- modules/dialplan/README | 420 ++++++++++ modules/tm/README | 1820 ++++++++++++++++++++++++++++++++++++++++++++ 7 files changed, 2328 insertions(+), 68 deletions(-) Diff: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commitdiff;h=791…

15 years, 1 month

reset dst_uri in t_load_contacts

by Jan Janak

Juha, Function t_loads contacts in tm/t_serial.c encodes the Request-URI and all branches of the SIP message into an AVP. At the end the function calls clear_branches to remove all branches from the SIP request, so that a subsequent call to t_next_contacts can only restore those with highest q number. I am wondering if calling clear_branches is enough. Shouldn't the function also call reset_dst_uri to reset the value of the dst_uri (which is now also stored in the AVP), and perhaps also clear the send socket, the branch flags and the path vector for the Request-URI? All these values are encoded into the AVP, but they are only cleared for additional branches (in clear_branches), but not for the Request-URI "branch". I also considered doing that in clear_branches, but then I realized that this function is called from other places and modules and it could break them. Any thoughts on this? How thorough should t_load_contacts be when it resets variables whose values are stored in the AVP? -- Jan

15 years, 1 month

t_next_contacts and fr_inv_timer_next

by Jan Janak

Juha, I wrote a very simple sip-router script to test serial forking based on q values with t_load_contacts and t_next_contacts. I noticed that when I use t_next_contacts before the transaction exists, it uses the value of fr_inv_timer_next even for the first branch. Is this itendended behavior? Shouldn't the function use the value of fr_inv_timer for the first branch and then fr_inv_timer_next for subsequent branches? This is where fr_inv_timer_next is set for the first branch: http://git.sip-router.org/cgi-bin/gitweb.cgi?p=kamailio;a=blob;f=modules/tm… -- Jan

15 years, 1 month

git:master: two debian packaging changes to fix package building

by Henning Westerholt

Module: sip-router Branch: master Commit: 98a8514ab6c01078a77536b8bc6498932db0642f URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=98a8514… Author: Henning Westerholt <henning.westerholt(a)1und1.de> Committer: Henning Westerholt <henning.westerholt(a)1und1.de> Date: Fri Oct 16 17:20:31 2009 +0200 two debian packaging changes to fix package building - add missing libpcre3-dev package for lcr module - comment not working sed replacement out for now, was this script moved? --- pkg/debian/control | 2 +- pkg/debian/rules | 5 +++-- 2 files changed, 4 insertions(+), 3 deletions(-) diff --git a/pkg/debian/control b/pkg/debian/control index 6e2f0c5..bd23d71 100644 --- a/pkg/debian/control +++ b/pkg/debian/control @@ -2,7 +2,7 @@ Source: ser Section: net Priority: optional Maintainer: Andrei Pelinescu-Onciul <andrei(a)iptel.org> -Build-Depends: debhelper (>= 4), libmysqlclient-dev | libmysqlclient15-dev | libmysqlclient14-dev | libmysqlclient12-dev, libexpat1-dev, libradius-ng-dev | libradiusclient-ng-dev | libradius1-dev, libxml2-dev, libpq-dev | postgresql-dev, libcurl3-dev, libssl-dev, libreadline5-dev, bison, flex +Build-Depends: debhelper (>= 4), libmysqlclient-dev | libmysqlclient15-dev | libmysqlclient14-dev | libmysqlclient12-dev, libexpat1-dev, libradius-ng-dev | libradiusclient-ng-dev | libradius1-dev, libxml2-dev, libpq-dev | postgresql-dev, libcurl3-dev, libssl-dev, libreadline5-dev, libpcre3-dev, bison, flex Standards-Version: 3.5.2 Package: ser diff --git a/pkg/debian/rules b/pkg/debian/rules index 289ec3e..dd85545 100755 --- a/pkg/debian/rules +++ b/pkg/debian/rules @@ -181,8 +181,9 @@ install: build # install the *.sql files for ser_mysql.sh script cp -f scripts/mysql/*.sql $(CURDIR)/debian/ser/usr/lib/ser/ # and fix path to the *.sql files in ser_mysql.sh script - sed -i 's#DEFAULT_SCRIPT_DIR=.*#DEFAULT_SCRIPT_DIR="/usr/lib/ser/"#' \ - $(CURDIR)/debian/ser/usr/sbin/ser_mysql.sh + #FIXME + #sed -i 's#DEFAULT_SCRIPT_DIR=.*#DEFAULT_SCRIPT_DIR="/usr/lib/ser/"#' \ + # $(CURDIR)/debian/ser/usr/sbin/ser_mysql.sh # install advanced ser config file for ser-oob package mkdir -p $(CURDIR)/debian/ser-oob/etc/ser cp -f etc/sip-router-oob.cfg $(CURDIR)/debian/ser-oob/etc/ser/ser-oob.cfg

15 years, 1 month

git:kamailio_3.0: core: added new event SREV_CORE_STATS

by jh＠tutpro.com

i didn't get any answer to my question about this commit. it looks to me that there is now two versions of sip-router core. i thought that the agreement was that there is only one core and that all commits to core are done to sr_3.0 branch. can someone explain to me what is going on? am i missing something? why this commit could not use done to sr_3.0 perhaps #ifdef kamailio or something like that so that there would be only one core? -- juha

15 years, 1 month

[OT] How does SR Git repository handle access permissions?

by Iñaki Baz Castillo

Hi, sorry for this off-topic. I'm starting with Git (yeah!) and creating a repository in my server to manage various projects. I'm learning about Git and access control (users, permissions, authorization per repository and so). How is this stuff implemented in SR Git repository? does it use Gitosis? If not, how is managed the permissions? Thanks for any tip. -- Iñaki Baz Castillo <ibc(a)aliax.net>

15 years, 1 month

← Newer
1
...
20
21
22
23
24
25
26
...
47
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev October 2009