sr-users March 2019

sr-users@lists.kamailio.org

78 participants
101 discussions

kamailio 5.2.0 with empty table of rtpengine - kamailio doesn't start
by * Paolo Visintin - evosip.cloud 31 Mar '19

31 Mar '19

Hello, I noticed that , with kamailio ver. 5.2.1 starting with empty rtpengine table causes strange messages in kamailio and it doesn't start modparam("rtpengine", "db_url", "text:///tmp/kamailio/dbtext") cat /tmp/kamailio/dbtext/rtpengine id(int,auto) setid(int) url(string) weight(int) disabled(int) stamp(int) 0(2856) WARNING: tm [tm.c:760]: mod_init(): reparse_on_dns_failover is enabled on a multihomed host -- check the readme of tm module! 0(2856) WARNING: rtpengine [rtpengine_db.c:100]: rtpp_load_db(): No rtpproxy instances in database 0(2856) ERROR: rtpengine [rtpengine.c:2768]: select_rtpp_set(): no rtpp_set_list->rset_first 0(2856) NOTICE: rtpengine [rtpengine.c:1664]: mod_init(): Default rtpp set 0 NOT found 1(2857) NOTICE: usrloc [udomain.c:434]: preload_udomain(): filtered by server_id[0] 2(2858) ERROR: rtpengine [rtpengine.c:1722]: build_rtpp_socks(): no more pkg memory for rtpp_socks 2(2858) ERROR: <core> [core/sr_module.c:847]: init_mod_child(): error while initializing module rtpengine (/usr/lib/x86_64-linux-gnu/kamailio/modules/rtpengine.so) (idx: 2 rank: 2 desc: [udp receiver child=1 sock=172.28.0.120:5060]) 2(2858) ERROR: <core> [core/pt.c:342]: fork_process(): init_child failed for process 2, pid 2858, "udp receiver child=1 sock=172.28.0.120:5060" 2(2858) CRITICAL: <core> [main.c:1633]: main_loop(): Cannot fork 4(2860) ERROR: rtpengine [rtpengine.c:1722]: build_rtpp_socks(): no more pkg memory for rtpp_socks 4(2860) ERROR: <core> [core/sr_module.c:847]: init_mod_child(): error while initializing module rtpengine (/usr/lib/x86_64-linux-gnu/kamailio/modules/rtpengine.so) (idx: 4 rank: 4 desc: [udp receiver child=3 sock=172.28.0.120:5060]) 4(2860) ERROR: <core> [core/pt.c:342]: fork_process(): init_child failed for process 4, pid 2860, "udp receiver child=3 sock=172.28.0.120:5060" 4(2860) CRITICAL: <core> [main.c:1633]: main_loop(): Cannot fork any hint on what could be wrong ? (5.2.0 works perfectly) many thanks! Paolo

6 7

app_ruby - KSR::PV.sets method not found
by Andrew White 31 Mar '19

31 Mar '19

Hi all, I’m trying to set a pseudovariable via app_ruby. I’m able to retrieve pseudovariables using PV.gete as such: However trying to set these using sets, I get “No method found”: KSR::PV.sets("$fu", "sip:#{$uacs[trunk]['r_username']}@#{$uacs[trunk]['r_domain']}") Mar 30 04:44:59 ip-10-0-0-2 /usr/local/sbin/kamailio[28421]: ERROR: {1 102 INVITE 0fae8097312bec2b5ec79ada30c227e7@127.0.0.1:5060} app_ruby [app_ruby_api.c:107]: app_ruby_print_last_exception(): exception: undefined method `[]' for nil:NilClass PV.seti appears to work correctly. Am I calling the wrong method? Thanks! ________________________________ Andrew White - Director uConnected Email: andrew(a)uconnected.com.au Web: www.uConnected.com.au

2 4

Low %
by Loan Offer 30 Mar '19

30 Mar '19

Apply Now!!!

1 0

[--SPAM--] Low %
by Loan Offer 30 Mar '19

30 Mar '19

Apply Now!!!

1 0

Lost connection to MySQL server during query
by JR Richardson 29 Mar '19

29 Mar '19

Hey Folks, Getting some annoying logs, pretty certain these are false positives. I'm running kamailio 4.4.7 using localhost mysql 5.5.60 on debian 7.11. Pretty simple setup, have acc and collecting cdrs. Relevant kamailio.cfg: loadmodule "acc.so" loadmodule "rtimer.so" loadmodule "sqlops.so" # ----- acc params ----- modparam("acc", "db_url", DBURLRW) modparam("acc", "db_flag", 1) modparam("acc", "db_missed_flag", 2) modparam("acc", "db_extra", "src_user=$fU;src_domain=$fd;src_ip=$si;" "dst_ouser=$tU;dst_user=$rU;dst_domain=$rd;" "accountcode=$avp(s:acctcode)") modparam("rtimer", "timer", "name=cdr;interval=300;mode=1;") modparam("rtimer", "exec", "timer=cdr;route=CDRS") modparam("sqlops", "sqlcon", "cb=>mysql://rwuser:rwpass@localhost/kamailio") route[CDRS] { sql_query("cb","call kamailio_cdrs()","rb"); } Logs: ERROR: db_mysql [km_dbase.c:128]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) ERROR: <core> [db_query.c:181]: db_do_raw_query(): error while submitting query ERROR: sqlops [sql_api.c:265]: sql_do_query(): cannot do the query [call kamailio_cdrs()] CDRs are working fine, no issues with the results, just the log messages. Errors occur every 5 minutes so this is related to the rtimer cycle, mode=1 is set for new connection so there really wouldn't be a lost connection, the old connection should have been relieved on last cycle. I've seen some other post talking about this issue but could not find any resolution or work around. Any help is appreciated. Thanks. JR -- JR Richardson Engineering for the Masses Chasing the Azeotrope

3 3

log timestamp granularity
by Patrick Murphy 28 Mar '19

28 Mar '19

Hello - Is there a way I can print current timestamp in milli or microseconds in the log file? Something like: 2019-03-28 04:50:15.379 would be ideal The closest thing I could find was $TV(Sn) but it doesn't suit the purpose here since its not human readable. Thanks Pat

2 1

flags definition in kamailio.cfg + 5.2 documentation
by Joel Serrano 27 Mar '19

27 Mar '19

Hi, I saw in the Kazoo default.cfg this: ... ####### Flags ####### flags FLAG_INTERNALLY_SOURCED: 1, FLAG_ASSOCIATE_SERVER: 2, FLAG_SKIP_NAT_CORRECTION: 3, FLAG_ASSOCIATE_USER: 4, FLAG_TRUSTED_SOURCE: 5, FLAG_SESSION_PROGRESS: 6, FLAG_IS_REPLY: 7, FLAG_SIP_TRACE: 8; ... So then I went here to read about it: https://www.kamailio.org/wiki/cookbooks/5.2.x/core#flags I found out it's not documented... is this a drop-in alternative for a: #!define FLAG_NAME FLAG_BIT? Sorry, first time I see this if not I would update the docs myself... :( Thanks, Joel.

4 8

Uri's user part parameters
by Duarte Rocha 27 Mar '19

27 Mar '19

Greetings, Does Kamailio have a way of identifying the user-part parameters of an URI? I have situations where i have sip:user;parameter=yes@host. Best Regards, Duarte Rocha

2 1

Manipulating User Agent header in dispatcher OPTIONS
by Andrew White 27 Mar '19

27 Mar '19

Hi all, I’ve set the server_header variable in my primary config, and I’ve got a catch in the default reply route to modify headers where required. I’m masking this value for security reasons, and filling it with my own value for vanity reasons :). I’ve noticed that the OPTIONS packet that is send via the dispatcher module when probing mode is on contains a User-Agent field which has the full version and OS type. Unfortunately I don’t necessarily have trust of the end destination being dispatcher to, nor the packet switchers in-between. How can I catch this OPTIONS packet to manipulate the value? It doesn’t appear to go through the REQUEST route or the ONSEND route. Thanks! ________________________________ Andrew White - Director uConnected Email: andrew(a)uconnected.com.au Web: www.uConnected.com.au

2 2

accounting and db_redis
by Daniel Tryba 27 Mar '19

27 Mar '19

Under https://www.kamailio.org/docs/modules/5.2.x/modules/db_redis.html#db_redis.… there is an example for using db_redis for accounting. This doesn't appear to work (5.2.2) modparam("db_redis", "keys", "acc=entry:callid,time_hires&cid:callid") results in: db_redis [redis_dbase.c:1886]: db_redis_insert(): inserting to prefix (table) 'acc' db_redis [redis_dbase.c:382]: db_redis_build_entry_keys(): build entry keys db_redis [redis_dbase.c:295]: db_redis_find_query_key(): checking for existence of ent db_redis [redis_dbase.c:306]: db_redis_find_query_key(): found key in entry key db_redis [redis_dbase.c:133]: db_redis_val2str(): converting str value '1db9c0bc57291e db_redis [redis_dbase.c:338]: db_redis_find_query_key(): entry key so far is 'acc:entr db_redis [redis_dbase.c:295]: db_redis_find_query_key(): checking for existence of entry key 'time_hires' in query db_redis [redis_dbase.c:346]: db_redis_find_query_key(): key 'time_hires' for type 'entry' not found, unable to use this type db_redis [redis_dbase.c:405]: db_redis_build_entry_keys(): Failed to create direct entry key, no matching key definition db_redis [redis_dbase.c:1892]: db_redis_insert(): failed to build entry keys db_redis [redis_dbase.c:1976]: db_redis_insert(): failed to do the insert What does work is "time" instead of "time_hires". Since I have no idea what values are available (I guess the table names?) and time only has a 1 sec resolution, what is a correct version of time_hires?

1 2

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users March 2019