sr-dev October 2019

sr-dev@lists.kamailio.org

22 participants
436 discussions

[kamailio/kamailio] Allow more options on dispatcher.set_state (#2085)

by duarterocha91

Greetings, Dispatcher RPC command allows to change the runtime state of a GW using its Group ID and the IP. In my implementation i have 2 Kamailio machines in an HA setup and, as such, i have the GW configured twice with same group_id and different sockets (Different HA adressess - one for each machine). I would like to be able to disable on runtime GWs that are configured with an HA adress that isn't present yet on that machine. To be able do that, the combination of GroupID + IP is not enough, but Socket + IP would be enough. Is this possible to implement ? Best Regards -- 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/2085

4 years, 6 months

[kamailio/kamailio] error: 'pkg/docker' does not have a commit checked out (#2003)

by Daniel-Constantin Mierla

When I just tried to do a commit today, I got the following error: ``` kamailio $ git ci . error: 'pkg/docker' does not have a commit checked out fatal: updating files failed ``` It is related to the `pkg/docker` submodule referencing to kamailio/kamailio-ci. Not sure if this is due to a new git version or something else, because I did commits in that folder a few days ago. To get is sorted out, I did: ``` kamailio $ git submodule update pkg/docker Submodule path 'pkg/docker' not initialized Maybe you want to use 'update --init'? kamailio $ git submodule update --init pkg/docker Submodule 'pkg/docker' (https://github.com/kamailio/kamailio-ci.git) registered for path 'pkg/docker' Cloning into '/.../kamailio/pkg/docker'... Submodule path 'pkg/docker': checked out 'b92a1c899b8c474afadd0cf29dd7cb4ea01a3466' ``` Then it worked to do the commit. I wonder if this is going to break the process we were used with, specially the installation guidelines from GIT repo. Therefore I open this item to see if we really need the to have `pkg/docker` submodule, or better have the docker files directly in the repo. Other options to keep things sane and simple? Git version: ``` $ git --version git version 2.22.0 ``` -- 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/2003

4 years, 6 months

[kamailio/kamailio] [Feature Request] Python3 compatibility for dbtextdb (#1747)

by Anthony Messina

kamctl's dbtextdb.py fails to build in a Python3-only environment. Update dbtextdb to Python3. -- 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/1747

4 years, 6 months

[kamailio/kamailio] TLS module compiled with outdated OpenSSL version for Ubuntu bionic (#2018)

by welljsjs

### Description  Ubuntu Bionic 18.04.02 LTS ships with "OpenSSL 1.1.1 11 Sep 2018" (0x1010100f), whereas the `kamailio-tls-modules` package is compiled with "OpenSSL 1.1.0g 2 Nov 2017" (0x1010007f). I installed Kamailio from the Kamailio repositories (not from the Ubuntu repositories). This leads to Kamailio being unable to start as it complains about the OpenSSL versions being too different from each other. Overriding the OpenSSl version check by enabling `tls_force_run` does not solve the issue, instead, it leads to Kamailio emitting multiple errors.  #### Reproduction I installed Kamailio from the official Kamailio apt sources (nightly build, the same occurs for the latest stable version 5.2). ``` deb http://deb.kamailio.org/kamailiodev-nightly bionic main deb-src http://deb.kamailio.org/kamailiodev-nightly bionic main ``` I enabled TLS and edited the configuration files accordingly.    ``` (paste your debugging data here) ``` #### Log Messages ``` CRITICAL: tls [tls_init.c:677]: init_tls_h(): installed openssl library version is too different from the library the kamailio tls module was compiled with: installed "OpenSSL 1.1.1 11 Sep 2018" (0x1010100f), compiled "OpenSSL 1.1.0g 2 Nov 2017" (0x1010007f).#012 Please make sure a compatible version is used (tls_force_run in kamailio.cfg will override this check) ```  ### Possible Solutions Recompile and publish the `kamailio-tls-modules` package compiled with OpenSSL 1.1.1b. ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` version: kamailio 5.3.0-dev6 (x86_64/linux) flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, 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: unknown compiled with gcc 7.3.0 ``` * **Operating System**:  ``` Linux hostname 4.15.0-55-generic #60-Ubuntu SMP Tue Jul 2 18:22:20 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Description: Ubuntu 18.04.2 LTS Release: 18.04 ``` -- 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/2018

4 years, 7 months

[kamailio/kamailio] Support for 192.0.0.0/29 as NATed source (#1488)

by dtryba

#### 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 - [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 - [ ] Tested changes locally - [ ] Related to issue #XXXX (replace XXXX with an open issue number) #### Description  192.0.0.0/29 is a reserved subnet for NATtin IPv4 across an IPv6 netwerk. For example Dual Stack Lite carrier grade NAT. This is small change and updates the subnets used for NAT according to https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-speci… You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/1488 -- Commit Summary -- * Support for -- File Changes -- M src/modules/ipops/detailed_ip_type.c (1) M src/modules/ipops/detailed_ip_type.h (2) M src/modules/nat_traversal/nat_traversal.c (3) M src/modules/nathelper/nathelper.c (1) -- Patch Links -- https://github.com/kamailio/kamailio/pull/1488.patch https://github.com/kamailio/kamailio/pull/1488.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/1488

4 years, 7 months

[kamailio/kamailio] app_python warning about strict-aliasing (#1249)

by Daniel-Constantin Mierla

Tracking here the issue exposed by @linuxmaniac via PR #924, as it was merged and then reverted (by #1248), so anyone can be aware of as well as comment/propose solutions for it. > Add "-fno-strict-aliasing" to compilation flags > > Fixes a slew of: > "dereferencing type-punned pointer will break strict-aliasing rules" > warnings from GCC for lines of the form: > Py_INCREF(Py_True); > and > Py_INCREF(Py_False); > > due to the cast from PyIntObject* to PyObject* > > GCC is technically correct here; see: > http://www.python.org/dev/peps/pep-3123/ > though this is unlikely to lead to non-working machine code. The initial proposed patch for `src/modules/app_python/Makefile` is: ``` @@ -22,6 +22,8 @@ ifeq ($(OS), freebsd) LIBS+=-pthread endif +# python2 https://www.python.org/dev/peps/pep-3123/ +DEFS+=-fno-strict-aliasing DEFS+=-I${PYTHON_INCDIR} DEFS+=-DKAMAILIO_MOD_INTERFACE ``` -- 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/1249

4 years, 8 months

[kamailio/kamailio] Kamailio SDP Error 5.1.8 (#1983)

by nicoonline

Hello, I got this message under some circumstances (the number called) Jun 12 15:15:01 proxy1 /usr/sbin/kamailio[16096]: ERROR: <core> [core/parser/sdp/sdp.c:228]: set_sdp_payload_fmtp(): Invalid payload location What means "Payload location" ? SDP Debug from the callee: Jun 12 15:15:01 proxy1 /usr/sbin/kamailio[16096]: DEBUG: sdpops [sdpops_mod.c:1626]: sdp_get_helper(): Found SDP v=0#015#012o=- 5793 1 IN IP4 192.168.50.50#015#012s=-#015#012t=0 0#015#012m=audio 24734 RTP/AVP 8 101#015#012c=IN IP4 217.112.190.117#015#012a=rtpmap:101 telephone-event/8000#015#012a=fmtp:18 annexa=yes#015#012a=fmtp:101 0-15#015#012a=ptime:30#015#012a=silenceSupp:off - - - -#015#012a=sendrecv#015#012 SDP Debug called pbx: Jun 12 15:15:01 proxy1 /usr/sbin/kamailio[16097]: DEBUG: sdpops [sdpops_mod.c:1626]: sdp_get_helper(): Found SDP v=0#015#012o=root 1673681431 1673681431 IN IP4 217.112.180.5#015#012s=Asterisk PBX 11.25.1#015#012c=IN IP4 217.112.180.5#015#012t=0 0#015#012m=audio 10884 RTP/AVP 8 101#015#012a=rtpmap:8 PCMA/8000#015#012a=rtpmap:101 telephone-event/8000#015#012a=fmtp:101 0-16#015#012a=ptime:20#015#012a=sendrecv#015#012 -- 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/1983

4 years, 8 months

[kamailio/kamailio] Adding CDR as JSON functionality (#2107)

by Lucian Balaceanu

#### 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 #XXXX (replace XXXX with an open issue number) #### Description  These commits create a CDR addressed engine, similar to the one that acc module exports for acc message accounting. Such an engine made an extension module like acc_json possible. This CDR engine is then used in acc_json to write the functionality for logging CDRs in JSON format. I have added functions to the API exported by acc module instead of creating another separate CDR API, as I thought this is cleaner. I only implemented the acc_json logging to syslog (no message queue support yet). You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/2107 -- Commit Summary -- * acc: adding CDR engine functionality * acc_json: adding CDR as JSON functionality -- File Changes -- M src/modules/acc/acc_api.h (38) M src/modules/acc/acc_cdr.c (41) M src/modules/acc/acc_cdr.h (6) M src/modules/acc/acc_logic.c (10) M src/modules/acc/acc_logic.h (2) M src/modules/acc/acc_mod.c (93) M src/modules/acc_json/acc_json_mod.c (131) M src/modules/acc_json/acc_json_mod.h (4) M src/modules/acc_json/doc/acc_json_admin.xml (54) -- Patch Links -- https://github.com/kamailio/kamailio/pull/2107.patch https://github.com/kamailio/kamailio/pull/2107.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/2107

4 years, 9 months

some missing kemi module functions

by David Escartin

hello all we are trying to rewrite our code to lua kemi, and we have found some issues/questions until we would like to share with you. -module call_obj not exported, we have tested a patch for the module to export the functions to kemi, which seems works fine -KSR.xlog.xinfo seems not able to select a facility as we currently can like xlog("LOG_LOCAL7", "L_NOTICE", "$var(xxxx)"); -module sipt not exported yet, must use ksr.x.modf ? will be exported for a future version? -on 5.3.0-dev5 we don't see the KSR.dialog.var_sets() and KSR.dialog.var_get/e/w() functions in the code, so we do use KSR.pv functions to set and retrieve those dialog vars. However i see them on master branch. Which kamailio release would have them? -sdpops function sdp_with_codecs_by_name seems to not me exported, is it on a todo list? -textops module, missing remove_hf and append_hf functions exported. We already did a patch for the remove_hf, despite we could work with textopsx remove_hf_value function to get the almost the same functionality. However, with append_hf i'm having some more issues. We cannot use modf to exec those funtions, we get something like For ---> KSR.x.modf("append_hf", "User-Agent: test", "To"); I get something like ----> Jun 27 07:19:16 proxy-1 /usr/local/kamailio/sbin/kamailio[5525]: ERROR: app_lua [app_lua_sr.c:188]: lua_sr_modf(): function 'append_hf' has fixup - cannot be used I could append a new header and not only at the end of the message by replacing a header called the same way, by doing something like KSR.textopsx.insert_hf_value("header", "value"); KSR.textopsx.remove_hf_value("header[-1]"); but i'm not able to insert a header after another different one like we can do with append_hf("header:value", "To") for instance. Is it expected to have it on a next commit those append_hf and remove_hf exported. Would we do a pull request with the ki_remove_hf we already have and the call_obj functions too? We can check to export append_hf too if it's not planned to be done thanks a lot and regards david

4 years, 9 months

[kamailio/kamailio] db_check_table_version(): invalid version 6 for table subscriber found, expected 7 (check table structure and table "version") (#1270)

by abell-star

kamailio version：5.0.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/1270

4 years, 10 months

← Newer
1
...
5
6
7
8
9
10
11
...
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