sr-dev June 2013

sr-dev@lists.kamailio.org

33 participants
235 discussions

assistance required
by Piyush.Bansal＠relianceada.com 28 Jun '13

28 Jun '13

Hi, I am using SER iptel as a SIP proxy. I have few doubts regarding ser.cfg configuration file. 1. I am having two config variables, say $a and $b. Can't I do any comparison of the two in any if loop? e.g. [if ($a == $b)] or something similar. 2. I exported a function from a module say func1( ). It works perfectly fine if I pass a static value in it but corrupts the value if I pass a variable thru it.e.g. func1("11") will work fine but $a = '11' and func1("%$a") will not work. Please help. Regards --Piyush The information contained in this electronic message (email) and any attachments to this email are intended for the exclusive use of the addressee(s) and access to this email by any one else is unauthorised. The email may contain proprietary, confidential or privileged information or information relating to Reliance Group. If you are not the intended recipient, please notify the sender by telephone, fax, or return email and delete this communication and any attachments thereto, immediately from your computer. Any dissemination, distribution, or copying of this communication and the attachments thereto (in whole or part), in any manner, is strictly prohibited and actionable at law. The recipient acknowledges that emails are susceptible to alteration and their integrity can not be guaranteed and that Company does not guarantee that any e-mail is virus-free and accept no liability for any damage caused by any virus transmitted by this email.

1 0

[tracker] Comment added: Nathelper: modparam natping_processes max value
by sip-router 27 Jun '13

27 Jun '13

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#321 - Nathelper: modparam natping_processes max value User who did this - Víctor Seva (linuxmaniac) ---------- BTW is there any particular reason to have this limit? ---------- More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=321#comment975 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: Nathelper: modparam natping_processes max value
by sip-router 27 Jun '13

27 Jun '13

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#321 - Nathelper: modparam natping_processes max value User who did this - Víctor Seva (linuxmaniac) ---------- from modules/nathelper.c: if (natping_processes>=8) { LM_ERR("too many natping processes (%d) max=8\n", natping_processes); return -1; } and at mod_init: if (rank==PROC_MAIN && natping_interval > 0) { for( i=0 ; i<natping_processes ; i++ ) { if(fork_dummy_timer(PROC_TIMER, "TIMER NH", 1 /*socks flag*/, nh_timer, (void*)(unsigned long)i, 1 /*sec*/)<0) { LM_ERR("failed to register timer routine as process\n"); return -1; /* error */ } } } So... I think this is just what we need: diff --git a/modules/nathelper/nathelper.c b/modules/nathelper/nathelper.c index cff54d8..948c9c0 100644 --- a/modules/nathelper/nathelper.c +++ b/modules/nathelper/nathelper.c @@ -671,7 +671,7 @@ mod_init(void) " set in usrloc module\n"); return -1; } - if (natping_processes>=8) { + if (natping_processes>8) { LM_ERR("too many natping processes (%d) max=8\n", natping_processes); return -1; ---------- More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=321#comment974 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 opened: Nathelper: modparam natping_processes max value
by sip-router 27 Jun '13

27 Jun '13

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Jon Bonilla (manwe) Attached to Project - sip-router Summary - Nathelper: modparam natping_processes max value Task Type - Bug Report Category - Module Status - New Assigned To - Operating System - Linux Severity - Very Low Priority - Low Reported Version - 4.0 Due in Version - Undecided Due Date - Undecided Details - Module nathelper. When setting modparam natping_processes to 8 kamailio refuses to start with this message: "ERROR: nathelper [nathelper.c:678]: mod_init(): too many natping processes (8) max=8" Setting the modparam to 7 works. Should the error message be changed or should kamaiio support 8 natping_preocesses? Reported by: Andrew Pogrebennyk More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=321 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: modules_k/uac: uac_replace_from/to AUTO mode with dialog module
by Anca Vamanu 27 Jun '13

27 Jun '13

Module: sip-router Branch: master Commit: 0f702f6e236eb0cbb238bf83a0c4ae94d7b3cad8 URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=0f702f6… Author: Anca Vamanu <anca.vamanu(a)1and1.ro> Committer: Anca Vamanu <anca.vamanu(a)1and1.ro> Date: Thu Jul 19 17:49:13 2012 +0300 modules_k/uac: uac_replace_from/to AUTO mode with dialog module Added a implementation for uac_replace_from/to() that uses the dialog module for AUTO mode. In this mode the URIs are stored as dialog variables. The change in tm module fixes a bug: if uac_replace_to() was called, the URI was not changed accordingly in Cancel. --- modules/tm/t_cancel.c | 5 +- modules_k/dialog/dialog.c | 2 + modules_k/dialog/dlg_load.h | 6 + modules_k/uac/README | 111 +++++++++++----- modules_k/uac/doc/uac_admin.xml | 68 +++++++++- modules_k/uac/replace.c | 292 ++++++++++++++++++++++++++++++--------- modules_k/uac/uac.c | 17 ++- 7 files changed, 393 insertions(+), 108 deletions(-) Diff: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commitdiff;h=0f7…

2 1

'481 dialog/transaction does not exists' error.
by Ravindra Gowda 26 Jun '13

26 Jun '13

Dear All, I have integrated Kamailio (Version 4.0.1) with Asterisk (Version 11.4.0 rc1) server. I should have get VoIP features(call, SMS) with this integrated server. But when i tried to call other end SIP client through this integrated server, I'm getting the '*481 dialog/transaction does not exists*' error (please find the attachment 'call.pcap' below). SMS is through with the kamailio server without any problem (Find the attachment 'SMS.pcap' below). But when it comes to Calling feature, something is wrong and i am unable to find it. So please help me in resolving this issue. My system configuration is as follows: Host Architecture: i686 OS : Ubuntu 12.04 LTS Clients: Wi-Fi enabled VoIP phones. Find the attachments below for the kamailio configuration file and tcpdump based trace files for Calling and SMSing process, to give a more complete picture. Any help will greatly appreciate. *Thank you and Best regards,* *R Ravindra **Gowda*

1 0

[tracker] Comment added: default_expires_range should be applied to all expire times, not only to default
by sip-router 26 Jun '13

26 Jun '13

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#249 - default_expires_range should be applied to all expire times, not only to default User who did this - Alekzander Spiridonov (alekz) ---------- I do believe that existing behavior should not be modified. Separate option should be introduced instead. Anyway I do agree that current implementation doesn't make much sense in case of reg spikes prevention. ---------- More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=249#comment973 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 opened: Configuration Directives: Five Syntaxes: kamailio.cfg:
by sip-router 26 Jun '13

26 Jun '13

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Brian LaVallee (poing) Attached to Project - sip-router Summary - Configuration Directives: Five Syntaxes: kamailio.cfg: Task Type - Improvement Category - Core Status - Unconfirmed Assigned To - Operating System - All Severity - Low Priority - Normal Reported Version - 4.0 Due in Version - Undecided Due Date - Undecided Details - When I opened the kamailio.cfg file for the first time, I was lost in the syntax variations. There are actually five (5) different variations. REQUEST: Please work towards a single directive syntax for the kamailio.cfg configuration file. I ended up putting together a wiki page that covers the different variations. Since there are a number of areas that can be improved, please review the wiki page to understand the various issues. http://www.kamailio.org/wiki/cookbooks/4.0.x/core/cfg A FEW SUGGESTIONS: - Move the Route Function [Scripts] to a separate (or individual) configuration file(s). - Uniform treatment of name/value pairs. -- Settle on a single syntax. (Normal or Apache Style) -- Add flexibility for values enclosed in quotes. "All", none, or just "has a white-space". - Add PHP style // for line comments. More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=320 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 opened: Possible memory leak in srdb1
by sip-router 26 Jun '13

26 Jun '13

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Konstantin (Konstantin) Attached to Project - sip-router Summary - Possible memory leak in srdb1 Task Type - Bug Report Category - libsrdb1 (kamailio) Status - Unconfirmed Assigned To - Operating System - Linux Severity - Low Priority - Normal Reported Version - 4.0 Due in Version - Undecided Due Date - Undecided Details - Hi, I found that inside function db_free_columns in the file lib\srdb1\db_res.c there is no memory free for RES_NAMES(_r)[col]->s structure member pointer. It could be a memory leak. The RES_NAMES(_r)[col]->s points to a dynamically allocated memory and it should be deallocated with all other structures inside db1_res_t. I found it in version 3.1.5 and I checked that the issue exists in the latest version as well. Best regards, Konstantin. More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=319 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: modules/ims_auth: updated documentation
by Richard Good 25 Jun '13

25 Jun '13

Module: sip-router Branch: master Commit: 8f1904fd0a0b305b2c528df0d1d3c27d5eef0c7d URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=8f1904f… Author: Richard Good <richard.good(a)smilecoms.com> Committer: Richard Good <richard.good(a)smilecoms.com> Date: Tue Jun 25 15:41:42 2013 +0200 modules/ims_auth: updated documentation - updated documentation to use route blocks after async diameter --- modules/ims_auth/doc/ims_auth_admin.xml | 68 +++++++++++++++++++++++++++---- 1 files changed, 60 insertions(+), 8 deletions(-) diff --git a/modules/ims_auth/doc/ims_auth_admin.xml b/modules/ims_auth/doc/ims_auth_admin.xml index 56eb972..3357cc9 100644 --- a/modules/ims_auth/doc/ims_auth_admin.xml +++ b/modules/ims_auth/doc/ims_auth_admin.xml @@ -274,8 +274,6 @@ modparam("ims_auth", "max_nonce_reuse", 1) </example> </section> - </section> - <section> <title><varname>add_authinfo_hdr</varname> (integer)</title> @@ -404,8 +402,8 @@ modparam("ims_auth", "av_check_only_impu", 1) <programlisting format="linespecific"> ... if (!www_authorize("kamailio.org", "subscriber")) { - www_challenge("kamailio.org", "1"); -}; + www_challenge(""REG_MAR_REPLY"", "kamailio.org", "1"); +}; ... </programlisting> </example> @@ -421,7 +419,7 @@ if (!www_authorize("kamailio.org", "subscriber")) { </section> <section> - <title><function moreinfo="none">ims_www_challenge(realm, + <title><function moreinfo="none">ims_www_challenge(route_block, realm, table)</function></title> <para>Name alias: proxy_authorize(realm, table)</para> @@ -442,6 +440,9 @@ if (!www_authorize("kamailio.org", "subscriber")) { <itemizedlist> <listitem> + <para>Route block to resume after async MAR Diameter reply.</para> + </listitem> + <listitem> <para><emphasis>realm</emphasis> - 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 @@ -472,15 +473,39 @@ if (!www_authorize("kamailio.org", "subscriber")) { <programlisting format="linespecific"> ... if (!proxy_authorize("$fd", "subscriber)) { - proxy_challenge("$fd", "1"); # Realm will be autogenerated + proxy_challenge(""REG_MAR_REPLY","$fd"); # Realm will be autogenerated }; ... + ... +route[REG_MAR_REPLY] +{ + #this is async so to know status we have to check the reply avp + xlog("L_DBG","maa_return code is $avp(s:maa_return_code)\n"); + + switch ($avp(s:maa_return_code)){ + case 1: #success + xlog("L_DBG", "MAR success - 401/407 response sent from module\n"); + break; + case -1: #failure + xlog("L_ERR", "MAR failure - error response sent from module\n"); + break; + case -2: #error + xlog("L_ERR", "MAR error - sending error response now\n"); + t_reply("500", "MAR failed"); + break; + default: + xlog("L_ERR", "Unknown return code from MAR, value is [$avp(s:uaa_return_code)]\n"); + t_reply("500", "Unknown response code from MAR"); + break; + } + exit; +} </programlisting> </example> </section> <section> - <title><function moreinfo="none">ims_proxy_challenge(realm, + <title><function moreinfo="none">ims_proxy_challenge(route_block, realm, table)</function></title> <para>Name alias: proxy_authorize(realm, table)</para> @@ -501,6 +526,9 @@ if (!proxy_authorize("$fd", "subscriber)) { <itemizedlist> <listitem> + <para>Route block to resume after async MAR Diameter reply.</para> + </listitem> + <listitem> <para><emphasis>realm</emphasis> - 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 @@ -531,9 +559,33 @@ if (!proxy_authorize("$fd", "subscriber)) { <programlisting format="linespecific"> ... if (!proxy_authorize("$fd", "subscriber)) { - proxy_challenge("$fd", "1"); # Realm will be autogenerated + proxy_challenge("REG_MAR_REPLY","$fd", "1"); # Realm will be autogenerated }; ... +route[REG_MAR_REPLY] +{ + #this is async so to know status we have to check the reply avp + xlog("L_DBG","maa_return code is $avp(s:maa_return_code)\n"); + + switch ($avp(s:maa_return_code)){ + case 1: #success + xlog("L_DBG", "MAR success - 401/407 response sent from module\n"); + break; + case -1: #failure + xlog("L_ERR", "MAR failure - error response sent from module\n"); + break; + case -2: #error + xlog("L_ERR", "MAR error - sending error response now\n"); + t_reply("500", "MAR failed"); + break; + default: + xlog("L_ERR", "Unknown return code from MAR, value is [$avp(s:uaa_return_code)]\n"); + t_reply("500", "Unknown response code from MAR"); + break; + } + exit; +} +... </programlisting> </example> </section>

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev June 2013