sr-dev May 2017

sr-dev@lists.kamailio.org

32 participants
299 discussions

[kamailio] PID file permissions (#231)
by Arsen 26 Jul '17

26 Jul '17

ENV: Debian 8 So on most Linux systems the /var/run folder is a tmpfs and after which clears after each reboot As I try to start up kamailio after a reboot through kamctl I get the following error. "ERROR: PID file /var/run/kamailio.pid does not exist -- Kamailio start failed" Because kamailio does not have the permission to write to the /var/run folder as the kamailio user. Would it be possible to add in the "kamctl" code a section where the SPECIFIED PID LOCATION (/var/run/kamailio) is checked and if it does not exist create it as the root user and chown it to the SPECIFIED USER (kamailio)? The way I have patched it for now is to create a init script that creates a /var/run/kamailio folder and chmods it to kamailio:kamailio Thanks everyone! --- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/231

6 13

[kamailio/kamailio] tls compiler warnings (#1075)
by juha-h 28 Jun '17

28 Jun '17

These warnings should be eliminated in order to make compilation readable: CC (gcc) [M tls.so] tls_locking.o tls_locking.c:98:13: warning: 'locking_f' defined but not used [-Wunused-function] static void locking_f(int mode, int n, const char* file, int line) ^~~~~~~~~ tls_locking.c:83:13: warning: 'dyn_destroy_f' defined but not used [-Wunused-function] static void dyn_destroy_f(struct CRYPTO_dynlock_value *l, ^~~~~~~~~~~~~ tls_locking.c:65:13: warning: 'dyn_lock_f' defined but not used [-Wunused-function] static void dyn_lock_f(int mode, struct CRYPTO_dynlock_value* l, ^~~~~~~~~~ tls_locking.c:42:37: warning: 'dyn_create_f' defined but not used [-Wunused-function] static struct CRYPTO_dynlock_value* dyn_create_f(const char* file, int line) ^~~~~~~~~~~~ CC (gcc) [M tls.so] tls_init.o tls_init.c: In function 'init_ssl_methods': tls_init.c:377:2: warning: 'TLSv1_client_method' is deprecated [-Wdeprecated-declarations] ssl_methods[TLS_USE_TLSv1_cli - 1] = TLSv1_client_method(); ^~~~~~~~~~~ In file included from /usr/include/openssl/ct.h:13:0, from /usr/include/openssl/ssl.h:61, from tls_init.c:45: /usr/include/openssl/ssl.h:1598:1: note: declared here DEPRECATEDIN_1_1_0(__owur const SSL_METHOD *TLSv1_client_method(void)) /* TLSv1.0 */ ^ tls_init.c:378:2: warning: 'TLSv1_server_method' is deprecated [-Wdeprecated-declarations] ssl_methods[TLS_USE_TLSv1_srv - 1] = TLSv1_server_method(); ^~~~~~~~~~~ In file included from /usr/include/openssl/ct.h:13:0, from /usr/include/openssl/ssl.h:61, from tls_init.c:45: /usr/include/openssl/ssl.h:1597:1: note: declared here DEPRECATEDIN_1_1_0(__owur const SSL_METHOD *TLSv1_server_method(void)) /* TLSv1.0 */ ^ tls_init.c:379:2: warning: 'TLSv1_method' is deprecated [-Wdeprecated-declarations] ssl_methods[TLS_USE_TLSv1 - 1] = TLSv1_method(); ^~~~~~~~~~~ In file included from /usr/include/openssl/ct.h:13:0, from /usr/include/openssl/ssl.h:61, from tls_init.c:45: /usr/include/openssl/ssl.h:1596:1: note: declared here DEPRECATEDIN_1_1_0(__owur const SSL_METHOD *TLSv1_method(void)) /* TLSv1.0 */ ^ tls_init.c:382:2: warning: 'TLSv1_1_client_method' is deprecated [-Wdeprecated-declarations] ssl_methods[TLS_USE_TLSv1_1_cli - 1] = TLSv1_1_client_method(); ^~~~~~~~~~~ In file included from /usr/include/openssl/ct.h:13:0, from /usr/include/openssl/ssl.h:61, from tls_init.c:45: /usr/include/openssl/ssl.h:1604:1: note: declared here DEPRECATEDIN_1_1_0(__owur const SSL_METHOD *TLSv1_1_client_method(void)) /* TLSv1.1 */ ^ tls_init.c:383:2: warning: 'TLSv1_1_server_method' is deprecated [-Wdeprecated-declarations] ssl_methods[TLS_USE_TLSv1_1_srv - 1] = TLSv1_1_server_method(); ^~~~~~~~~~~ In file included from /usr/include/openssl/ct.h:13:0, from /usr/include/openssl/ssl.h:61, from tls_init.c:45: /usr/include/openssl/ssl.h:1603:1: note: declared here DEPRECATEDIN_1_1_0(__owur const SSL_METHOD *TLSv1_1_server_method(void)) /* TLSv1.1 */ ^ tls_init.c:384:2: warning: 'TLSv1_1_method' is deprecated [-Wdeprecated-declarations] ssl_methods[TLS_USE_TLSv1_1 - 1] = TLSv1_1_method(); ^~~~~~~~~~~ In file included from /usr/include/openssl/ct.h:13:0, from /usr/include/openssl/ssl.h:61, from tls_init.c:45: /usr/include/openssl/ssl.h:1602:1: note: declared here DEPRECATEDIN_1_1_0(__owur const SSL_METHOD *TLSv1_1_method(void)) /* TLSv1.1 */ ^ tls_init.c:388:2: warning: 'TLSv1_2_client_method' is deprecated [-Wdeprecated-declarations] ssl_methods[TLS_USE_TLSv1_2_cli - 1] = TLSv1_2_client_method(); ^~~~~~~~~~~ In file included from /usr/include/openssl/ct.h:13:0, from /usr/include/openssl/ssl.h:61, from tls_init.c:45: /usr/include/openssl/ssl.h:1610:1: note: declared here DEPRECATEDIN_1_1_0(__owur const SSL_METHOD *TLSv1_2_client_method(void)) /* TLSv1.2 */ ^ tls_init.c:389:2: warning: 'TLSv1_2_server_method' is deprecated [-Wdeprecated-declarations] ssl_methods[TLS_USE_TLSv1_2_srv - 1] = TLSv1_2_server_method(); ^~~~~~~~~~~ In file included from /usr/include/openssl/ct.h:13:0, from /usr/include/openssl/ssl.h:61, from tls_init.c:45: /usr/include/openssl/ssl.h:1609:1: note: declared here DEPRECATEDIN_1_1_0(__owur const SSL_METHOD *TLSv1_2_server_method(void)) /* TLSv1.2 */ ^ tls_init.c:390:2: warning: 'TLSv1_2_method' is deprecated [-Wdeprecated-declarations] ssl_methods[TLS_USE_TLSv1_2 - 1] = TLSv1_2_method(); ^~~~~~~~~~~ In file included from /usr/include/openssl/ct.h:13:0, from /usr/include/openssl/ssl.h:61, from tls_init.c:45: /usr/include/openssl/ssl.h:1608:1: note: declared here DEPRECATEDIN_1_1_0(__owur const SSL_METHOD *TLSv1_2_method(void)) /* TLSv1.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/1075

2 2

[kamailio/kamailio] IPv6 parse_uri error (#1136)
by davidxbwang 22 Jun '17

22 Jun '17

### Description  When making end-to-end IMS voice call over IPv6, Kamailio PCSCF doesn't send the Sip Invite to callee. I saw the following error in PCSCF logs: 4(32107) DEBUG: <core> [parser/parse_uri.c:1258]: parse_uri(): parse_uri: bad char ':' in state 2 parsed: <sip:FC00:1234> (13) / <sip:FC00:1234:3:2:0:0:0:0:5060> (30) 4(32107) ERROR: tm [ut.h:254]: uri2dst2(): ERROR: uri2dst: bad_uri: [sip:FC00:1234:3:2:0:0:0:0:5060] 4(32107) ERROR: tm [t_fwd.c:1737]: t_forward_nonack(): ERROR: t_forward_nonack: failure to add branches 4(32107) DEBUG: tm [t_funcs.c:331]: t_relay_to(): t_forward_nonack returned error -478 (-478) 4(32107) DEBUG: tm [t_funcs.c:348]: t_relay_to(): -478 error reply generation delayed I saw a similar issue in your database: nat_traversal: Builds wrong URI for IPv6, bad URI parsing #362. Have you fixed this issue? ### Troubleshooting To me, sip:FC00:1234:3:2:0:0:0:0:5060 should be sip:[FC00:1234:3:2:0:0:0:0]:5060. After I added the workarround to change it to sip:[FC00:1234:3:2:0:0:0:0]:5060, PCSCF can send the Sip Invite to callee and the IMS voice call can be established. #### Reproduction  I can reproduce this issue using two soft phones: Linphone and Jitsi. #### Debugging Data  ``` (paste your debugging data here) ``` #### Log Messages  ``` (paste your log messages here) ``` 4(32107) DEBUG: <core> [parser/parse_uri.c:1258]: parse_uri(): parse_uri: bad char ':' in state 2 parsed: <sip:FC00:1234> (13) / <sip:FC00:1234:3:2:0:0:0:0:5060> (30) 4(32107) ERROR: tm [ut.h:254]: uri2dst2(): ERROR: uri2dst: bad_uri: [sip:FC00:1234:3:2:0:0:0:0:5060] 4(32107) ERROR: tm [t_fwd.c:1737]: t_forward_nonack(): ERROR: t_forward_nonack: failure to add branches 4(32107) DEBUG: tm [t_funcs.c:331]: t_relay_to(): t_forward_nonack returned error -478 (-478) 4(32107) DEBUG: tm [t_funcs.c:348]: t_relay_to(): -478 error reply generation delayed #### SIP Traffic  ``` (paste your sip traffic here) ``` INVITE sip:bob@[fc00:1234:3:2:0:0:0:0]:5060;transport=udp;registering_acc=ims_mnc001_mcc001_3gppnetwork_org SIP/2.0 Record-Route: <sip:mt@[FC00:1234:1:0:0:0:0:47];lr=on;ftag=be2790bd;did=557.1972> Route: <sip:term@pcscf.ims.mnc001.mcc001.3gppnetwork.org:5060;nat=yes;received=sip:FC00:1234:3:2:0:0:0:0:5060;lr> Record-Route: <sip:mo@[FC00:1234:1:0:0:0:0:47];lr=on;ftag=be2790bd;did=557.1972> Record-Route: <sip:mo@[FC00:1234:1:0:0:0:0:45];lr=on;ftag=be2790bd;nat=yes;did=557.f271> Call-ID: 16a983b6edc2370ad08370112a800d98@0:0:0:0:0:0:0:0 CSeq: 1 INVITE From: "alice" <sip:alice@ims.mnc001.mcc001.3gppnetwork.org>;tag=be2790bd To: <sip:bob@ims.mnc001.mcc001.3gppnetwork.org> Via: SIP/2.0/UDP [FC00:1234:1:0:0:0:0:47];branch=z9hG4bKc87.6294094b4129fdf733069ffd6625d303.0 Via: SIP/2.0/UDP [FC00:1234:1:0:0:0:0:46];branch=z9hG4bKc87.66958ffdcce62f80024bf5913086e312.1 Via: SIP/2.0/UDP [FC00:1234:1:0:0:0:0:47];branch=z9hG4bKc87.5d9a7aae58830978432d73b25057fb39.0 Via: SIP/2.0/UDP [FC00:1234:1:0:0:0:0:45];branch=z9hG4bKc87.b56bcd8f177f65d2b1ec20ccca46519a.0 Via: SIP/2.0/UDP [fc00:1234:3:1:0:0:0:0]:5060;rport=5060;branch=z9hG4bK-363237-5db2dc2ac95e17a0c589ae29eb75a0ce Max-Forwards: 66 Contact: "alice" <sip:alice@[fc00:1234:3:1:0:0:0:0]:5060;transport=udp;registering_acc=ims_mnc001_mcc001_3gppnetwork_org> User-Agent: Jitsi2.10.5550Linux Content-Type: application/sdp Content-Length: 910 X-RTP: mo P-Asserted-Identity: <sip:alice@ims.mnc001.mcc001.3gppnetwork.org> v=0 o=alice-jitsi.org 0 0 IN IP6 fc00:1234:3:1:0:0:0:0 s=- c=IN IP6 fc00:1234:3:1:0:0:0:0 t=0 0 m=audio 5056 RTP/AVP 96 97 98 9 100 102 0 8 103 3 104 101 a=rtpmap:96 opus/48000/2 a=fmtp:96 usedtx=1 a=ptime:20 a=rtpmap:97 SILK/24000 a=rtpmap:98 SILK/16000 a=rtpmap:9 G722/8000 a=rtpmap:100 speex/32000 a=rtpmap:102 speex/16000 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:103 iLBC/8000 a=rtpmap:3 GSM/8000 a=rtpmap:104 speex/8000 a=rtpmap:101 telephone-event/8000 a=extmap:1 urn:ietf:params:rtp-hdrext:csrc-audio-level a=extmap:2 urn:ietf:params:rtp-hdrext:ssrc-audio-level a=rtcp-xr:voip-metrics m=video 5058 RTP/AVP 105 99 a=recvonly a=rtpmap:105 H264/90000 a=fmtp:105 profile-level-id=4DE01f;packetization-mode=1 a=imageattr:105 send * recv [x=[1:1376],y=[1:883]] a=rtpmap:99 H264/90000 a=fmtp:99 profile-level-id=4DE01f a=imageattr:99 send * recv [x=[1:1376],y=[1:883]] ### Possible Solutions  ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` (paste your output here) ``` version: kamailio 5.0.0-dev5 (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_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 on 21:48:42 Feb 21 2017 with gcc 5.4.0 * **Operating System**:  ``` (paste your output here) ``` Distributor ID: Ubuntu Description: Ubuntu 16.04.2 LTS Release: 16.04 Codename: xenial -- 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/1136

6 17

[kamailio/kamailio] Compile problem+fix on solaris in app_jsdt (#1072)
by celan69 13 Jun '17

13 Jun '17

Kamailio 5 did not compile on solaris 11 anymore due to a missing ast/endian.h included from app_jsdt/duk_config.h. The solution is: --- kamailio-5.0.1~/src/modules/app_jsdt/duk_config.h 2017-04-05 15:32:38.000000000 +0000 +++ kamailio-5.0.1/src/modules/app_jsdt/duk_config.h 2017-04-15 09:27:14.335213048 +0000 @@ -607,7 +607,7 @@ #define DUK_USE_DATE_FMT_STRFTIME #include <sys/types.h> -#include <ast/endian.h> +#include <sys/byteorder.h> #include <sys/param.h> #include <sys/time.h> #include <time.h> -- 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/1072

2 6

[kamailio/kamailio] Extend keepalive module documentation (#1082)
by Andreas Granig 13 Jun '17

13 Jun '17

The new keepalive module states that it "performs destinations monitoring either for itself, or on the behalf of other modules". What does that mean? What are the use cases and which problems does it solve? Which mechanisms does it use (SIP, ICMP, others?) Some examples would greatly help in the README to get some context on how to actually use this module. -- 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/1082

4 6

benchmark rpc commands causing kamailio to crash
by David Escartín Almudévar 06 Jun '17

06 Jun '17

hello all today testing kamailio 5.0.1 version we have seen that some rpc commands of benchmark module are not working fine. when trying to change enable_global parameter, setting 1 for example it says that the parameter is invalid /usr/local/kamailio-5.0/sbin/kamcmd -s udp:127.0.0.1:2046 benchmark.enable_global 1 error: 500 - Invalid Parameter Value besides, it also permits to set a granularity value of 0 without giving error. By doing that, if the kamailio has calls in progress, the kamailio get a crash Core was generated by `/usr/local/kamailio-5.0/sbin/kamailio -P /var/run/kamailio/kamailio_talos.pid -'. Program terminated with signal 8, Arithmetic exception. #0 0x00007f4d55989757 in _bm_log_timer (id=0) at benchmark.c:320 320 if ((bm_mycfg->tindex[id]->calls % bm_mycfg->granularity) == 0) Missing separate debuginfos, use: debuginfo-install glibc-2.12-1.132.el6.x86_64 libxml2-2.7.6-14.el6.x86_64 pcre-7.8-6.el6.x86_64 zlib-1.2.3-29.el6.x86_64 i understand that maybe is trying to divide by 0 to calcutate the benchmark stats. checking the functions, we made a change to fix this problem, by chaning the type of the vars defined as "int", instead of "long int". this way seems the commands work fine /usr/local/kamailio-5.0/sbin/kamcmd -s udp:127.0.0.1:2046 benchmark.enable_global 1 /usr/local/kamailio-5.0/sbin/kamcmd -s udp:127.0.0.1:2046 benchmark.granularity 0 error: 500 - Invalid Parameter Value this are the changes we made index d40469b..5a353d5 100644 --- a/src/modules/benchmark/benchmark.c +++ b/src/modules/benchmark/benchmark.c @@ -479,7 +479,8 @@ static inline int fixup_bm_timer(void** param, int param_no) */ void bm_rpc_enable_global(rpc_t* rpc, void* ctx) { - long int v1; + int v1; + /*long int v1;*/ if(rpc->scan(ctx, "d", (int*)(&v1))<1) { LM_WARN("no parameters\n"); rpc->fault(ctx, 500, "Invalid Parameters"); @@ -518,7 +519,8 @@ void bm_rpc_enable_timer(rpc_t* rpc, void* ctx) void bm_rpc_granularity(rpc_t* rpc, void* ctx) { - long int v1; + int v1; + /*long int v1;*/ if(rpc->scan(ctx, "d", (int*)(&v1))<1) { LM_WARN("no parameters\n"); rpc->fault(ctx, 500, "Invalid Parameters"); @@ -533,7 +535,8 @@ void bm_rpc_granularity(rpc_t* rpc, void* ctx) void bm_rpc_loglevel(rpc_t* rpc, void* ctx) { - long int v1; + int v1; + /*long int v1;*/ if(rpc->scan(ctx, "d", (int*)(&v1))<1) { LM_WARN("no parameters\n"); rpc->fault(ctx, 500, "Invalid Parameters"); could you please check if this fix is enough? and maybe there can be some other functions with this problem? thanks alot and regards david

2 2

[kamailio/kamailio] pkg/kamailio: Fixed systemd unit failure on server boot (#1090)
by sergey-safarov 02 Jun '17

02 Jun '17

You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/1090 -- Commit Summary -- * pkg/kamailio: Fixed systemd unit failure on server boot -- File Changes -- M pkg/kamailio/centos/7/kamailio.service (2) M pkg/kamailio/fedora/17/kamailio.service (2) -- Patch Links -- https://github.com/kamailio/kamailio/pull/1090.patch https://github.com/kamailio/kamailio/pull/1090.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/1090

3 7

[kamailio/kamailio] pkg/kamailio: Fixed systemd unit failure on server boot (#1089)
by sergey-safarov 02 Jun '17

02 Jun '17

You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/1089 -- Commit Summary -- * pkg/kamailio: Fixed systemd unit failure on server boot -- File Changes -- M pkg/kamailio/centos/7/kamailio.service (2) M pkg/kamailio/fedora/17/kamailio.service (2) -- Patch Links -- https://github.com/kamailio/kamailio/pull/1089.patch https://github.com/kamailio/kamailio/pull/1089.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/1089

3 8

[kamailio/kamailio] htable: fix crash if deleted entry is reused (#1142)
by lazedo 02 Jun '17

02 Jun '17

resets 'first' when esize == 0 You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/1142 -- Commit Summary -- * htable: fix crash if deleted entry is reused -- File Changes -- M src/modules/htable/ht_api.c (14) -- Patch Links -- https://github.com/kamailio/kamailio/pull/1142.patch https://github.com/kamailio/kamailio/pull/1142.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/1142

2 5

git:master:c1737daf: modules: readme files regenerated - ctl ... [skip ci]
by Kamailio Dev 31 May '17

31 May '17

Module: kamailio Branch: master Commit: c1737dafeddc7c2f496d45e5df1b3da9c287494b URL: https://github.com/kamailio/kamailio/commit/c1737dafeddc7c2f496d45e5df1b3da… Author: Kamailio Dev <kamailio.dev(a)kamailio.org> Committer: Kamailio Dev <kamailio.dev(a)kamailio.org> Date: 2017-05-31T22:01:23+02:00 modules: readme files regenerated - ctl ... [skip ci] --- Modified: src/modules/ctl/README --- Diff: https://github.com/kamailio/kamailio/commit/c1737dafeddc7c2f496d45e5df1b3da… Patch: https://github.com/kamailio/kamailio/commit/c1737dafeddc7c2f496d45e5df1b3da… --- diff --git a/src/modules/ctl/README b/src/modules/ctl/README index e879436b11..5bb4170ca5 100644 --- a/src/modules/ctl/README +++ b/src/modules/ctl/README @@ -160,7 +160,7 @@ loadmodule "ctl" # optional listen addresses, if no one is specified, # ctl will listen on unixs:/tmp/ser_ctl -modparam("ctl", "binrpc", "unix:/tmp/kamailio_ctl") # default +modparam("ctl", "binrpc", "unix:/var/run/kamailio/kamailio_ctl") # default modparam("ctl", "binrpc", "udp:localhost:2046") modparam("ctl", "binrpc", "tcp:localhost:2046") modparam("ctl", "binrpc", "unixd:/tmp/unix_dgram") # unix datagram @@ -289,7 +289,7 @@ modparam("ctl", "binrpc_struct_max_body_size", 4) Example 1.11. print usage $ kamcmd -f"[%v] %v:%v %v\n" ctl.listen -[binrpc] unix_stream:/tmp/kamailio_ctl +[binrpc] unix_stream:/var/run/kamailio/kamailio_ctl # note: the above command is equivalent with kamcmd listen @@ -307,6 +307,6 @@ modparam("ctl", "binrpc_struct_max_body_size", 4) Example 1.13. ctl.who usage $ kamcmd -f"[%v] %v: %v %v -> %v %v\n" ctl.who -[binrpc] unix_stream: <anonymous unix socket> -> /tmp/kamailio_ctl +[binrpc] unix_stream: <anonymous unix socket> -> /var/run/kamailio/kamailio_ctl # note the above command is equivalent to kamcmd who

1 0

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