sr-dev July 2011

sr-dev@lists.kamailio.org

28 participants
198 discussions

git:master: kamdbctl: added pipelimit to the list of extra tables to create
by Daniel-Constantin Mierla 20 Jul '11

20 Jul '11

Module: sip-router Branch: master Commit: 0be9f5a4efeba2eb297a2e3286b9795f33f2dbe2 URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=0be9f5a… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: Wed Jul 20 23:42:05 2011 +0200 kamdbctl: added pipelimit to the list of extra tables to create --- utils/kamctl/kamdbctl.base | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff … [View More]

1 0

Re: [sr-dev] [SR-Users] issue tracking system
by Daniel-Constantin Mierla 20 Jul '11

20 Jul '11

Hello, some comments about all provided options so far: - google code tracker -- haven't use it at all, going to look a bit at it - github - maybe I missed some setting, but the issue tracker there seems to be to simplistic - no way to categorize in bugs or feature requests - jira - folks at SER used it in the past when we were two projects, reporting that it was rather buggy to keep using it -- maybe it was just the version purchased at that time (several years ago). I am not familiar … [View More]with its administration at all - mantis - I have no experience with it to say pro/con opinions. Is the administration (upgrade, patching) easy enough? Does it support multi-projects on the same instance? - redmine - it is the one I use for various needs, therefore I have some experience with its administration. However, I cannot say that it is a thing I would like to take care of. It seems to be a bit heavy, I had to patch it (for some quite basic features such as different email address for different projects or the body of notification emails -- I have to say I am not that familiar with it and I may have missed some plugins/settings) For self installed app, at this time my preferences would be redmine, mantis, jira -- a big + to rise the rank in the order would come if there is going to be someone to commit for the maintenance of either one. Haven't made my mind for hosted options yet. More comments? Any other options? Thanks, Daniel On 7/19/11 8:18 PM, Jason Penton wrote: > +1 for Jira. If you have the resources to setup and manage JIRA then I > would suggest this too. We use and it is really very good > > On Tue, Jul 19, 2011 at 8:05 PM, Alex Balashov > <abalashov(a)evaristesys.com <mailto:abalashov@evaristesys.com>> wrote: > > We have been extremely happy with Mantis as a self-hosted > approach. It is easy to use, yet has the sophistication and > flexibility for a needed to manage a project of non-trivial size. > > On the other hand, Digium recently moved away from it in favour of > JIRA for issues.asterisk.org <http://issues.asterisk.org>. > > For fairly large projects like this one[1], I have always favoured > internal hosting of such systems in order to maintain maximum > control, use optional plugins, make customisations, etc. I think > that would make the most sense for the SR/Kamailio community. > > -- Alex > > [1] It's not nearly as large as say, the Linux kernel, but it's > bigger than 99% of open-source which, after all, consists largely > of projects done by one person or a few people at most. > -- 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 [View Less]

5 8

git:master: core: small doxygen fix, synchronize a few function definitions with declarations
by Henning Westerholt 20 Jul '11

20 Jul '11

Module: sip-router Branch: master Commit: d949f97e5b3707100a7dfc8422ece0f19bcc163c URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=d949f97… Author: Henning Westerholt <henning.westerholt(a)1und1.de> Committer: Henning Westerholt <henning.westerholt(a)1und1.de> Date: Wed Jul 20 22:49:21 2011 +0200 core: small doxygen fix, synchronize a few function definitions with declarations --- mem/f_malloc.h | 28 ++++++++++++++-------------- 1 files changed, … [View More]14 insertions(+), 14 deletions(-) diff --git a/mem/f_malloc.h b/mem/f_malloc.h index 2246ee1..bd18bd9 100644 --- a/mem/f_malloc.h +++ b/mem/f_malloc.h @@ -114,10 +114,10 @@ struct fm_frag_lnk{ * \see mem_info */ struct fm_block{ - unsigned long size; /* total size */ + unsigned long size; /** total size */ #if defined(DBG_F_MALLOC) || defined(MALLOC_STATS) - unsigned long used; /* alloc'ed size*/ - unsigned long real_used; /* used+malloc overhead*/ + unsigned long used; /** allocated size*/ + unsigned long real_used; /** used + malloc overhead */ unsigned long max_real_used; #endif @@ -146,10 +146,10 @@ struct fm_block* fm_malloc_init(char* address, unsigned long size); * \return address of allocated memory */ #ifdef DBG_F_MALLOC -void* fm_malloc(struct fm_block*, unsigned long size, +void* fm_malloc(struct fm_block* qm, unsigned long size, const char* file, const char* func, unsigned int line); #else -void* fm_malloc(struct fm_block*, unsigned long size); +void* fm_malloc(struct fm_block* qm, unsigned long size); #endif @@ -161,10 +161,10 @@ void* fm_malloc(struct fm_block*, unsigned long size); * \param p freed memory */ #ifdef DBG_F_MALLOC -void fm_free(struct fm_block*, void* p, const char* file, const char* func, +void fm_free(struct fm_block* qm, void* p, const char* file, const char* func, unsigned int line); #else -void fm_free(struct fm_block*, void* p); +void fm_free(struct fm_block* qm, void* p); #endif @@ -178,10 +178,10 @@ void fm_free(struct fm_block*, void* p); * \return reallocated memory block */ #ifdef DBG_F_MALLOC -void* fm_realloc(struct fm_block*, void* p, unsigned long size, +void* fm_realloc(struct fm_block* qm, void* p, unsigned long size, const char* file, const char* func, unsigned int line); #else -void* fm_realloc(struct fm_block*, void* p, unsigned long size); +void* fm_realloc(struct fm_block* qm, void* p, unsigned long size); #endif @@ -189,7 +189,7 @@ void* fm_realloc(struct fm_block*, void* p, unsigned long size); * \brief Report internal memory manager status * \param qm memory block */ -void fm_status(struct fm_block*); +void fm_status(struct fm_block* qm); /** @@ -200,7 +200,7 @@ void fm_status(struct fm_block*); * \param qm memory block * \param memory information */ -void fm_info(struct fm_block*, struct mem_info*); +void fm_info(struct fm_block* qm, struct mem_info* info); /** @@ -209,7 +209,7 @@ void fm_info(struct fm_block*, struct mem_info*); * \return Returns how much free memory is available, on error (not compiled * with bookkeeping code) returns (unsigned long)(-1) */ -unsigned long fm_available(struct fm_block*); +unsigned long fm_available(struct fm_block* qm); /** @@ -217,9 +217,9 @@ unsigned long fm_available(struct fm_block*); * \param qm memory block */ #ifdef DBG_F_MALLOC -void fm_sums(struct fm_block*); +void fm_sums(struct fm_block* qm); #else -#define fm_sums(v) do{}while(0) +#define fm_sums(qm) do{}while(0) #endif /* DBG_F_MALLOC */ #endif [View Less]

1 0

git:master: core: remove commented out ROUNDUP macro (2002) and big_hash_idx() (2007)
by Henning Westerholt 20 Jul '11

20 Jul '11

Module: sip-router Branch: master Commit: 683a4899a992b42d60cc0d45bd10ff197d85dd39 URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=683a489… Author: Henning Westerholt <henning.westerholt(a)1und1.de> Committer: Henning Westerholt <henning.westerholt(a)1und1.de> Date: Wed Jul 20 21:34:14 2011 +0200 core: remove commented out ROUNDUP macro (2002) and big_hash_idx() (2007) --- mem/f_malloc.c | 19 ------------------- mem/q_malloc.c | 5 ----- 2 … [View More]

1 0

git:master: core: doxygen documentation for F_MALLOC memory manager
by Henning Westerholt 20 Jul '11

20 Jul '11

Module: sip-router Branch: master Commit: c20927f7867163efa7d800bd0e7fee65e5980dcb URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=c20927f… Author: Henning Westerholt <henning.westerholt(a)1und1.de> Committer: Henning Westerholt <henning.westerholt(a)1und1.de> Date: Wed Jul 20 22:36:41 2011 +0200 core: doxygen documentation for F_MALLOC memory manager --- mem/f_malloc.c | 112 ++++++++++++++++++++++++++++++++++++++++++++----------- mem/f_malloc.h |… [View More]

1 0

git:master: fixed issue regarding caching presentity information when in DB_ONLY mode
by Marius Ovidiu Bucur 20 Jul '11

20 Jul '11

Module: sip-router Branch: master Commit: a3d6d80d1805109b6340cd7182323ef9ad9c11d4 URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=a3d6d80… Author: Marius Bucur <marius(a)marius-bucur.ro> Committer: Marius Bucur <marius(a)marius-bucur.ro> Date: Wed Jul 20 20:27:51 2011 +0300 fixed issue regarding caching presentity information when in DB_ONLY mode --- modules_k/presence/notify.c | 7 ++++++- 1 files changed, 6 insertions(+), 1 deletions(-) diff … [View More]

1 0

git:master: Add new db option and improve connect mechanism.
by Andreas Granig 20 Jul '11

20 Jul '11

Module: sip-router Branch: master Commit: 2cbd47c4f9a16ef869efd7830e48a419b3cc1020 URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=2cbd47c… Author: Andreas Granig <agranig(a)sipwise.com> Committer: Andreas Granig <agranig(a)sipwise.com> Date: Wed Jul 20 15:54:21 2011 +0200 Add new db option and improve connect mechanism. Add "db" option to "server" parameter to select the redis db number. Set 1 sec timeout when connecting to redis server. Perform "… [View More]PING" to verify newly created redis connection. --- modules/ndb_redis/README | 6 ++-- modules/ndb_redis/doc/ndb_redis_admin.xml | 6 ++-- modules/ndb_redis/redis_client.c | 41 ++++++++++++++++++++++------- 3 files changed, 37 insertions(+), 16 deletions(-) diff --git a/modules/ndb_redis/README b/modules/ndb_redis/README index 37409c4..8dc695d 100644 --- a/modules/ndb_redis/README +++ b/modules/ndb_redis/README @@ -87,15 +87,15 @@ Chapter 1. Admin Guide Specify the details to connect to REDIS server. It takes a list of attribute=value separated by semicolon, the attributes can be name, - addr and port. Name is a genric identifier to be used with module + addr, port and db. Name is a generic identifier to be used with module functions. addr and port are the IP address and the port to connect to - REDIS server. + REDIS server. db is the DB number to use (defaults to 0 if not specified). Default value is NULL. Example 1.1. Set server parameter ... -modparam("ndb_redis", "server", "name=srvN;addr=127.0.0.1;port=6379") +modparam("ndb_redis", "server", "name=srvN;addr=127.0.0.1;port=6379;db=1") ... 4. Exported Functions diff --git a/modules/ndb_redis/doc/ndb_redis_admin.xml b/modules/ndb_redis/doc/ndb_redis_admin.xml index a9609a2..4e2db66 100644 --- a/modules/ndb_redis/doc/ndb_redis_admin.xml +++ b/modules/ndb_redis/doc/ndb_redis_admin.xml @@ -64,9 +64,9 @@ <para> Specify the details to connect to REDIS server. It takes a list of attribute=value separated by semicolon, the attributes can be - name, addr and port. Name is a genric identifier to be used with + name, addr, port and db. Name is a generic identifier to be used with module functions. addr and port are the IP address and the port to - connect to REDIS server. + connect to REDIS server. db is the DB number to use (defaults to 0 if not specified). </para> <para> <emphasis> @@ -77,7 +77,7 @@ <title>Set <varname>server</varname> parameter</title> <programlisting format="linespecific"> ... -modparam("ndb_redis", "server", "name=srvN;addr=127.0.0.1;port=6379") +modparam("ndb_redis", "server", "name=srvN;addr=127.0.0.1;port=6379;db=1") ... </programlisting> </example> diff --git a/modules/ndb_redis/redis_client.c b/modules/ndb_redis/redis_client.c index 37c67f7..6a91019 100644 --- a/modules/ndb_redis/redis_client.c +++ b/modules/ndb_redis/redis_client.c @@ -34,6 +34,8 @@ #include "redis_client.h" +#define redisCommandNR(a...) (int)({ void *__tmp; __tmp = redisCommand(a); if (__tmp) freeReplyObject(__tmp); __tmp ? 0 : -1;}) + static redisc_server_t *_redisc_srv_list=NULL; static redisc_reply_t *_redisc_rpl_list=NULL; @@ -44,9 +46,13 @@ static redisc_reply_t *_redisc_rpl_list=NULL; int redisc_init(void) { char *addr; - unsigned int port; + unsigned int port, db; redisc_server_t *rsrv=NULL; param_t *pit = NULL; + struct timeval tv; + + tv.tv_sec = 1; + tv.tv_usec = 0; if(_redisc_srv_list==NULL) { @@ -58,6 +64,7 @@ int redisc_init(void) { addr = "127.0.0.1"; port = 6379; + db = 0; for (pit = rsrv->attrs; pit; pit=pit->next) { if(pit->name.len==4 && strncmp(pit->name.s, "addr", 4)==0) { @@ -66,19 +73,33 @@ int redisc_init(void) } else if(pit->name.len==4 && strncmp(pit->name.s, "port", 4)==0) { if(!str2int(&pit->body, &port)) port = 6379; + } else if(pit->name.len==2 && strncmp(pit->name.s, "db", 2)==0) { + if(!str2int(&pit->body, &db)) + db = 0; } } - rsrv->ctxRedis = redisConnect(addr, port); - if (rsrv->ctxRedis->err) { - LM_ERR("failed to connect to redis server [%.*s]: %s\n", - rsrv->sname->len, rsrv->sname->s, rsrv->ctxRedis->errstr); - return -1; - } else { - LM_DBG("connected to redis server [%.*s] (%s:%d)\n", - rsrv->sname->len, rsrv->sname->s, addr, port); - } + rsrv->ctxRedis = redisConnectWithTimeout(addr, port, tv); + if(!rsrv->ctxRedis) + goto err; + if (rsrv->ctxRedis->err) + goto err2; + if (redisCommandNR(rsrv->ctxRedis, "PING")) + goto err2; + if (redisCommandNR(rsrv->ctxRedis, "SELECT %i", db)) + goto err2; + } + return 0; + +err2: + LM_ERR("error communicating with redis server [%.*s] (%s:%d/%d): %s\n", + rsrv->sname->len, rsrv->sname->s, addr, port, db, rsrv->ctxRedis->errstr); + return -1; +err: + LM_ERR("failed to connect to redis server [%.*s] (%s:%d/%d)\n", + rsrv->sname->len, rsrv->sname->s, addr, port, db); + return -1; } /** [View Less]

1 0

Re: [sr-dev] [SR-Users] issue tracking system
by Daniel-Constantin Mierla 20 Jul '11

20 Jul '11

Btw, anyone has any experience/feedback with BugGenie? http://www.thebuggenie.com/ Just found it and at least it looks pretty. However, does not seem well documented on the web site, neither big community around (based on a quick look). Thanks, Daniel On 7/20/11 2:32 AM, Alex Balashov wrote: > We use RT as a ticketing system too. It's great for that. But I don't think it's suitable as a bug tracking or project management database for software development per se, and that's not what it … [View More]

1 0

Project conference in Berlin, Sep 02, 2011
by Daniel-Constantin Mierla 20 Jul '11

20 Jul '11

Hello, the details for organizing the 10 years SER conference in Berlin were settled. After the initial announcement the interest was quite high, by now we have a good number of attendees and speakers. We are still open for new speakers, with the target of showing use cases of Kamailio or SER. The event will be hosted by FhG Fokus institute, where SER project was started. It will be a day full of presentations, followed by an evening social networking event. We hope to be able to provide … [View More]

1 0

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. … [View More]

4 3

← Newer
1
...
7
8
9
10
11
12
13
...
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