sr-dev November 2012

sr-dev@lists.kamailio.org

28 participants
122 discussions

Using t_suspend()/t_continue() multiple times on the same transaction

by Peter Dunkley

Hi, I am trying to use t_suspend()/t_continue() multiple times on the same transaction. Calling t_suspend() more than once works, but the second time I call t_continue() the transaction is killed and a 500 response is sent. It is the "if (branch == t->nr_of_outgoings)" check from the code fragment below (from t_suspend.c:t_continue()) that results in the transaction being killed - you can see the debug/error line I added to determine this in the fragment. Is using t_suspend()/t_continue() multiple times something that should work? Thanks, Peter if (t->uas.status < 200) { /* No final reply has been sent yet. * Check whether or not there is any pending branch. */ for ( branch = 0; branch < t->nr_of_outgoings; branch++ ) { if ((t->uac[branch].request.buffer != NULL) && (t->uac[branch].last_received < 200) ) break; } if (branch == t->nr_of_outgoings) { /* There is not any open branch so there is * no chance that a final response will be received. */ ret = 0; LM_ERR("branch == t->nr_of_outgoings\n"); goto kill_trans; } } -- Peter Dunkley Technical Director Crocodile RCS Ltd

10 years, 4 months

default config: do loose_route() for in-dialog NOTIFY as per new RFC 6665

by Iñaki Baz Castillo

Hi, the new RFC 6665 mandates that the subscription dialog is made *after* the first NOTIFY from the UAS (rather than after the 200 to the initial SUBSCRIBE). This means that the UAC MUST take the route set from the *first* received NOTIFY (instead of taking it from the 200 to the initial SUBSCRIBE). Therefore a proxy compliant with RFC 6665 MUST always add RR to in-dialog NOTIFY requests and thus, I propose that the default SR script file implements it. Regards. -- Iñaki Baz Castillo <ibc(a)aliax.net>

10 years, 9 months

git:master: modules_k/uac: uac_replace_from/to AUTO mode with dialog module

by Anca Vamanu

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…

11 years, 4 months

dns resolver issue (RFC3263)

by MÉSZÁROS Mihály

Hi All, I am experiencing an issue when i try to contact xy(a)cisco.com. I found that kamailio/sip-router can't resolve by default resolving way a TCP + SRV records from domain cisco.com. e.g. cisco.com misi@alma:~$ host -t NAPTR cisco.com cisco.com has no NAPTR record misi@alma:~$ host -t SRV _sip._udp.cisco.com Host _sip._udp.cisco.com not found: 3(NXDOMAIN) misi@alma:~$ host -t SRV _sip._tcp.cisco.com _sip._tcp.cisco.com has SRV record 1 0 5060 vcsgw.cisco.com. misi@alma:~$ host -t SRV _sips._tcp.cisco.com _sips._tcp.cisco.com has SRV record 1 0 5061 vcsgw.cisco.com. I can't call xy(a)cisco.com because it does not exists an NAPTR record in domain cisco.com, and furthermore no SRV with udp. But it exists sip+tcp record and also exists an secure sip SRV, so sips+tcp record! I read rfc3263 I find kamailio dns resolver is not working as it should according RFC3263. http://tools.ietf.org/html/rfc3263 _If no NAPTR records are found, the client constructs SRV queries for those transport protocols it supports, and does a query for each._ So kamailio should query all (udp, tcp, tls, sctp whatever) protocols. Can anyone help/guide me to create a fix to this issue? My plan is to create a patch to kamailio resolver, to correct and behave according RFC3263. Any help or guidance appreciated! Thanks, Misi

11 years, 11 months

Kamailio v3.3.2 Released

by Daniel-Constantin Mierla

Hello, Kamailio SIP Server v3.3.2 stable release is out. This is a maintenance release of the latest stable branch, 3.3, that includes fixes since release of v3.3.1. There is no change to database schema or configuration language structure that you have to do on installations of v3.3.0 or v3.3.1. Deployments running previous v3.x.x versions are strongly recommended to be upgraded to v3.3.2. For more details about version 3.3.2 (including links and hints to download the tarball or from GIT repository), visit: * http://www.kamailio.org/w/2012/10/kamailio-v3-3-2-released/ RPM, Debian/Ubuntu packages will be available soon as well. Cheers, Daniel -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio Advanced Training, Berlin, Nov 5-8, 2012 - http://asipto.com/u/kat Kamailio Advanced Training, Miami, USA, Nov 12-14, 2012 - http://asipto.com/u/katu

11 years, 11 months

git:master: sca: support Record-Route

by Andrew Mortensen

Module: sip-router Branch: master Commit: 8632a265c3703e19cad9253f84527a913ee9cdd5 URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=8632a26… Author: Andrew Mortensen <admorten(a)isc.upenn.edu> Committer: Andrew Mortensen <admorten(a)isc.upenn.edu> Date: Fri Nov 30 14:42:19 2012 -0500 sca: support Record-Route - Save Record-Route values from SUBSCRIBEs to ensure NOTIFYs traverse correct path to subscriber. - Update SCA DB schema & creation scripts: add record_route column, increment sca_subscriptsion table version. --- lib/srdb1/schema/sca.xml | 7 +++ modules/sca/sca_db.c | 4 ++ modules/sca/sca_db.h | 6 ++- modules/sca/sca_notify.c | 25 ++++++++- modules/sca/sca_subscribe.c | 55 ++++++++++++++++++- modules/sca/sca_subscribe.h | 2 + .../kamctl/db_berkeley/kamailio/sca_subscriptions | 4 +- utils/kamctl/db_sqlite/sca-create.sql | 3 +- utils/kamctl/dbtext/kamailio/sca_subscriptions | 2 +- utils/kamctl/mysql/sca-create.sql | 3 +- utils/kamctl/oracle/sca-create.sql | 3 +- utils/kamctl/postgres/sca-create.sql | 3 +- 12 files changed, 103 insertions(+), 14 deletions(-) Diff: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commitdiff;h=863…

11 years, 11 months

git:master: core/corex: move send()/send_tcp() to corex module

by Richard Fuchs

Module: sip-router Branch: master Commit: 1da2a76be4e374ddb4296a1d54963fe344dc0970 URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=1da2a76… Author: Richard Fuchs <rfuchs(a)sipwise.com> Committer: Richard Fuchs <rfuchs(a)sipwise.com> Date: Fri Nov 30 14:00:09 2012 -0500 core/corex: move send()/send_tcp() to corex module As suggested by miconda on sr-dev, move send() and send_tcp() out of core and into the new corex module in order to make them support pseudo variables. This changes: - drops SEND and SEND_TCP tokens from config parser - remove related config parser code relying on SEND_T and SEND_TCP_T - augment corex module to provide the functions removed from core - update corex docs --- action.c | 74 ------------------------------- cfg.lex | 4 -- cfg.y | 22 --------- modules/corex/README | 44 ++++++++++++++++-- modules/corex/corex_lib.c | 87 +++++++++++++++++++++++++++++++++++++ modules/corex/corex_lib.h | 1 + modules/corex/corex_mod.c | 26 +++++++++++ modules/corex/doc/corex_admin.xml | 46 +++++++++++++++++++ modules/debugger/debugger_act.c | 2 - route.c | 2 - route_struct.c | 6 --- route_struct.h | 3 +- 12 files changed, 200 insertions(+), 117 deletions(-) Diff: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commitdiff;h=1da…

11 years, 11 months

SQLOPS / sql_xquery & $dbr(result=>rows)

by Brandon Armstead

Hello, There appears to be an issue with the exported pseudo variable $dbr(key=>rows). I am receiving rows back that are being populated into xavp via sql_xquery. However the result of $dbr(key=>rows) is zero. Perhaps I am doing something wrong or sql_xquery does not populate the $dbr pseudo variable? Thanks in advance. Sincerely, Brandon Armstead

11 years, 11 months

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

by Olle E. Johansson

Module: sip-router Branch: master Commit: cf97967489f1b61c5bf0a841f9f650e40fc9911e URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=cf97967… Author: Olle E. Johansson <oej(a)edvina.net> Committer: Olle E. Johansson <oej(a)edvina.net> Date: Thu Nov 29 22:01:05 2012 +0100 Merge branch 'master' of ssh://git.sip-router.org/sip-router * 'master' of ssh://git.sip-router.org/sip-router: kamctlrc: adding sca to the list of extra modules ---

11 years, 11 months

git:master: htable: Update documentation on mod-init

by Olle E. Johansson

Module: sip-router Branch: master Commit: 3376e3b8c54a7c9bc13f87368baeaaa145a9ced5 URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=3376e3b… Author: Olle E. Johansson <oej(a)edvina.net> Committer: Olle E. Johansson <oej(a)edvina.net> Date: Fri Nov 30 09:31:47 2012 +0100 htable: Update documentation on mod-init Based on Daniel's answer in sr-dev on a question about lua. The Lua environment is initialized in child processes, so it's not reachable in mod-init. --- modules_k/htable/README | 22 ++++++++++++---------- modules_k/htable/doc/htable_admin.xml | 5 +++-- 2 files changed, 15 insertions(+), 12 deletions(-) diff --git a/modules_k/htable/README b/modules_k/htable/README index a4e9155..ae0f786 100644 --- a/modules_k/htable/README +++ b/modules_k/htable/README @@ -309,7 +309,7 @@ modparam("htable", "htable", "c=>size=4;autoexpire=7200;initval=1;") Example 1.4. Set db_url parameter ... -modparam("htable", "db_url", "mysql://openser:openserrw@localhost/openser") +modparam("htable", "db_url", "mysql://kamailio:kamailiorw@localhost/kamailio") ... 3.3. key_name_column (str) @@ -431,7 +431,7 @@ modparam("htable", "db_expires", 1) 4.2. sht_rm_name_re(htable=>regexp) 4.3. sht_rm_value_re(htable=>regexp) -4.1. sht_print() +4.1. sht_print() Dump content of hash table to L_ERR log level. Intended for debug purposes. @@ -444,7 +444,7 @@ modparam("htable", "db_expires", 1) sht_print(); ... -4.2. sht_rm_name_re(htable=>regexp) +4.2. sht_rm_name_re(htable=>regexp) Delete all entries in the htable that match the name against regular expression. @@ -457,7 +457,7 @@ sht_print(); sht_rm_name_re("ha=>.*"); ... -4.3. sht_rm_value_re(htable=>regexp) +4.3. sht_rm_value_re(htable=>regexp) Delete all entries in the htable that match the value against regular expression. @@ -488,7 +488,7 @@ sht_rm_value_re("ha=>.*"); 6.2. sht_dump 6.3. sht_delete -6.1. sht_reload +6.1. sht_reload Reload a hash table from database. @@ -501,7 +501,7 @@ sht_rm_value_re("ha=>.*"); _hash_table_name_ _empty_line_ -6.2. sht_dump +6.2. sht_dump Dump content of a hash table via MI. @@ -514,7 +514,7 @@ sht_rm_value_re("ha=>.*"); _hash_table_name_ _empty_line_ -6.3. sht_delete +6.3. sht_delete Delete a key from a hash table via MI. @@ -537,11 +537,13 @@ sht_rm_value_re("ha=>.*"); 7.1. htable:mod-init -7.1. htable:mod-init +7.1. htable:mod-init When defined, the module calls event_route[htable:mod-init] after all - modules have been initialised. A typical use case is to initialise - items in hash tables. The event route is executed only once. + modules have been initialized. A typical use case is to initialise + items in hash tables. The event route is executed only once, after core + and module initialization, but before Kamailio forks any child + processes. ... event_route[htable:mod-init] { $sht(a=>x) = 1; diff --git a/modules_k/htable/doc/htable_admin.xml b/modules_k/htable/doc/htable_admin.xml index 32f51ce..b9e95ea 100644 --- a/modules_k/htable/doc/htable_admin.xml +++ b/modules_k/htable/doc/htable_admin.xml @@ -683,9 +683,10 @@ sht_rm_value_re("ha=>.*"); </title> <para> When defined, the module calls event_route[htable:mod-init] after - all modules have been initialised. A typical use case is to + all modules have been initialized. A typical use case is to initialise items in hash tables. The event route is executed only - once. + once, after core and module initialization, but before &kamailio; forks any + child processes. </para> <programlisting format="linespecific"> ...

11 years, 11 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev November 2012