sr-dev October 2019

sr-dev@lists.kamailio.org

22 participants
436 discussions

[kamailio/kamailio] Extend rtpengine hashing algorithms (#1986)

by Ionut Ionita

#### Pre-Submission Checklist    - [ ] Commit message has the format required by CONTRIBUTING guide - [ ] Commits are split per component (core, individual modules, libs, utils, ...) - [ ] Each component has a single commit (if not, squash them into one commit) - [ ] No commits to README files for modules (changes must be done to docbook files in `doc/` subfolder, the README file is autogenerated) #### Type Of Change - [ ] Small bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds new functionality) - [ ] Breaking change (fix or feature that would change existing functionality) #### Checklist:  - [ ] PR should be backported to stable branches - [ ] Tested changes locally - [ ] Related to issue #1911 #### Description  The goal was to have a different, more complex hashing algorithm that would offer a better distribution among nodes. We've seen in production that the current algorithm does not perform well under heavy load therefore we decided to add SHA1 hashing. After running performance tests we've decided that we need a cryptographic function in order to have the best results mostly when the callids have small entropy. In order to add SHA1, a new API was added in crypto module exporting a function applying SHA1 to a string. The API was used in rtpengine module over the callid. After this operation the hash was calculated as before except for applying 0xFF mask over the hash as it was done before, which restrains the power of this algorithm. You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/1986 -- Commit Summary -- * crypto: add exportable API and expose SHA1 hashing function * rtpengine: use SHA1 over callid for better distribution among nodes * rtpengine: add modparam to switch between legacy hashing algorithm and SHA1 * rtpengine: update README -- File Changes -- A src/modules/crypto/api.c (30) A src/modules/crypto/api.h (63) M src/modules/crypto/crypto_mod.c (2) M src/modules/crypto/crypto_uuid.c (34) M src/modules/crypto/crypto_uuid.h (8) M src/modules/rtpengine/doc/rtpengine_admin.xml (25) M src/modules/rtpengine/rtpengine.c (53) M src/modules/rtpengine/rtpengine.h (1) -- Patch Links -- https://github.com/kamailio/kamailio/pull/1986.patch https://github.com/kamailio/kamailio/pull/1986.diff -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/1986

3 years, 8 months

[kamailio/kamailio] Kamailio memory leak - versions 5.1.4 and 5.1.7 (#1895)

by Jay J

### Description Kamailio runs out of memory and stops processing requests. ``` ERROR: <core> [core/tcp_main.c:973]: tcpconn_new(): mem. allocation failure ERROR: <core> [core/tcp_main.c:4042]: handle_new_connect(): tcpconn_new failed, closing socket ERROR: uac [uac_reg.c:533]: reg_ht_add(): no more shm ERROR: uac [uac_reg.c:1347]: uac_reg_load_db(): Error adding reg to htable ``` ### Troubleshooting Restarting the Kamailio process resolves the issue #### Reproduction The issue occurs every 48 hours or so on the Kamailio instance #### Debugging Data ``` #kamcmd mod.stats all pkg Module: core { init_io_wait(475): 6480 init_dst_set(83): 32208 init_io_wait(524): 3576 yyparse(1782): 8 mk_new_net(52): 48 fix_param(1196): 128 route_new_list(200): 352 fix_expr(541): 616 exp_optimize_right(411): 40 fixup_regexp_null(213): 216 fix_param(1257): 352 yyparse(2729): 4872 mk_rval_expr1(2616): 68256 mk_elem(90): 976 mk_rval_expr2(2674): 321160 mk_rval_expr_v(2548): 768 mk_rval_expr_v(2537): 808136 mk_action(118): 196384 parse_params2(585): 560 set_mod_param_regex(121): 848 set_mod_param_regex(110): 264 tr_table_add(1875): 400 sr_cmd_exports_convert(235): 34160 register_module(280): 6192 load_module(496): 2072 new_sock_info(235): 176 new_sock_info(230): 3640 yyparse(642): 352 yyparse(1732): 288 add_alias(93): 80 add_alias(91): 128 yyparse(1446): 8 yyparse(2262): 296 yyparse(661): 416 subst_str(514): 416 subst_parser(301): 264 subst_parser(291): 2384 subst_parser(274): 960 pp_subst_add(57): 312 pp_define(1766): 1096 addstr(1399): 261168 str_hash_alloc(59): 512 pv_table_add(236): 22616 parse_pvname_list(1515): 2496 tr_new(1646): 1512 fix_match_rve(3028): 2152 pv_cache_add(347): 20664 fix_param(1162): 18936 init_modules(1026): 16 cnt_hash_add(383): 2048 db_do_init2(299): 336 dupl_string_name(72): 32 dupl_string(48): 144 new_db_id(272): 288 get_abs_pathname(262): 80 rpc_hash_add(146): 2048 pv_parse_format(1150): 40592 get_hdr_field(116): 232 parse_headers(320): 64 register_select_table(458): 104 rpc_hash_add(100): 26264 add_callback(59): 288 sr_wtimer_init(308): 136 cfg_new_group(79): 1160 cfg_declare(50): 4120 fix_socket_list(1509): 96 fix_sock_str(420): 912 fix_hostname(1301): 160 grp_hash_add(234): 952 pv_init_buffer(2055): 163840 pv_init_buffer(2045): 320 init_nonsip_hooks(43): 24 init_rlist(146): 40 route_add(124): 1784 str_hash_alloc(59): 768 rval_get_str(1256): 33648 init_counters(122): 128 cnt_hash_add(332): 26352 str_hash_alloc(59): 1280 Total: 2138200 } Module: ndb_redis { redis_parse_index(627): 88 pv_parse_redisc_name(704): 16496 redisc_add_server(257): 24064 Total: 40648 } Module: pv { tr_parse_string(2340): 64 tr_parse_string(2310): 192 tr_parse_string(2300): 192 tr_parse_string(2360): 32 tr_parse_string(2264): 544 add_var(65): 512 add_var(58): 2080 tr_parse_string(2275): 496 tr_parse_paramlist(2668): 32 Total: 4144 } Module: sqlops { sql_get_result(200): 64 pv_parse_dbr_name(134): 864 sql_init_con(83): 240 sqlops_tr_buffer_init(46): 2048 Total: 3216 } Module: textops { tr_txt_parse_re(212): 96 hname_fixup(2819): 616 fixup_method(2889): 1256 Total: 1968 } Module: xhttp_rpc { child_init(789): 832 Total: 832 } Module: db_mysql { db_mysql_new_connection(75): 4088 db_mysql_new_connection(65): 96 Total: 4184 } Module: auth { generate_random_secret(239): 32 generate_random_secret(238): 32 Total: 64 } Module: htable { pv_parse_ht_name(158): 160 fixup_ht_key(339): 88 Total: 248 } Module: xlog { xlog_fixup_helper(535): 17472 mod_init(214): 4104 xdbg_fixup_helper(500): 3352 Total: 24928 } Module: cnxcc { __alloc_redis(149): 24 __alloc_redis(146): 40 Total: 64 } Module: rtpengine { build_rtpp_socks(1611): 8 child_init(1768): 240 Total: 248 } Module: mangler { compile_expresions(557): 64 compile_expresions(541): 64 Total: 128 } Module: acc { parse_acc_extra(116): 672 Total: 672 } Module: rr { register_rrcb(61): 32 Total: 32 } Module: dialog { dlg_bridge_init_hdrs(66): 80 Total: 80 } Module: tm { Total: 0 } Module: uac { Total: 0 } Module: tls { Total: 0 } Module: sl { Total: 0 } Module: tmx { Total: 0 } Module: kex { Total: 0 } Module: usrloc { Total: 0 } Module: pike { Total: 0 } Module: websocket { Total: 0 } Module: cfgutils { Total: 0 } Module: nathelper { Total: 0 } Module: dispatcher { Total: 0 } ``` #### Log Messages ``` kamailio[6722]: ERROR: <core> [core/tcp_main.c:973]: tcpconn_new(): mem. allocation failure kamailio[6722]: ERROR: <core> [core/tcp_main.c:4042]: handle_new_connect(): tcpconn_new failed, closing socket kamailio[6722]: ERROR: tm [t_msgbuilder.c:1594]: build_uac_req(): no more shared memory (544) ``` ### Possible Solutions Restarting Kamailio ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` version: kamailio 5.1.7 (x86_64/linux) 567df3 flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144 MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: 567df3 compiled on 04:30:41 Mar 14 2019 with gcc 7.3.0 ``` * **Operating System**: ``` cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.2 LTS" ``` ``` 4.15.0-1034-aws #36-Ubuntu SMP Tue Mar 5 23:17:16 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux ``` ``` cat /proc/meminfo MemTotal: 4038176 kB MemFree: 130020 kB MemAvailable: 747324 kB Buffers: 15136 kB Cached: 2851248 kB SwapCached: 0 kB Active: 930936 kB Inactive: 2672836 kB Active(anon): 737672 kB Inactive(anon): 2097272 kB Active(file): 193264 kB Inactive(file): 575564 kB Unevictable: 0 kB Mlocked: 0 kB SwapTotal: 0 kB SwapFree: 0 kB Dirty: 120 kB Writeback: 0 kB AnonPages: 734064 kB Mapped: 2180672 kB Shmem: 2097544 kB Slab: 154288 kB SReclaimable: 101108 kB SUnreclaim: 53180 kB KernelStack: 4176 kB PageTables: 81940 kB NFS_Unstable: 0 kB Bounce: 0 kB WritebackTmp: 0 kB CommitLimit: 2019088 kB Committed_AS: 4529756 kB VmallocTotal: 34359738367 kB VmallocUsed: 0 kB VmallocChunk: 0 kB HardwareCorrupted: 0 kB AnonHugePages: 0 kB ShmemHugePages: 0 kB ShmemPmdMapped: 0 kB CmaTotal: 0 kB CmaFree: 0 kB HugePages_Total: 0 HugePages_Free: 0 HugePages_Rsvd: 0 HugePages_Surp: 0 Hugepagesize: 2048 kB DirectMap4k: 221184 kB DirectMap2M: 3973120 kB ``` Also, here is the output of "grep alloc qm_status.txt | awk '{ print substr( $0, 16, length($0) ) }' | sort | uniq -c | sort -k1n" (as per https://www.kamailio.org/wiki/tutorials/troubleshooting/memory): https://www.dropbox.com/s/act3whe6gumyzvj/alloc.txt?dl=1 -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/1895

3 years, 8 months

[kamailio/kamailio] app_java.so: undefined symbol: JNI_CreateJavaVM please help (#1969)

by xevilstar

### Description  ### Troubleshooting #### Reproduction  #### Debugging Data  ``` (paste your debugging data here) ``` #### Log Messages  ``` (paste your log messages here) ``` #### SIP Traffic  ``` (paste your sip traffic here) ``` ### Possible Solutions  ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` (paste your output here) ``` * **Operating System**:  ``` (paste your output here) ``` -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/1969

3 years, 8 months

[kamailio/kamailio] t_set_fr only works with UDP (#1966)

by Boden Garman

3 years, 8 months

[kamailio/kamailio] RPM repos at https://rpm.kamailio.org (#2084)

by Daniel-Constantin Mierla

Build own repositories for RPM packages for various distros: CentOS, RedHate, OpenSuse ... -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/2084

3 years, 8 months

[kamailio/kamailio] rtpengine module is not retrying for rtpengine_offer. retry is working for rtpengine_answer and rtpengine_delete (#1696)

by Surendra Tiwari

### Description we are using rtpengine with kamailio [KSR-LUA]. kamailio sending the rtpengine_offer to rtpengine. If kamailio didn't get the response from the rtpengine then it's not retrying . for rtpengine_answer and rtpengine_delete retry is working pretty good. we are using following rtpengine configuration # ----- rtpengine params ----- modparam("rtpengine", "db_url", DBURL) modparam("rtpengine", "table_name" , "rtpengine") modparam("rtpengine", "rtpengine_allow_op", 1) modparam("rtpengine", "queried_nodes_limit", 4) modparam("rtpengine", "rtpengine_retr", 2) modparam("rtpengine", "rtp_inst_pvar", "$avp(RTP_INSTANCE)") modparam("rtpengine", "setid_default", 1) modparam("rtpengine", "rtpengine_tout_ms", 400)  ### Troubleshooting #### Reproduction This issue can be reproduced by above configuration. and need to use rtpengine_offer,rtpengine_answer and rtpengine_delete with ksr lua routing.  #### Debugging Data  ``` (paste your debugging data here) ``` #### Log Messages  ``` (paste your log messages here) ``` #### SIP Traffic  ``` (paste your sip traffic here) ``` ### Possible Solutions  ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` version: kamailio 5.1.4 (x86_64/linux) a1df59 flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: a1df59 compiled on 06:23:23 Oct 30 2018 with gcc 4.8.4 ``` * **Operating System**:  ``` root@ip-172-31-4-160:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 14.04.5 LTS Release: 14.04 Codename: trusty root@ip-172-31-4-160:~# uname -a Linux ip-172-31-4-160 3.13.0-143-generic #192-Ubuntu SMP Tue Feb 27 10:45:36 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux ``` -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/1696

3 years, 8 months

[kamailio/kamailio] Active dialog stats stays static on a passive kamailio node that replicates dialogs via DMQ (#1692)

by Joel Serrano

### Description In a setup with 2 kamailios in active/passive with a virtual IP that failovers between them: sbc01 (active) is handling calls. sbc02 (passive) is started, and does an initial dialog sync via DMQ ``` root@sbc01:~# kamctl rpc stats.get_statistics all | grep dialog "dialog:active_dialogs = 39", "dialog:early_dialogs = 2", "dialog:expired_dialogs = 0", "dialog:failed_dialogs = 583", "dialog:processed_dialogs = 2527", root@sbc01:~# ``` ``` root@sbc02:/etc/kamailio# kamctl rpc stats.get_statistics all | grep dialog "dialog:active_dialogs = 39", "dialog:early_dialogs = 0", "dialog:expired_dialogs = 0", "dialog:failed_dialogs = 0", "dialog:processed_dialogs = 0", root@sbc02:/etc/kamailio# ``` >From that point onwards, as long as sbc01 stays as active, sbc02 stays as passive, and no restarts occur anywhere, the values for `dialog` metrics in sbc02 will not change and remain as they are, in the previous example, active_dialogs would remain as 39. ### Troubleshooting This was discovered during some tests from #1591 #### Reproduction Setup 2 kamailio instances that replicate dialogs via DMQ. 1- On Kamailio1 put some traffic to have some active dialogs (must call `dlg_manage()` in routing script for these test calls) 2- Start Kamailio2 3- Compare output of: `kamcmd stats.get_statistics dialog:` on both nodes. 4- Alter the amount of active dialogs on Kamailio1 (either end some or create new ones). 5- Repeat step 3. Kamailio1 --> Step5 will have different values from Step3. Kamailio2 --> Step5 will have exactly the same values from Step3. ### Possible Solutions `dialog:active_dialogs` should remain as 0 on Kamailio2, as technically there are no dialogs being handled by that server, it only has information of replicated dialogs and those stats are available in the `dlg.stats_active` metric. ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` # kamailio -V version: kamailio 5.2.0-pre1 (x86_64/linux) 2ecf60-dirty flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144 MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: 2ecf60 -dirty compiled with gcc 6.3.0 ``` * **Operating System**:  ``` root@sbc02:~# lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 9.5 (stretch) Release: 9.5 Codename: stretch root@sbc02:~# uname -a Linux sbc02 4.9.0-8-amd64 #1 SMP Debian 4.9.110-3+deb9u6 (2018-10-08) x86_64 GNU/Linux root@sbc02:~# ``` -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/1692

3 years, 8 months

[kamailio] Anyone thinking about adding JWT (JSON Web Token) support to Kamailio (#29)

by mading087

It seems a good idea to support JWT as a new SIP authorization method. Wonder if anyone is interested? Think auth_db would be the best spot to add support for JWT. --- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/29

3 years, 9 months

[kamailio/kamailio] 180 Ringing without Contact with TOPOS enabled (#1720)

by Sergey Basov

### Description Kamailio with TOPOS enabled acts as a proxy between SIP client and SBC. When client sends "180 Ringing" without Contact header - kamailio does not forward it to SBC. If Contact header exists in "180 Ringing" - all works as expected. ### Troubleshooting #### Reproduction Load and configure topos module Make call with "180 Ringing" without Contact header - kamailio will not forward it. #### Log Messages ``` ERROR: topos [tps_storage.c:340]: tps_storage_link_msg(): bad sip message or missing Contact hdr ``` #### SIP Traffic ``` SIP/2.0 180 Ringing Via: SIP/2.0/TLS 1.2.3.4:5061;branch=z9hG4bKef45.8c75f0bae8a59dfaec6ff533ff0f3b2d.0 From: <sip:1111@1.2.3.4:5061>;tag=02000879948559 To: <sip:2.2.2.2@5.6.7.8:5061;transport=tls;user=phone>;tag=SDbsq8499-y2pMOVV Call-ID: apdW7374315131g0bcGhEfDjFof CSeq: 988207425 INVITE User-Agent: agent Supported: replaces, outbound Content-Length: 0 ``` ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` version: kamailio 5.1.6 (x86_64/linux) flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select ``` * **Operating System**: ``` Red Hat Enterprise Linux Server 7.3 3.10.0-514.el7.x86_64 #1 SMP Wed Oct 19 11:24:13 EDT 2016 x86_64 x86_64 x86_64 GNU/Linux ``` -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/1720

3 years, 10 months

[kamailio/kamailio] Configure permissions module without database (#2037)

by Sebastian Damm

### Description In our setup, we try to eliminate setup configuration in database and replace it with files. The advantage is, that we can maintain those files via puppet or ansible, and since we always rewrite the whole file, we don't have to take care about deleting obsolete entries. We can run different Kamailio versions without having problems with the version table when using the same database. And finally, we can stop all those local mysqld processes on a lot of machines. Modules like the dispatcher module were easy to change. But the permissions module is not prepared to run without database, if you want to use `allow_trusted()` or `allow_source_address()` and similar. The only option to feed those functions with data is a database table. ### Expected behavior We would like to place files for trusted and address into the Kamailio directory and have Kamailio read from those files during startup or after reload commands. #### Actual observed behavior Data for trusted and address have to reside inside a database. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/2037

3 years, 11 months

← Newer
1
...
4
5
6
7
8
9
10
...
44
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev October 2019