sr-dev May 2009

sr-dev@lists.kamailio.org

26 participants
263 discussions

symbols not found
by jh＠tutpro.com 01 Jun '09

01 Jun '09

dpkg-shlibdeps complains about lots of symbols that it cannot find, for example: dpkg-shlibdeps: warning: symbol core_cfg used by debian/sip-router/usr/lib/sip-router/libkmi.so.1.0 found in none of the libraries. ... dpkg-shlibdeps: warning: symbol core_cfg used by debian/sip-router/usr/lib/sip-router/libsrdb2.so.1.0 found in none of the libraries. ... dpkg-shlibdeps: warning: symbol mem_lock used by debian/sip-router/usr/lib/sip-router/libkcore.so.1.0 found in none of the libraries. should i get worried about that? am i missing some libraries? --juha

2 3

how to turn off debug?
by jh＠tutpro.com 01 Jun '09

01 Jun '09

when i run /usr/sbin/sip-router -c -d -f /etc/sip-router/sip-router.cfg i still get lots of debug messages. how to start sip-router so that it only prints warning and errors? -- juha

3 5

return($retcode) gives syntax error
by jh＠tutpro.com 01 Jun '09

01 Jun '09

here is one more: return($retcode); 0(6768) : <core> [cfg.y:2921]: parse error in config file, line 2905, column 17: syntax error 0(6768) : <core> [cfg.y:2921]: parse error in config file, line 2905, column 17: ==, !=, <,>, >= or <= expected -- juha

2 1

onreply_avp_mode tm param is missing
by jh＠tutpro.com 01 Jun '09

01 Jun '09

i got all my modules loaded. first error while processing my config was this: 0(18354) DEBUG: <core> [sr_module.c:616]: find_param_export: parameter <onreply _avp_mode> not found in module <tm> 0(18354) ERROR: <core> [modparam.c:143]: set_mod_param_regex: parameter <onrepl y_avp_mode> not found in module <tm> 0(18354) : <core> [cfg.y:2921]: parse error in config file, line 407, column 37 : Can't set module parameter migration tips doesn't tell yet, how to solve this. -- juha

3 4

Planning for new functionality for kamailio
by Vadim Lebedev 01 Jun '09

01 Jun '09

Hello, I'd like to discuss some new functionaity for Kamailio i intend to develop for a client. My client need to integrate very specific transport security layer... The layer will function over tcp and udp and will be intgreated into the SSL framework The client will provide a function returning SSL_METHOD * descritptor So what i need to do is 1) Add possibility to use SSL over udp socket 2) To use a new SSL method So my first question is: Is there any chance that such functionality will be accepted into the main trunk of kamailio? Thanks Vadim

3 3

[RtpProxy] debian init patch to be LSB compliant
by Iñaki Baz Castillo 31 May '09

31 May '09

Hi, I attach a ptch for rtpproxy Debian init script which allows it being LSB compliant. Basically I add "--oknodo" option to all calls to "start-stop-daemon" which, by default, is not LSB compliant. Being LSB compliant is really useful when we want to manage a service (like RtpProxy) using some failover system as HeartBeat, which relies on *exact* reply code of the init scripts. About LSB specification [1] for init scripts which I refer to: --------------------- "For all other init-script actions, the init script shall return an exit status of zero if the action was successful. Otherwise, the exit status shall be non-zero, as defined below. In addition to straightforward success, the following situations are also to be considered successful: - Restarting a service (instead of reloading it) with the force-reload argument - Running start on a service already running - Running stop on a service already stopped or not running - Running restart on a service already stopped or not running - Running try-restart on a service already stopped or not running" So if I start a service that is already running I should receive 0, but "start-stop-daemon" returns 1 (error). The option "--oknodo" changes the behaviour to the LSB recomendations but many services in Debian don't use this option and return 1 in the case I've quotted. This is very problematic for me when I try to use a Debian service init script with HeartBeat that expects to receive a 0. ----------------------- So adding "--oknodo" to the init script, "/etc/init.d/rtpproxy start" returns 0 (no error) even if RtpProxy is already running, and "/etc/init.d/rtpproxy stop" returns 0 (no error) even if RtpProxy is not running (as LSB mandates). Note however that in Debian Lenny the default behaviour of "start-stop-daemon" has changed to implement this LSB compliant behaviour by default. This is the bug report I opened in Debian for this issue: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=426877 [1] LSB specifications about init script actions: http://www.linux-foundation.org/spec/refspecs/LSB_3.0.0/LSB-Core-generic/LS… Core-generic/iniscrptact.html -- Iñaki Baz Castillo <ibc(a)aliax.net>

1 0

[rtpproxy module] set_rtp_proxy_set() to allow pv as parameter
by Iñaki Baz Castillo 31 May '09

31 May '09

Hi, using multiple RtpProxy instancies would be more flexible if set_rtp_proxy_set() allows a pseudo-variable instead of just a fixed integer. Without this feature, it's impossible to implement real RtpProxy loadbalancing since: how to use the same RtpProxy for an in-dialog request? Let me show an example: - Let's suppose we have these rtpproxies: modparam("nathelper", "rtpproxy_sock", "1 == udp:1.1.1.1:12221") modparam("nathelper", "rtpproxy_sock", "2 == udp:2.2.2.2:12221") (note that I don't use various rtpproxies in the same set since with the, real loadbalancing it's not possible). - An INVITE arrives and we want to use a ramdom rtpproxy (set 1 or 2). Since set_rtp_proxy_set() doesn't allow pv, the only way is something as computing the from_tag or call-id and get values 0 or 1 (or 1 or 2). In the first case we invoke set_rtp_proxy_set("1") and in the second set_rtp_proxy_set("2"). - When processing the 183/200 response we should do the same (get 1 or 2 from the from_tag or call-id), or perhaps add a parameter in RR (rtpproxy_set=1) and invoke the corresponding set_rtp_proxy_set() function. - The same for every in-dialog request (re-INVITE, BYE...). I understand that this mechanims is not really scalable since adding a new rtpproxy requires modifications in the kamailio script (the ramdom function which now should return 1, 2 or 3 depending on the call-id/from_tag hash or something similar) and also adding a new "else if (XXXXX) { set_rtp_proxy_set("3") ... }" So, extending set_rtp_proxy_set() to allow pv would mitigate this issue: - When the INVITE arrives a ramdom function returns 1,2,3..., we store that value in a pv and use it into set_rtp_proxy_set(). - We also store that value in a RR param to retrieve it in replies and in- dialog requests in order to invoke the samertpproxy set. About various rtpproxy instances per set: I consider there is no solution for it. If we have: # multiple rtproxies for LB modparam("nathelper", "rtpproxy_sock", "udp:localhost:12221 udp:localhost:12222") We invoke "rtpproxy_offer" and some rtpproxy has been transparently selected, but we CANNOT know which one, so, how to reuse it in the reply and in-dialog requests?? I remember a thread about it in which the code was inspected and some "hash algorithm" resulted to take place to select the rtpproxy instance. However I remember that this algorithm is not so robust as required for a real loadbalancing system. So, in conclusion, is there any aim in improving RtpProxy module to allow real and robust load-balancing? What about multiple rtpproxy instances in the same set? is it really usable? Thanks a lot for any comment on it. -- Iñaki Baz Castillo <ibc(a)aliax.net>

1 0

[rtpproxy] ERR:create_twinlistener: unable to set TOS to 184: Operation not permitted
by Iñaki Baz Castillo 31 May '09

31 May '09

Hi, when rtpproxy is running as non root user, it gives this error for each request (anyway it doesn't fail): ERR:create_twinlistener: unable to set TOS to 184: Operation not permitted I've not checked it running as root however. How could I avoid this error? I don't see options in rtpproxy to dissable the TOS modification. -- Iñaki Baz Castillo <ibc(a)aliax.net>

2 6

git:master: tm: doc - added note about tmx module
by Daniel-Constantin Mierla 30 May '09

30 May '09

Module: sip-router Branch: master Commit: bb8a054005373f8c78ca480435b7db2a7a8b3676 URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=bb8a054… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: Sat May 30 17:40:17 2009 +0300 tm: doc - added note about tmx module - indication that some functionalities of K tm are now in tmx --- modules/tm/README | 94 +++++++++++++++++++++++++++++++++++++++++++++++++ modules/tm/doc/tm.xml | 5 +++ 2 files changed, 99 insertions(+), 0 deletions(-) diff --git a/modules/tm/README b/modules/tm/README index 9d489a5..ecee53b 100644 --- a/modules/tm/README +++ b/modules/tm/README @@ -15,6 +15,94 @@ Juha Heinanen Revision $Revision$ $Date$ __________________________________________________________________ + 1.1. Overview + 1.2. Known Issues + 1.3. Parameters + + 1.3.1. fr_timer (integer) + 1.3.2. fr_inv_timer (integer) + 1.3.3. max_inv_lifetime (integer) + 1.3.4. max_noninv_lifetime (integer) + 1.3.5. wt_timer (integer) + 1.3.6. delete_timer (integer) + 1.3.7. retr_timer1 (integer) + 1.3.8. retr_timer2 (integer) + 1.3.9. noisy_ctimer (integer) + 1.3.10. restart_fr_on_each_reply (integer) + 1.3.11. auto_inv_100 (integer) + 1.3.12. auto_inv_100_reason (string) + 1.3.13. unix_tx_timeout (integer) + 1.3.14. aggregate_challenges (integer) + 1.3.15. reparse_invite (integer) + 1.3.16. ac_extra_hdrs (string) + 1.3.17. blst_503 (integer) + 1.3.18. blst_503_def_timeout (integer) + 1.3.19. blst_503_min_timeout (integer) + 1.3.20. blst_503_max_timeout (integer) + 1.3.21. blst_methods_add (unsigned integer) + 1.3.22. blst_methods_lookup (unsigned integer) + 1.3.23. cancel_b_method (integer) + 1.3.24. reparse_on_dns_failover (integer) + 1.3.25. on_sl_reply (string) + 1.3.26. fr_inv_timer_next (integer) + 1.3.27. contacts_avp (string) + + 1.4. Functions + + 1.4.1. t_relay_to_udp(ip, port), t_relay_to_udp(), + t_relay_to_tcp(ip, port) t_relay_to_tcp() + t_relay_to_tls(ip, port) t_relay_to_tls() + t_relay_to_sctp(ip, port) t_relay_to_sctp() + + 1.4.2. t_relay() t_relay(host, port) + 1.4.3. t_on_failure(failure_route) + 1.4.4. t_on_reply(onreply_route) + 1.4.5. t_on_branch(branch_route) + 1.4.6. append_branch() + 1.4.7. t_newtran() + 1.4.8. t_reply(code, reason_phrase) + 1.4.9. t_lookup_request() + 1.4.10. t_retransmit_reply() + 1.4.11. t_release() + 1.4.12. t_forward_nonack() t_forward_nonack(ip, port) + t_forward_nonack_udp(ip, port) t_forward_nonack_tcp(ip, + port) t_forward_nonack_tls(ip, port) + t_forward_nonack_sctp(ip, port) + + 1.4.13. t_set_fr(fr_inv_timeout [, fr_timeout]) + 1.4.14. t_reset_fr() + 1.4.15. t_set_max_lifetime(inv_lifetime, noninv_lifetime) + 1.4.16. t_reset_max_lifetime() + 1.4.17. t_set_retr(retr_t1_interval, retr_t2_interval) + 1.4.18. t_reset_retr() + 1.4.19. t_set_auto_inv_100(0|1) + 1.4.20. t_branch_timeout() + 1.4.21. t_branch_replied() + 1.4.22. t_any_timeout() + 1.4.23. t_any_replied() + 1.4.24. t_grep_status("code") + 1.4.25. t_is_canceled() + 1.4.26. t_is_expired() + 1.4.27. t_relay_cancel() + 1.4.28. t_lookup_cancel(), t_lookup_cancel(1) + 1.4.29. t_drop_replies() + 1.4.30. t_save_lumps() + 1.4.31. t_load_contacts() + 1.4.32. t_next_contacts() + + 1.5. TM Module API + + 1.5.1. Defines + 1.5.2. Functions + + 1.5.2.1. register_tmcb(cb_type, cb_func) + 1.5.2.2. load_tm(*import_structure) + 1.5.2.3. int t_suspend(struct sip_msg *msg, unsigned int + *hash_index, unsigned int *label) + + 1.5.2.4. int t_continue(unsigned int hash_index, unsigned + int label, struct action *route) + 1.1. Overview TM module enables stateful processing of SIP transactions. The main use @@ -64,6 +152,12 @@ Juha Heinanen timeouts, forking, etc. See t_uac prototype in uac.h for more details. Who wants to see the transaction result may register for a callback. +Note + + Several Kamailio (OpenSER) TM module functionalities are now + implemented in the TMX module: "modules_k/tmx". Check it to see if what + you are looking for is there. + 1.2. Known Issues * Possibly, performance could be improved by not parsing non-INVITEs, diff --git a/modules/tm/doc/tm.xml b/modules/tm/doc/tm.xml index 2ee419c..64134ff 100644 --- a/modules/tm/doc/tm.xml +++ b/modules/tm/doc/tm.xml @@ -98,6 +98,11 @@ See t_uac prototype in uac.h for more details. Who wants to see the transaction result may register for a callback. </para> + <note> + <para>Several Kamailio (OpenSER) TM module functionalities are now + implemented in the TMX module: <quote>modules_k/tmx</quote>. Check + it to see if what you are looking for is there.</para> + </note> </section> <section id="tm.known_issues">

1 0

i: and s: avp syntax
by jh＠tutpro.com 30 May '09

30 May '09

i'm getting lots of these: 0(13997) WARNING: <core> [usr_avp.c:882]: i: and s: avp name syntax is deprecated! and didn't find anything about that on tips page. where is the new avp name syntax explained? modules_k/avpops/README still has this: * avp_flags = type_flags [script_flags]; type_flags = 'I' | 'i' | 'S' | 's'; script_flags = 0..255 'I' or 'i' means that the type of avp name is integer (ID) 'S' or 's' means that the type of avp name is string The type flag is mandatory. -- juha

2 7

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev May 2009