sr-users October 2018

sr-users@lists.kamailio.org

81 participants
124 discussions

clang compiler warnings
by Juha Heinanen 05 Oct '18

05 Oct '18

I just made a test and, for sure, clang warns about unused variables: $ clang -Wunused-variable -I/usr/include/re -I/usr/include/baresip -lbaresip -lrem -lre baresip.c baresip.c:48:6: warning: unused variable 'unused' [-Wunused-variable] int unused; ^ 1 warning generated. -- Juha

3 3

Kamailio memory manager
by Igor Olhovskiy 05 Oct '18

05 Oct '18

Hi! What is the best way to debug messages like... 29(42) ERROR: [core/mem/q_malloc.c:290]: qm_find_free(): qm_find_free(0x7fad301cf010, 56); Free fragment not found! 29(42) ERROR: [core/mem/q_malloc.c:423]: qm_malloc(): qm_malloc(0x7fad301cf010, 56) called from core: core/data_lump.c: dup_lump_list_r(537), module: core; Free fragment not found! 29(42) ERROR: [core/data_lump.c:573]: dup_lump_list_r(): out of mem 29(42) ERROR: [core/data_lump.c:573]: dup_lump_list_r(): out of mem 29(42) ERROR: [core/data_lump.c:573]: dup_lump_list_r(): out of mem 29(42) ERROR: [core/data_lump.c:573]: dup_lump_list_r(): out of mem 29(42) ERROR: [core/data_lump.c:573]: dup_lump_list_r(): out of mem 29(42) ERROR: [core/data_lump.c:573]: dup_lump_list_r(): out of mem 29(42) ERROR: [core/data_lump.c:573]: dup_lump_list_r(): out of mem 29(42) ERROR: [core/data_lump.c:573]: dup_lump_list_r(): out of mem 29(42) ERROR: tm [t_fwd.c:1735]: t_forward_nonack(): failure to add branches Cause core.shmmem shows total: 536870912 free: 522859104 used: 12224144 real_used: 14011808 max_used: 14479048 fragments: 10560 Also mod.stats all pkg Module: core { init_io_wait(475): 6960 init_io_wait(524): 6312 new_db_id(272): 512 dupl_string_name(72): 32 db_do_init2(298): 488 mk_switch_cond_table(43): 144 sr_wtimer_add(330): 48 as_asciiz(161): 24 init_modules(1026): 16 rpc_hash_add(146): 2048 db_allocate_columns(150): 32 db_new_result(114): 56 get_hdr_field(116): 1160 db_allocate_columns(160): 16 cnt_hash_add(383): 1024 register_select_table(458): 48 add_callback(59): 320 sr_wtimer_init(308): 136 cfg_new_group(79): 704 cfg_declare(50): 3360 fix_sock_str(420): 480 init_dst_set(83): 32208 grp_hash_add(234): 808 fix_hostname(1301): 152 add_alias(91): 464 add_alias(93): 256 dupl_string(48): 176 parse_headers(325): 432 subst_parser(291): 144 subst_parser(274): 64 exp_optimize_right(411): 24 fix_expr(541): 600 mk_case_stm(3775): 400 fixup_regexp_null(213): 72 mk_elem(90): 560 route_new_list(200): 1344 fix_param(1196): 1336 parse_select(204): 1488 fix_param(1257): 536 fix_match_rve(3028): 320 mk_rval_expr1(2616): 142656 tr_new(1646): 1464 fixup_pvar_all(279): 1624 fix_param(1162): 16144 mk_action(118): 350168 mk_rval_expr2(2674): 489552 mk_rval_expr_v(2537): 1475600 yyparse(2757): 8792 pv_parse_format(1150): 89064 pv_cache_add(347): 31456 parse_params2(585): 1400 set_mod_param_regex(110): 376 set_mod_param_regex(121): 832 tr_table_add(1875): 400 sr_cmd_exports_convert(235): 36288 register_module(280): 6624 load_module(496): 2640 new_sock_info(235): 224 fix_socket_list(1509): 48 new_sock_info(230): 3920 add_alias(93): 56 add_alias(91): 96 yyparse(1774): 64 yyparse(667): 152 yyparse(2306): 128 yyparse(648): 144 sr_push_yy_state(1666): 32 sr_push_yy_state(1656): 104 sr_push_yy_state(1596): 184 addstr(1413): 415752 rpc_hash_add(100): 25656 str_hash_alloc(59): 512 pv_table_add(236): 17864 pv_init_buffer(2055): 327680 pv_init_buffer(2045): 320 init_nonsip_hooks(43): 24 init_rlist(146): 8 mk_rval_expr_v(2548): 1264 route_add(124): 5872 str_hash_alloc(59): 768 rval_get_str(1256): 56632 pp_define(1788): 2248 init_counters(122): 128 cnt_hash_add(332): 20608 str_hash_alloc(59): 1280 Total: 3602152 } Module: rtpengine { child_init(1812): 256 Total: 256 } Module: db_mysql { db_mysql_new_connection(65): 96 db_mysql_new_connection(75): 3040 Total: 3136 } Module: siptrace { mod_init(344): 384 Total: 384 } Module: sl { sl_register_callback(460): 88 Total: 88 } Module: acc { parse_acc_extra(116): 1512 Total: 1512 } Module: dialog { dlg_bridge_init_hdrs(66): 80 Total: 80 } Module: rr { register_rrcb(61): 80 Total: 80 } Module: db_text { dbt_get_columns(67): 64 Total: 64 } Module: permissions { get_pathname(242): 64 Total: 64 } Module: auth { generate_random_secret(239): 32 generate_random_secret(238): 32 Total: 64 } Module: xlog { mod_init(214): 4104 xdbg_fixup_helper(500): 6032 xlog_fixup_helper(535): 26992 Total: 37128 } Module: dmq { make_socket_str_from_uri(149): 24 Total: 24 } Module: sqlops { sqlops_tr_buffer_init(46): 2048 sql_init_con(83): 240 Total: 2288 } Module: textops { tr_txt_parse_re(212): 32 hname_fixup(3217): 768 fixup_method(3287): 1384 Total: 2184 } Module: pv { tr_parse_string(2343): 120 tr_parse_string(2332): 32 tr_parse_string(2378): 96 tr_parse_string(2368): 184 tr_parse_string(2544): 576 add_var(58): 3616 add_var(65): 1112 Total: 5736 } Module: textopsx { fixup_hname_param(598): 352 Total: 352 } Module: avpops { avpops_parse_pvar(57): 416 Total: 416 } Module: userblacklist { check_blacklist_fixup(522): 16 Total: 16 } Module: htable { fixup_ht_key(348): 176 pv_parse_ht_name(158): 520 Total: 696 } Module: dialplan { dp_trans_fixup(396): 296 Total: 296 } Module: dispatcher { Total: 0 } Module: tmx { Total: 0 } Module: tm { Total: 0 } Module: kex { Total: 0 } Module: usrloc { Total: 0 } Module: topos { Total: 0 } Module: utils { Total: 0 } Module: app_python { Total: 0 } Module: cfgutils { Total: 0 } Module: nathelper { Total: 0 } Where is the place to look at? Means what module can cause this? Regards, Igor

2 3

Astricon: OpenSource Soiree
by Giovanni Maruzzelli 05 Oct '18

05 Oct '18

Hello friends and collegues, A nice get together has been organized for evening Wednesday 10th at 7pm The idea is to have drinks and chitchat about opensource telephony and webrtc, and all opensource project founders, members, and practitioners are invited. Please join me, as distinguished participants too! Check it out at http://party.officering.com (no animals has been harmed in this mail) -giovanni -- Sincerely, Giovanni Maruzzelli OpenTelecom.IT cell: +39 347 266 56 18

2 2

Kamailio as TCP UDP proxy
by M K 05 Oct '18

05 Oct '18

Hi, I'm struggling with the configuration to use Kamailio as TCP UDP proxy: [SIP Client] <-(TCP)-> [Proxy] <-(UDP)-> [SIP Server] should be the setup. I only have one client and one SIP server. How do I get Kamailio configured as a proxy so that translation between TCP and UDP works (and vice versa)? I have not yet found any documentation and examples that have caused messages to arrive at my SIP server. I think I've been on the wrong track so far and I'm looking forward to any help. Thank you in advance, Laqoore

3 2

Development for Kamailio v5.2 series is frozen
by Daniel-Constantin Mierla 05 Oct '18

05 Oct '18

Hello, short note to mark the freezing of development for Kamailio v5.2 series. For few weeks, please do not push new features in the master branch. Once the branch 5.2 is created (expected to happen in 3-4 weeks from now), the master branch becomes again open for new feature. Meanwhile the focus has to be on testing current code. Work on related tools (e.g., kamctl) or documentation can still be done as well as getting the new modules in 5.2 in good shape, plus adding exports to kemi interface (which should not interfere with old code). The entire testing phase is expected to be 4 to 6 weeks, then the release of v5.2.0 will be out. Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - www.asipto.com Kamailio World Conference - www.kamailioworld.com

1 0

PATH when used with multiple listening ports
by Sergiu Pojoga 04 Oct '18

04 Oct '18

Hi again, When acting as an intermediary proxy for a non-colocated Registrar, the REGISTER request coming in on one port and going out on another, shouldn't the *add_path[received]()* generate *two* nodes in the Path header? Otherwise, how are the subsequent requests supposed to be routed back to the UAC? Scenario with Kamailio proxy on IP 1.1.1.1 with dual port listeners UAC => proxy:5070 <=> proxy:5060 => Registrar:5060 Path: <sip:1.1.1.1;lr;received=sip:123.123.123.123:59593> I would expect it to be something like: Path: <sip:1.1.1.1;lr>,<sip:1.1.1.1:5070;lr;received=sip: 123.123.123.123:59593> modparam("rr", "enable_double_rr", 1) modparam("path", "use_received", 1) Merci!

2 2

Kamailio in a mobile world - ts_append issue
by Dan Quinney 04 Oct '18

04 Oct '18

Using "Kamailio in a mobile world" as a base, I have the following routes to store information about the current transaction, however, if the transaction is already cancelled registrations for the user will still trigger `ts_append`, raising an error as the htable hasn't expired yet. Is there anyway to remove the htable entry when the original transaction cancels? Or something else that I'm missing?

2 1

Kamailio v5.1.6 Released
by Daniel-Constantin Mierla 04 Oct '18

04 Oct '18

Hello, Kamailio SIP Server v5.1.6 stable release is out. This is a maintenance release of the latest stable branch, 5.1, that includes fixes since the release of v5.1.5. There is no change to database schema or configuration language structure that you have to do on previous installations of v5.1.x. Deployments running previous v5.1.x versions are strongly recommended to be upgraded to v5.1.6. For more details about version 5.1.6 (including links and guidelines to download the tarball or from GIT repository), visit: * https://www.kamailio.org/w/2018/10/kamailio-v5-1-6-released/ RPM, Debian/Ubuntu packages will be available soon as well. Many thanks to all contributing and using Kamailio! Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - www.asipto.com Kamailio World Conference - www.kamailioworld.com

1 0

Roadmap to next major release - v5.2.0
by Daniel-Constantin Mierla 04 Oct '18

04 Oct '18

Hello, as it was discussed during our last IRC devel meeting before the summer, the time to release a new major version should be this autumn. With the Kamailio Developers Meeting planned for September 27-28, 2018, I think it is better to freeze the code couple of days after that event. So I propose the following milestones: * on Thursday, October 4, 2018 - last development day, code for 5.2.0 will be frozen at the end of the day * 4 to 6 weeks of testing * release sometime in November, to be decided more precisely after the first weeks of testing, some rough candidates being within the weeks of Nov 5 or Nov 19 If anyone has something to add or adjust, let's discuss on sr-users mailing list. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference -- www.kamailioworld.com Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com

2 3

Planing the release of Kamailio v5.1.6
by Daniel-Constantin Mierla 04 Oct '18

04 Oct '18

Hello, a matter of the schedule to be agreed in the morning and the availability during the Kamailio Developers Meeting, we may do a new stable release from branch 5.1.6 on Thursday, Sep 27, 2018, in the afternoon. Given that several of us will be in the same room, the special goal would be to try to automate the process as much as possible. If the time doesn't allow it, then the release will be done next week, a specific day to be decided by the end of this week. Anyhow, this is the informal notification to report as soon as possible any issues you are aware of and not yet in bug tracker, so they get a chance to be fixed. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference -- www.kamailioworld.com Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com

2 4

2026

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 October 2018