sr-dev

sr-dev@lists.kamailio.org

44307 discussions

by Daniel-Constantin Mierla

Module: sip-router Branch: master Commit: 7a5f0fa88564b8ccc3d710773ff5ac8a3f49cdd4 URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=7a5f0fa… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: Sun Oct 24 23:03:45 2010 +0200 auth: fixe typo in docs --- modules/auth/README | 12 ++++++------ modules/auth/doc/functions.xml | 6 +++--- 2 files changed, 9 insertions(+), 9 deletions(-) diff --git a/modules/auth/README b/modules/auth/README index 433422c..025a044 100644 --- a/modules/auth/README +++ b/modules/auth/README @@ -15,7 +15,7 @@ Daniel-Constantin Mierla asipto.com <miconda(a)gmail.com> - Copyright � 2002, 2003 FhG FOKUS + Copyright © 2002, 2003 FhG FOKUS __________________________________________________________________ 1.1. Overview @@ -528,10 +528,10 @@ if (www_authenticate("realm", "subscriber)) { * realm - Realm is a opaque string that the user agent should present to the user so he can decide what username and password to use. Usually this is domain of the host the server is running on. - It must not be empty string "". In case of REGISTER requests To - header field domain (e.g., varibale $td) can be used (because this - header field represents a user being registered), for all other - messages From header field domain can be used (e.g., varibale $fd). + It must not be empty string “”. In case of REGISTER requests To + header field domain (e.g., variable $td) can be used (because this + header field represents the user being registered), for all other + messages From header field domain can be used (e.g., variable $fd). The string may contain pseudo variables. * flags - Value of this parameter can be a bitmask of following: + 1 - build challenge header with qop=auth @@ -590,7 +590,7 @@ if (!proxy_authenticate("$fd", "subscriber)) { * realm - Realm is a opaque string that the user agent should present to the user so he can decide what username and password to use. Usually this is domain of the host the server is running on. - It must not be empty string "". In case of REGISTER requests To + It must not be empty string “”. In case of REGISTER requests To header field domain (e.g., varibale $td) can be used (because this header field represents a user being registered), for all other messages From header field domain can be used (e.g., varibale $fd). diff --git a/modules/auth/doc/functions.xml b/modules/auth/doc/functions.xml index c293822..45eceb6 100644 --- a/modules/auth/doc/functions.xml +++ b/modules/auth/doc/functions.xml @@ -55,10 +55,10 @@ if (www_authenticate("realm", "subscriber)) { </para> <para> It must not be empty string <quote></quote>. In case of REGISTER - requests To header field domain (e.g., varibale $td) can be used - (because this header field represents a user being registered), + requests To header field domain (e.g., variable $td) can be used + (because this header field represents the user being registered), for all other messages From header field domain can be used - (e.g., varibale $fd). + (e.g., variable $fd). </para> <para> The string may contain pseudo variables.

14 years, 3 months

git:master: auth_db(k): note about empty realm parameter

by Daniel-Constantin Mierla

Module: sip-router Branch: master Commit: bacb5704a05dafb345221095ff194a9181394b98 URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=bacb570… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: Sun Oct 24 23:03:59 2010 +0200 auth_db(k): note about empty realm parameter - empty realm is no longer allowed, use $td of $fd if you have multi-domain --- modules_k/auth_db/README | 11 ++++++----- modules_k/auth_db/doc/auth_db_admin.xml | 15 ++++++++++----- 2 files changed, 16 insertions(+), 10 deletions(-) diff --git a/modules_k/auth_db/README b/modules_k/auth_db/README index dc1cccf..cb6177c 100644 --- a/modules_k/auth_db/README +++ b/modules_k/auth_db/README @@ -305,11 +305,10 @@ modparam("auth_db", "load_credentials", "$avp(i:123)=rpid;email_address") * realm - Realm is a opaque string that the user agent should present to the user so he can decide what username and password to use. Usually this is domain of the host the server is running on. - If an empty string “” is used then the server will generate it from - the request. In case of REGISTER requests To header field domain - will be used (because this header field represents a user being - registered), for all other messages From header field domain will - be used. + It must not be empty string “”. In case of REGISTER requests To + header field domain (e.g., variable $td) can be used (because this + header field represents the user being registered), for all other + messages From header field domain can be used (e.g., variable $fd). The string may contain pseudo variables. * table - Table to be used to lookup usernames and passwords (usually subscribers table). @@ -346,6 +345,8 @@ if (www_authorize("kamailio.org", "subscriber")) { * realm - Realm is a opaque string that the user agent should present to the user so he can decide what username and password to use. Usually this is domain of the host the server is running on. + It must not be empty string “”. Apart of a static strinh, typical + value is From header field domain (e.g., variable $fd). If an empty string “” is used then the server will generate it from the request. From header field domain will be used as realm. The string may contain pseudo variables. diff --git a/modules_k/auth_db/doc/auth_db_admin.xml b/modules_k/auth_db/doc/auth_db_admin.xml index b6e1d14..f00e5ca 100644 --- a/modules_k/auth_db/doc/auth_db_admin.xml +++ b/modules_k/auth_db/doc/auth_db_admin.xml @@ -324,11 +324,11 @@ modparam("auth_db", "load_credentials", "$avp(i:123)=rpid;email_address") the server is running on. </para> <para> - If an empty string <quote></quote> is used then the server will - generate it from the request. In case of REGISTER requests To - header field domain will be used (because this header field - represents a user being registered), for all other messages From - header field domain will be used. + It must not be empty string <quote></quote>. In case of REGISTER + requests To header field domain (e.g., variable $td) can be used + (because this header field represents the user being registered), + for all other messages From header field domain can be used + (e.g., variable $fd). </para> <para> The string may contain pseudo variables. @@ -395,6 +395,11 @@ if (www_authorize("kamailio.org", "subscriber")) { the server is running on. </para> <para> + It must not be empty string <quote></quote>. Apart of a static + strinh, typical value is From header field domain + (e.g., variable $fd). + </para> + <para> If an empty string <quote></quote> is used then the server will generate it from the request. From header field domain will be used as realm.

14 years, 3 months

git:3.1: tm: fixed typo in docs

by Daniel-Constantin Mierla

Module: sip-router Branch: 3.1 Commit: 7c4c6136a230aa71b8856b2df03bbdb43249e97a URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=7c4c613… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: Wed Oct 20 12:54:40 2010 +0200 tm: fixed typo in docs - some ingeter parameters related to control of reason header for local cancel were provided as string values instead of integer - reported by Mikko Lehto (cherry picked from commit 97d4e101219dbb035f2a734a2a1ddea119782f55) --- modules/tm/README | 10 +++++----- modules/tm/doc/params.xml | 4 ++-- 2 files changed, 7 insertions(+), 7 deletions(-) diff --git a/modules/tm/README b/modules/tm/README index 318c3bf..4e535bc 100644 --- a/modules/tm/README +++ b/modules/tm/README @@ -8,9 +8,9 @@ Juha Heinanen <jh(a)tutpro.com> - Copyright � 2003 FhG FOKUS + Copyright © 2003 FhG FOKUS - Copyright � 2008 Juha Heinanen + Copyright © 2008 Juha Heinanen Revision History Revision $Revision$ $Date$ __________________________________________________________________ @@ -177,7 +177,7 @@ Juha Heinanen Note Several Kamailio (OpenSER) TM module functionalities are now - implemented in the TMX module: "modules_k/tmx". Check it to see if what + implemented in the TMX module: “modules_k/tmx”. Check it to see if what you are looking for is there. 1.2. Serial Forking Based on Q Value @@ -1149,7 +1149,7 @@ modparam("tm", "failure_reply_mode", 3) Example 38. Set local_cancel_reason parameter ... -modparam("tm", "local_cancel_reason", "0") +modparam("tm", "local_cancel_reason", 0) ... 1.4.39. e2e_cancel_reason (boolean) @@ -1167,7 +1167,7 @@ modparam("tm", "local_cancel_reason", "0") Example 39. Set e2e_cancel_reason parameter ... -modparam("tm", "e2e_cancel_reason", "0") +modparam("tm", "e2e_cancel_reason", 0) ... 1.5. Functions diff --git a/modules/tm/doc/params.xml b/modules/tm/doc/params.xml index 2bd0724..f881af5 100644 --- a/modules/tm/doc/params.xml +++ b/modules/tm/doc/params.xml @@ -1198,7 +1198,7 @@ modparam("tm", "failure_reply_mode", 3) <title>Set <varname>local_cancel_reason</varname> parameter</title> <programlisting> ... -modparam("tm", "local_cancel_reason", "0") +modparam("tm", "local_cancel_reason", 0) ... </programlisting> </example> @@ -1230,7 +1230,7 @@ modparam("tm", "local_cancel_reason", "0") <title>Set <varname>e2e_cancel_reason</varname> parameter</title> <programlisting> ... -modparam("tm", "e2e_cancel_reason", "0") +modparam("tm", "e2e_cancel_reason", 0) ... </programlisting> </example>

14 years, 3 months

git:3.1: auth_db(k): updated return codes meaning

by Daniel-Constantin Mierla

Module: sip-router Branch: 3.1 Commit: b7e7a8fb2551422e2b853036e2a4bee2d8d82c32 URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=b7e7a8f… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: Sun Oct 24 20:33:01 2010 +0200 auth_db(k): updated return codes meaning - authentication functions use now auth module that was inherited from ser for better nonce protection and performances, therefore the return codes have different meanings (cherry picked from commit 6760745b4187c7b5af2752a82754aa0e511a38c9) --- modules_k/auth_db/README | 114 +++++++++++++++++++------------ modules_k/auth_db/doc/auth_db_admin.xml | 104 +++++++++++++++------------- 2 files changed, 127 insertions(+), 91 deletions(-) Diff: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commitdiff;h=b7e…

14 years, 3 months

git:3.1: htable: updated example with www auth

by Daniel-Constantin Mierla

Module: sip-router Branch: 3.1 Commit: ba80998055c95ae5f6dc730ecc4233981b432003 URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=ba80998… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: Sun Oct 24 20:48:56 2010 +0200 htable: updated example with www auth - some more details about hash tables (cherry picked from commit 8431de384b9fb6122203ed7388a26990cd4b025c) --- modules_k/htable/README | 35 ++++++++++++++++++++++---------- modules_k/htable/doc/htable_admin.xml | 30 ++++++++++++++++++++------- 2 files changed, 46 insertions(+), 19 deletions(-) diff --git a/modules_k/htable/README b/modules_k/htable/README index 9e8fe6f..facb147 100644 --- a/modules_k/htable/README +++ b/modules_k/htable/README @@ -11,7 +11,7 @@ Elena-Ramona Modroiu <ramona(a)rosdev.ro> - Copyright � 2008 http://www.asipto.com + Copyright © 2008 http://www.asipto.com __________________________________________________________________ Table of Contents @@ -116,9 +116,21 @@ Chapter 1. Admin Guide The module adds a hash table container to configuration language. The hash table is stored in shared memory and the access to it can be done - via pseudo-variables: $sht(htname=>name). + via pseudo-variables: $sht(htname=>name). The module supports + definition of many hash tables and can load values at startup from a + database table. - The "name" can be a static string or can include pseudo- variables that + A typical use case for the SIP server is to implement a cache system in + configuration file - if a value is not found in hash table, load it + from database and store it in hash table so next time the access to it + is very fast. In the definition of the table you can define the default + expiration time of cached items. The expiration time can be adjusted + per itme via assignment operation at runtime. + + You can read more about hash tables at: + http://en.wikipedia.org/wiki/Hash_table. + + The “name” can be a static string or can include pseudo- variables that will be replaced at runtime. Example 1.1. Accessing $sht(htname=>key) @@ -141,7 +153,7 @@ $sht(a=>$ci::srcip) = $si; the failed authentications per user and one for storing the time of last authentication attempt. To ensure unique name per user, the hash table uses a combination of authentication username and text - "::auth_count" and "::last_auth". + “::auth_count” and “::last_auth”. Example 1.2. Dictionary attack limitation ... @@ -160,7 +172,7 @@ if(is_present_hf("Authorization")) $sht(a=>$au::auth_count) = 0; } } - if(!www_authorize("")) + if(!www_authenticate("$td", "subscriber")) { switch ($retcode) { case -1: @@ -175,12 +187,12 @@ if(is_present_hf("Authorization")) $sht(a=>$au::last_auth) = $Ts; break; } - www_challenge(""/*realm*/,"0"/*qop*/); + www_challenge("$td"/*realm*/,"0"/*qop*/); exit; } $sht(a=>$au::auth_count) = 0; } else { - www_challenge("","0"); + www_challenge("$td","0"); exit; } ... @@ -243,9 +255,10 @@ if(is_present_hf("Authorization")) * htname - string specifying the name of the hash table. This string is used by $sht(...) to refer to the hash table. * size - number specifying the size of hash table. Larger value means - less collisions. The number of entries in the table is 2^size. The - possible range for this value is from 8 to 14, smaller or larger - values will be increased or decreased respectivly. + less collisions. The number of entries (aka slots or buckets) in + the table is 2^size. The possible range for this value is from 2 to + 14, smaller or larger values will be increased or decreased + respectivly. * autoexpire -time in seconds to delete an item from hash table if no update was done to it. If is missing or set to 0, the items won't expire. @@ -257,7 +270,7 @@ if(is_present_hf("Authorization")) Example 1.3. Set hash_size parameter ... modparam("htable", "htable", "a=>size=4;autoexpire=7200;dbtable=htable_a;") -modparam("htable", "htable", "a=>size=4;autoexpire=7200;dbtable=htable_a;") +modparam("htable", "htable", "b=>size=5;") ... 3.2. db_url (str) diff --git a/modules_k/htable/doc/htable_admin.xml b/modules_k/htable/doc/htable_admin.xml index 1257b6f..e2c2be6 100644 --- a/modules_k/htable/doc/htable_admin.xml +++ b/modules_k/htable/doc/htable_admin.xml @@ -18,7 +18,21 @@ <para> The module adds a hash table container to configuration language. The hash table is stored in shared memory and the access to it can be - done via pseudo-variables: $sht(htname=>name). + done via pseudo-variables: $sht(htname=>name). The module supports + definition of many hash tables and can load values at startup from + a database table. + </para> + <para> + A typical use case for the SIP server is to implement a cache system + in configuration file - if a value is not found in hash table, load + it from database and store it in hash table so next time the access to + it is very fast. In the definition of the table you can define the + default expiration time of cached items. The expiration time can + be adjusted per itme via assignment operation at runtime. + </para> + <para> + You can read more about hash tables at: + http://en.wikipedia.org/wiki/Hash_table. </para> <para> The <quote>name</quote> can be a static string or can include pseudo- @@ -70,7 +84,7 @@ if(is_present_hf("Authorization")) $sht(a=>$au::auth_count) = 0; } } - if(!www_authorize("")) + if(!www_authenticate("$td", "subscriber")) { switch ($retcode) { case -1: @@ -85,12 +99,12 @@ if(is_present_hf("Authorization")) $sht(a=>$au::last_auth) = $Ts; break; } - www_challenge(""/*realm*/,"0"/*qop*/); + www_challenge("$td"/*realm*/,"0"/*qop*/); exit; } $sht(a=>$au::auth_count) = 0; } else { - www_challenge("","0"); + www_challenge("$td","0"); exit; } ... @@ -221,9 +235,9 @@ if(is_present_hf("Authorization")) <para> <emphasis>size</emphasis> - number specifying the size of hash table. Larger value means less collisions. The number of entries - in the table is 2^size. The possible range for this value is from - 8 to 14, smaller or larger values will be increased or decreased - respectivly. + (aka slots or buckets) in the table is 2^size. The possible range + for this value is from 2 to 14, smaller or larger values will be + increased or decreased respectivly. </para> </listitem> <listitem> @@ -250,7 +264,7 @@ if(is_present_hf("Authorization")) <programlisting format="linespecific"> ... modparam("htable", "htable", "a=>size=4;autoexpire=7200;dbtable=htable_a;") -modparam("htable", "htable", "a=>size=4;autoexpire=7200;dbtable=htable_a;") +modparam("htable", "htable", "b=>size=5;") ... </programlisting> </example>

14 years, 3 months

git:3.1: tm: fix possible uninit. use of cancel_reason

by Daniel-Constantin Mierla

Module: sip-router Branch: 3.1 Commit: 292bab78715749066db5693b22b490fcbcfa4e4a URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=292bab7… Author: Andrei Pelinescu-Onciul <andrei(a)iptel.org> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: Wed Oct 20 18:38:11 2010 +0200 tm: fix possible uninit. use of cancel_reason In some cases an uninitialized cancel_reason structure was used (e.g. fake_reply() and relay_reply() failing). Reported-by: Alex Balashov abalashov evaristesys com (cherry picked from commit 7faa58b0264cb77c991a21bd3b7e3d660596ad85) --- modules/tm/t_cancel.c | 1 + modules/tm/t_reply.c | 11 +++++++++++ modules/tm/timer.c | 1 + 3 files changed, 13 insertions(+), 0 deletions(-) diff --git a/modules/tm/t_cancel.c b/modules/tm/t_cancel.c index 277c415..c1b52be 100644 --- a/modules/tm/t_cancel.c +++ b/modules/tm/t_cancel.c @@ -225,6 +225,7 @@ int cancel_branch( struct cell *t, int branch, irb=&t->uac[branch].request; irb->flags|=F_RB_CANCELED; ret=1; + init_cancel_info(&tmp_cd); # ifdef EXTRA_DEBUG if (crb->buffer!=BUSY_BUFFER) { diff --git a/modules/tm/t_reply.c b/modules/tm/t_reply.c index fcf214d..382244f 100644 --- a/modules/tm/t_reply.c +++ b/modules/tm/t_reply.c @@ -1096,8 +1096,11 @@ static unsigned char drop_replies; * Checks if the new reply (with new_code status) should be sent or not * based on the current * transaction status. + * + * @param cancel_data - initialized cancel_info structure. * Returns - branch number (0,1,...) which should be relayed * -1 if nothing to be relayed + * WARNING: cancel_data should be initialized prior to calling this function. */ static enum rps t_should_relay_response( struct cell *Trans , int new_code, int branch , int *should_store, int *should_relay, @@ -1576,6 +1579,10 @@ skip: REPLY_LOCK and it returns unlocked! If do_put_on_wait==1 and this is the final reply, the transaction wait timer will be started (put_on_wait(t)). + * + * @param cancel_data - initialized cancel_info structure. + * + * WARNING: cancel_data should be initialized prior to calling this function. */ enum rps relay_reply( struct cell *t, struct sip_msg *p_msg, int branch, unsigned int msg_status, struct cancel_info *cancel_data, @@ -1851,6 +1858,10 @@ error01: /* this is the "UAC" above transaction layer; if a final reply is received, it triggers a callback; note well -- it assumes it is entered locked with REPLY_LOCK and it returns unlocked! + * + * @param cancel_data - initialized cancel_info structure. + * + * WARNING: cancel_data should be initialized prior to calling this function. */ enum rps local_reply( struct cell *t, struct sip_msg *p_msg, int branch, unsigned int msg_status, struct cancel_info *cancel_data) diff --git a/modules/tm/timer.c b/modules/tm/timer.c index a961675..a31a59c 100644 --- a/modules/tm/timer.c +++ b/modules/tm/timer.c @@ -303,6 +303,7 @@ static void fake_reply(struct cell *t, int branch, int code ) short do_cancel_branch; enum rps reply_status; + init_cancel_info(&cancel_data); do_cancel_branch = is_invite(t) && prepare_cancel_branch(t, branch, 0); /* mark branch as canceled */ t->uac[branch].request.flags|=F_RB_CANCELED;

14 years, 3 months

git:master: htable: updated example with www auth

by Daniel-Constantin Mierla

Module: sip-router Branch: master Commit: 8431de384b9fb6122203ed7388a26990cd4b025c URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=8431de3… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: Sun Oct 24 20:48:56 2010 +0200 htable: updated example with www auth - some more details about hash tables --- modules_k/htable/README | 35 ++++++++++++++++++++++---------- modules_k/htable/doc/htable_admin.xml | 30 ++++++++++++++++++++------- 2 files changed, 46 insertions(+), 19 deletions(-) diff --git a/modules_k/htable/README b/modules_k/htable/README index 9e8fe6f..facb147 100644 --- a/modules_k/htable/README +++ b/modules_k/htable/README @@ -11,7 +11,7 @@ Elena-Ramona Modroiu <ramona(a)rosdev.ro> - Copyright � 2008 http://www.asipto.com + Copyright © 2008 http://www.asipto.com __________________________________________________________________ Table of Contents @@ -116,9 +116,21 @@ Chapter 1. Admin Guide The module adds a hash table container to configuration language. The hash table is stored in shared memory and the access to it can be done - via pseudo-variables: $sht(htname=>name). + via pseudo-variables: $sht(htname=>name). The module supports + definition of many hash tables and can load values at startup from a + database table. - The "name" can be a static string or can include pseudo- variables that + A typical use case for the SIP server is to implement a cache system in + configuration file - if a value is not found in hash table, load it + from database and store it in hash table so next time the access to it + is very fast. In the definition of the table you can define the default + expiration time of cached items. The expiration time can be adjusted + per itme via assignment operation at runtime. + + You can read more about hash tables at: + http://en.wikipedia.org/wiki/Hash_table. + + The “name” can be a static string or can include pseudo- variables that will be replaced at runtime. Example 1.1. Accessing $sht(htname=>key) @@ -141,7 +153,7 @@ $sht(a=>$ci::srcip) = $si; the failed authentications per user and one for storing the time of last authentication attempt. To ensure unique name per user, the hash table uses a combination of authentication username and text - "::auth_count" and "::last_auth". + “::auth_count” and “::last_auth”. Example 1.2. Dictionary attack limitation ... @@ -160,7 +172,7 @@ if(is_present_hf("Authorization")) $sht(a=>$au::auth_count) = 0; } } - if(!www_authorize("")) + if(!www_authenticate("$td", "subscriber")) { switch ($retcode) { case -1: @@ -175,12 +187,12 @@ if(is_present_hf("Authorization")) $sht(a=>$au::last_auth) = $Ts; break; } - www_challenge(""/*realm*/,"0"/*qop*/); + www_challenge("$td"/*realm*/,"0"/*qop*/); exit; } $sht(a=>$au::auth_count) = 0; } else { - www_challenge("","0"); + www_challenge("$td","0"); exit; } ... @@ -243,9 +255,10 @@ if(is_present_hf("Authorization")) * htname - string specifying the name of the hash table. This string is used by $sht(...) to refer to the hash table. * size - number specifying the size of hash table. Larger value means - less collisions. The number of entries in the table is 2^size. The - possible range for this value is from 8 to 14, smaller or larger - values will be increased or decreased respectivly. + less collisions. The number of entries (aka slots or buckets) in + the table is 2^size. The possible range for this value is from 2 to + 14, smaller or larger values will be increased or decreased + respectivly. * autoexpire -time in seconds to delete an item from hash table if no update was done to it. If is missing or set to 0, the items won't expire. @@ -257,7 +270,7 @@ if(is_present_hf("Authorization")) Example 1.3. Set hash_size parameter ... modparam("htable", "htable", "a=>size=4;autoexpire=7200;dbtable=htable_a;") -modparam("htable", "htable", "a=>size=4;autoexpire=7200;dbtable=htable_a;") +modparam("htable", "htable", "b=>size=5;") ... 3.2. db_url (str) diff --git a/modules_k/htable/doc/htable_admin.xml b/modules_k/htable/doc/htable_admin.xml index 1257b6f..e2c2be6 100644 --- a/modules_k/htable/doc/htable_admin.xml +++ b/modules_k/htable/doc/htable_admin.xml @@ -18,7 +18,21 @@ <para> The module adds a hash table container to configuration language. The hash table is stored in shared memory and the access to it can be - done via pseudo-variables: $sht(htname=>name). + done via pseudo-variables: $sht(htname=>name). The module supports + definition of many hash tables and can load values at startup from + a database table. + </para> + <para> + A typical use case for the SIP server is to implement a cache system + in configuration file - if a value is not found in hash table, load + it from database and store it in hash table so next time the access to + it is very fast. In the definition of the table you can define the + default expiration time of cached items. The expiration time can + be adjusted per itme via assignment operation at runtime. + </para> + <para> + You can read more about hash tables at: + http://en.wikipedia.org/wiki/Hash_table. </para> <para> The <quote>name</quote> can be a static string or can include pseudo- @@ -70,7 +84,7 @@ if(is_present_hf("Authorization")) $sht(a=>$au::auth_count) = 0; } } - if(!www_authorize("")) + if(!www_authenticate("$td", "subscriber")) { switch ($retcode) { case -1: @@ -85,12 +99,12 @@ if(is_present_hf("Authorization")) $sht(a=>$au::last_auth) = $Ts; break; } - www_challenge(""/*realm*/,"0"/*qop*/); + www_challenge("$td"/*realm*/,"0"/*qop*/); exit; } $sht(a=>$au::auth_count) = 0; } else { - www_challenge("","0"); + www_challenge("$td","0"); exit; } ... @@ -221,9 +235,9 @@ if(is_present_hf("Authorization")) <para> <emphasis>size</emphasis> - number specifying the size of hash table. Larger value means less collisions. The number of entries - in the table is 2^size. The possible range for this value is from - 8 to 14, smaller or larger values will be increased or decreased - respectivly. + (aka slots or buckets) in the table is 2^size. The possible range + for this value is from 2 to 14, smaller or larger values will be + increased or decreased respectivly. </para> </listitem> <listitem> @@ -250,7 +264,7 @@ if(is_present_hf("Authorization")) <programlisting format="linespecific"> ... modparam("htable", "htable", "a=>size=4;autoexpire=7200;dbtable=htable_a;") -modparam("htable", "htable", "a=>size=4;autoexpire=7200;dbtable=htable_a;") +modparam("htable", "htable", "b=>size=5;") ... </programlisting> </example>

14 years, 3 months

git:master: auth_db(k): updated return codes meaning

by Daniel-Constantin Mierla

Module: sip-router Branch: master Commit: 6760745b4187c7b5af2752a82754aa0e511a38c9 URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=6760745… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: Sun Oct 24 20:33:01 2010 +0200 auth_db(k): updated return codes meaning - authentication functions use now auth module that was inherited from ser for better nonce protection and performances, therefore the return codes have different meanings --- modules_k/auth_db/README | 114 +++++++++++++++++++------------ modules_k/auth_db/doc/auth_db_admin.xml | 104 +++++++++++++++------------- 2 files changed, 127 insertions(+), 91 deletions(-) Diff: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commitdiff;h=676…

14 years, 3 months

[tracker] Task opened: pooling of libsrdb1 doesnt restrict database connection to 1 thread and gives issues with postgresql (Attachment added)

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 - Robert Verspuy (exarv) Attached to Project - sip-router Summary - pooling of libsrdb1 doesnt restrict database connection to 1 thread and gives issues with postgresql Task Type - Bug Report Category - libsrdb1 (kamailio) Status - Assigned Assigned To - Henning Westerholt Operating System - Linux Severity - High Priority - Normal Reported Version - 3.1 Due in Version - Undecided Due Date - Undecided Details - In the source lib/srdb1/* some kind of pooling is used. When kamailio needs a database connection, the cmp_db_id function checks to see if there is already a database connection with the exact same params (username, database, server etc..). According to the PQ library every proces / thread should have it's own database connection. The db_postgres is setup to use asynchronous I/O with the PQ library. So when two threads are using the same database connection it is possible that, the resultset from a query of thread A is returned to thread B. The cmp_db_id function in lib/srdb1/db_id.c does _not_ check the PID. I've created a small patch to fix the problems mentioned above. The changes are made in lib/srdb1/* files So if you apply them, it will be active for _every_ database module. Maybe it's not needed for the mysql database, but I *assume* it will not break when used on a mysql database. (not tested) Maybe you will get a bit more database connections, but that depends on which modules you're using. What did I do: * Added pid to the db_id struct. * During initialization the pid is saved into the db_id struct. * In cmp_db_id the pid is also checked when searching for a database connection to be reused. See complete thread on http://lists.sip-router.org/pipermail/sr-dev/2010-October/009689.html One or more files have been attached. More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=97 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.

14 years, 3 months

[tracker] Assignee added: pooling of libsrdb1 doesnt restrict database connection to 1 thread and gives issues with postgresql

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#97 - pooling of libsrdb1 doesnt restrict database connection to 1 thread and gives issues with postgresql User who did this - Robert Verspuy (exarv) http://sip-router.org/tracker/index.php?do=details&task_id=97 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.

14 years, 3 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev