sr-dev May 2018

sr-dev@lists.kamailio.org

22 participants
214 discussions

[kamailio/kamailio] ims_charging unlink_unsafe_ro_session (#1549)
by thulasizwe-n 20 Jun '18

20 Jun '18

Apologies if i have not kept with the reporting standard. Insertion attempts of out-of-credit replies from resume_on_initial_ccr callback, are corrupting the ro_session list. i.e. they nullify the first and last fields, which under certain conditions the first entry gets restored but not the last.This then crashes the process at ro_session_hash.c (link_ro_session), where the first entry has a valid address but the last does not. Solution: ro_session_hash.h - unlink_unsafe_ro_session - check if the session to be linked is actually part of list i.e if ((ro_session->next == 0x00) && (ro_session->prev == 0x00) && (ro_session != ro_session_entry->first) ) { ro_session, &(ro_session->ro_tl), ro_session->callid.len, ro_session->callid.len, ro_session->callid.s); return; } rest of the code .... -- 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/1549

3 7

[kamailio] set_contact_alias is not applied (#445)
by Olle E. Johansson 20 Jun '18

20 Jun '18

If I run set_contact_alias nothing happens - the contact remains the same on the outbound message There's no error returned and debug logs indicate a proper header However, if I add "msg_apply_changes()" on the line after set_contact_alias the Contact sent to next hop has the alias content No other changes --- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/445

3 19

[kamailio/kamailio] ims_usrloc_scscf: bugfix Contct is removed when old Contct expires (#1547)
by Christoph VALENTIN 12 Jun '18

12 Jun '18

in function unlink_contact_from_impu() (in file impurecord.c) an assignment "=" is used instead of a comparision operator "==". This leads to mess, when old contact expires.   #### Pre-Submission Checklist    - [x] Commit message has the format required by CONTRIBUTING guide - [x] Commits are split per component (core, individual modules, libs, utils, ...) - [x] Each component has a single commit (if not, squash them into one commit) - [x] 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 - [x] 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:  - [x] PR should be backported to stable branches - [x] Tested changes locally versus release 5.1.0 - [ ] Related to issue #XXXX (replace XXXX with an open issue number) #### Description  This is the pull request for branch 5.1, which has been created by "cherry-pick" from the original commit You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/1547 -- Commit Summary -- * ims_usrloc_scscf: bugfix Contct is removed when old Contct expires -- File Changes -- M src/modules/ims_usrloc_scscf/impurecord.c (2) -- Patch Links -- https://github.com/kamailio/kamailio/pull/1547.patch https://github.com/kamailio/kamailio/pull/1547.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/1547

3 4

[kamailio/kamailio] log_prefix do not work in failure_route (#1531)
by Jurijs Ivolga 08 Jun '18

08 Jun '18

### Description log_prefix do not work in failure_route ### Troubleshooting #### Reproduction log_prefix="{$mt $hdr(CSeq) $ci} " ... ... failure_route[RTF_LCR_ROUTE] { if (t_is_canceled()) { exit; } xlog("L_INFO", "--- SCRIPT: failure_route - RTF_LCR_ROUTE\n"); if (t_check_status("408|50[0-4]") or (t_branch_timeout() and !t_branch_replied())) { if(!next_gw()) { send_reply("503", "No more LCR gateways"); exit; } xlog("L_INFO", "flag $avp(lcr_flag) \n"); t_on_failure("RTF_LCR_ROUTE"); t_set_retr(0, 4000); route(RELAY); exit; } } #### Debugging Data  ``` (paste your debugging data here) ``` #### Log Messages  ``` INFO: <script>: --- SCRIPT: failure_route - RTF_LCR_ROUTE ``` #### SIP Traffic  ``` (paste your sip traffic here) ``` ### Possible Solutions  ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` version: kamailio 4.4.7 (x86_64/linux) 35d8ab 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. id: 35d8ab compiled on 11:55:20 Mar 19 2018 with gcc 6.3.0 ``` * **Operating System**:  ``` Linux kamailio 4.13.0-37-generic #42~16.04.1-Ubuntu SMP Wed Mar 7 16:03:28 UTC 2018 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/1531

2 3

[kamailio/kamailio] cfgt: wrong route name if onsend_route is not declared at the beginning (#1536)
by Marco Capetta 07 Jun '18

07 Jun '18

kamailio version: kamailio 5.1.2 (x86_64/linux) If "onsend_route" routing block is defined at the beginning of the kamailio.cfg routing part, the name defined in "src/core/cfg.lex" file (DEFAULT_SEND) is used when printed in the json files. Instead, if this routing block is defined in between the configuration, its name is changed to the previous defined block. For example, if the cfg file looks like the following: route[TEST_1] { ... } onsend_route { ... } route[TEST_2] { ... } then in the output json file, the "onsend_route" block is called TEST_1. The issue doesn't happen for "request_route" block. -- 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/1536

2 2

[kamailio/kamailio] mod kazoo cannot be loaded on latest alpine:edge (#1540)
by sergey-safarov 07 Jun '18

07 Jun '18

When loaded mod kazoo i get error ``` / # kamailio -DD -E 0(178) WARNING: <core> [core/cfg.y:3426]: warn_at(): warning in config file /etc/kamailio/default.cfg, line 67, column 12: raw socket support not compiled in 0(178) ERROR: <core> [core/sr_module.c:582]: load_module(): could not open module </usr/lib/kamailio/modules/kazoo.so>: Error relocating /usr/lib/kamailio/modules/kazoo.so: is_error: symbol not found 0(178) CRITICAL: <core> [core/cfg.y:3446]: yyerror_at(): parse error in config file /etc/kamailio/default.cfg, line 188, column 12-21: failed to load module 0(178) ERROR: <core> [core/modparam.c:152]: set_mod_param_regex(): No module matching <kazoo> found ``` And ldd output ``` / # LD_PRELOAD=/usr/sbin/kamailio ldd /usr/lib/kamailio/modules/kazoo.so ldd (0x5592f5d09000) /usr/sbin/kamailio => /usr/sbin/kamailio (0x7fa6235bc000) libjson-c.so.4 => /usr/lib/libjson-c.so.4 (0x7fa6233ae000) libuuid.so.1 => /lib/libuuid.so.1 (0x7fa6231a8000) librabbitmq.so.4 => /usr/lib/librabbitmq.so.4 (0x7fa622f8c000) libevent-2.1.so.6 => /usr/lib/libevent-2.1.so.6 (0x7fa622d42000) libsrdb1.so.1 => /usr/lib/kamailio//libsrdb1.so.1 (0x7fa622b21000) libc.musl-x86_64.so.1 => ldd (0x5592f5d09000) libssl.so.45 => /lib/libssl.so.45 (0x7fa6228d5000) libcrypto.so.43 => /lib/libcrypto.so.43 (0x7fa62252a000) Error relocating /usr/lib/kamailio/modules/kazoo.so: is_error: symbol not found / # ``` Symbol `is_error` is defined at `/usr/include/json-c/bits.h` ``` /** * @deprecated */ #define is_error(ptr) (ptr == NULL) ``` I not know why this simple definition is not compiled into mod kazoo on latest Alpine:edge. -- 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/1540

2 2

[kamailio/kamailio] pv_evalx result in destination pv seems wrong (#1551)
by Victor Seva 07 Jun '18

07 Jun '18

### Description ``` xinfo("Send the call to CGRates ci='$ci'"); $var(tmp) = '"event":"CGR_AUTH_REQUEST", "cgr_category":"$dlg_var(cgrCategory)", "cgr_reqtype":"$dlg_var(cgrReqType)", "cgr_tenant":"$dlg_var(tenant)", "cgr_account":"$dlg_var(cgrAccount)", "cgr_destination":"$dlg_var(cgrDestination)", "direction":"$dlg_var(profile)", "source_user":"$dlg_var(source_user)", "recording_url":"", "account_code":"$dlg_var(account_code)", "billing_cli":"$dlg_var(billing_cli)", "cgr_setuptime":"$dlg_var(start_ts)", "reseller_id":"$dlg_var(reseller_id)"'; pv_evalx("$var(msg)", "$var(tmp)"); xinfo("--- $$var(tmp):'$var(tmp)'"); xinfo("--- $$var(msg):'$var(msg)'"); xinfo("++++"); ``` ### Troubleshooting #### Log Messages ``` May 31 15:07:27 PBX-2117 kamailio[30682]: INFO: <script>: Send the call to CGRates ci='ynfvvklkkcajrfi(a)slim.torreviejawireless.org' May 31 15:07:27 PBX-2117 kamailio[30682]: INFO: <script>: --- $var(tmp):'"event":"CGR_AUTH_REQUEST",#012 "cgr_category":"$dlg_var(cgrCategory)",#012 "cgr_reqtype":"$dlg_var(cgrReqType)",#012 "cgr_tenant":"$dlg_var(tenant)",#012 "cgr_account":"$dlg_var(cgrAccount)",#012 "cgr_destination":"$dlg_var(cgrDestination)",#012 "direction":"$dlg_var(profile)",#012 "source_user":"$dlg_var(source_user)",#012 "recording_url":"",#012 "account_code":"$dlg_var(account_code)",#012 "billing_cli":"$dlg_var(billing_cli)",#012 "cgr_setuptime":"$dlg_var(start_ts)",#012 "reseller_id":"$dlg_var(reseller_id)"' May 31 15:07:27 PBX-2117 kamailio[30682]: INFO: <script>: --- $var(msg):'5 May 31 15:07:27 PBX-2117 kamailio[30682]: INFO: <script>: ++++ ``` ### Possible Solutions  ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` version: kamailio 5.0.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. id: unknown compiled with gcc 4.8.2 ``` -- 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/1551

2 7

[kamailio/kamailio] dispatcher: congestion detection load balancing (#1533)
by Julien Chavanton 05 Jun '18

05 Jun '18

#### Pre-Submission Checklist    - [x] Commit message has the format required by CONTRIBUTING guide - [x] Commits are split per component (core, individual modules, libs, utils, ...) - [x] Each component has a single commit (if not, squash them into one commit) - [x] 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) - [x] 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 - [x] Tested changes locally - [ ] Related to issue #XXXX (replace XXXX with an open issue number) #### Description  Presented at Kamailio World 2018, load balancing doing congestion detection More information can be found http://www.castmm.com/KW2018.pdf https://github.com/jchavanton/kam_load_balancing You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/1533 -- Commit Summary -- * dispatcher: congestion detection load balancing -- File Changes -- M src/modules/dispatcher/dispatch.c (103) M src/modules/dispatcher/dispatch.h (2) M src/modules/dispatcher/doc/dispatcher.xml (2) M src/modules/dispatcher/doc/dispatcher_admin.xml (9) -- Patch Links -- https://github.com/kamailio/kamailio/pull/1533.patch https://github.com/kamailio/kamailio/pull/1533.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/1533

2 5

Releasing Kamailio v5.1.4
by Daniel-Constantin Mierla 05 Jun '18

05 Jun '18

Hello, I am considering to release a new minor version out of branch 5.1, respectively the v5.1.4, sometime next week, likely on Tuesday, June 5, 2018. As usual, if there is any issue not yet reported on github tracker, do it as soon as possible to give it a chance to be fixed. Soon I am going to do the backports of commits with fixes in master that apply in branch 5.1, so keep a close eye and if someone is missing, let me know to push it in the stable branch. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference -- www.kamailioworld.com

3 3

[kamailio/kamailio] change ims_diameter_server to allow binary data transcoding (#1528)
by Sergey Zyrianov 05 Jun '18

05 Jun '18

#### 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:  - [x] PR should be backported to stable branches - [x] Tested changes locally - [ ] Related to issue #XXXX (replace XXXX with an open issue number) #### Description  Diameter request MAR and corresponding response MAA both contain authentication vectors in binary form. Ims_diameter_server lacks functionality to convert binary arrays to json and back. This pr is a couple of minor fixes to rectify the issue: * when converting Diameter binary vector to json use %02x in sprintf() to form a proper hexdump which is possible to decode on json side. The hexdump is sent in "data" key value pair as string. * introduce new key value pair "hexdump" in json which will contain hex dump of binary vector formed on json side. ims_diameter_server converts it to Diameter AVP using hex dump to binary transcoding. You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/1528 -- Commit Summary -- * use hexdump type of string to send binary data in json * duplicate before giving it to cdp * converting binary data to hex dump requires fixed width lenght in snprintf -- File Changes -- M src/modules/ims_diameter_server/avp_helper.c (50) -- Patch Links -- https://github.com/kamailio/kamailio/pull/1528.patch https://github.com/kamailio/kamailio/pull/1528.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/1528

3 6

← Newer
1
...
5
6
7
8
9
10
11
...
22
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev May 2018