Re: [SR-Users] Kamailio 5.5.0 | CRITICAL: [core/pass_fd.c:277]: receive_fd(): EOF on 26
Hello, With Ubuntu 20.04 I face the same issue ☹, I disable the ssl with mysql (config of kamailio) and now it’s ok BR Laurent From: Daniel-Constantin Mierla Sent: lundi, 14 juin 2021 10:19 To: Kamailio (SER) - Users Mailing List ; Laurent Schweizer ; Kamailio (SER) - Users Mailing List Subject: Re: [SR-Users] Kamailio 5.5.0 | CRITICAL: [core/pass_fd.c:277]: receive_fd(): EOF on 26 Hello, if you are using libmysql from MySQL project (not MariaDB), there were similar issues reported which indicates some conflict/issue with libssl on Ubuntu 18.04. Try to upgrade to Ubuntu 20.04. Also, you can try with --atexit=no in case you are still facing startup issues on newer OS versions. Cheers, Daniel On 12.06.21 00:25, Laurent Schweizer wrote: Hello, Sorry, idea was to test the 5.6.0 and not the 5.5.0, so I will try again BR Laurent From: Laurent Schweizer Sent: vendredi, 11 juin 2021 23:49 To: Kamailio (SER) - Users Mailing List <mailto:sr-us...@lists.sip-router.org> Subject: Kamailio 5.5.0 | CRITICAL: [core/pass_fd.c:277]: receive_fd(): EOF on 26 Dear all, I setup a Kamailio 5.5.0 (from GIT) on a ubuntu Ubuntu 18.04.5 LTS and I have some error with the libssl/ libmysql, seems not happening every time. Regarding the config file, it’s a config running correctly on a Kamailio 5.3.x on a centos 7 I have attached the returned error and the result of the core file. Any idea ? BR Laurent version: kamailio 5.5.0 (x86_64/linux) 66370c flags: 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_BLOCKLIST, HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED 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: 66370c compiled on 07:23:15 Jun 11 2021 with gcc 7.5.0 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: loading modules under config path: /usr/local/lib64/kamailio/modules/ Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: Listening on Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: udp: 80.132.9.112:5060 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: udp: 80.132.9.112:6000 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: tcp: 80.132.9.112:5060 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: tcp: 80.132.9.112:6000 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: tls: 80.132.9.112:5061 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: Aliases: Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: tls: zrh02-srv03:5061 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: tcp: zrh02-srv03:6000 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: tcp: zrh02-srv03:5060 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: udp: zrh02-srv03:6000 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: udp: zrh02-srv03:5060 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: *: sipbkp.demo.ch:* Jun 11 21:35:45 zrh02-srv03 /usr/local/sbin/kamailio[7135]: WARNING: tls [tls_init.c:793]: tls_h_mod_init_f(): openssl bug #1491 (crash/mem leaks on low memory) workaround enabled (on low memory tls operations will fail preemptively) with free memory thresholds 13107200 and 6553600 bytes Jun 11 21:35:45 zrh02-srv03 /usr/local/sbin/kamailio[7135]: NOTICE: tls [tls_domain.c:1136]: ksr_tls_fix_domain(): registered server_name callback handler for socket [:0], server_name='' ... Jun 11 21:35:46 zrh02-srv03 kernel: [304361.950608] traps: kamailio[7147] general protection ip:7f5d209a344b sp:7ffe6ae5adb8 error:0 in libcrypto.so.1.1[7f5d207b5000+29b000] Jun 11 21:35:46 zrh02-srv03 systemd[1]: Started Kamailio SIP Server. Jun 11 21:35:54 zrh02-srv03 /usr/local/sbin/kamailio[7161]: CRITICAL: [core/pass_fd.c:277]: receive_fd(): EOF on 26 Jun 11 21:35:54 zrh02-srv03 /usr/local/sbin/kamailio[7135]: ALERT: [main.c:788]: handle_sigs(): child process 7147 exited by a signal 11 Jun 11 21:35:54 zrh02-srv03 /usr/local/sbin/kamailio[7135]: ALERT: [main.c:791]: handle_sigs(): core was generated Jun 11 21:35:54 zrh02-srv03 systemd[1]: kamailio.service: Main process exited, code=exited, status=1/FAILURE Jun 11 21:35:54 zrh02-srv03 systemd[1]: kamailio.service: Failed with result 'exit-code'. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/. Find the GDB manual and other documentation resources online at: http://www.gnu.org/software/gdb/documentation/. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/local/sbin/kamailio...done. [New LWP 7147] [Thread debugging using libthread_db enabled
Re: [SR-Users] Kamailio 5.5.0 | CRITICAL: [core/pass_fd.c:277]: receive_fd(): EOF on 26
Hello, Sorry, idea was to test the 5.6.0 and not the 5.5.0, so I will try again BR Laurent From: Laurent Schweizer Sent: vendredi, 11 juin 2021 23:49 To: Kamailio (SER) - Users Mailing List Subject: Kamailio 5.5.0 | CRITICAL: [core/pass_fd.c:277]: receive_fd(): EOF on 26 Dear all, I setup a Kamailio 5.5.0 (from GIT) on a ubuntu Ubuntu 18.04.5 LTS and I have some error with the libssl/ libmysql, seems not happening every time. Regarding the config file, it’s a config running correctly on a Kamailio 5.3.x on a centos 7 I have attached the returned error and the result of the core file. Any idea ? BR Laurent version: kamailio 5.5.0 (x86_64/linux) 66370c flags: 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_BLOCKLIST, HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED 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: 66370c compiled on 07:23:15 Jun 11 2021 with gcc 7.5.0 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: loading modules under config path: /usr/local/lib64/kamailio/modules/ Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: Listening on Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: udp: 80.132.9.112:5060 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: udp: 80.132.9.112:6000 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: tcp: 80.132.9.112:5060 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: tcp: 80.132.9.112:6000 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: tls: 80.132.9.112:5061 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: Aliases: Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: tls: zrh02-srv03:5061 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: tcp: zrh02-srv03:6000 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: tcp: zrh02-srv03:5060 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: udp: zrh02-srv03:6000 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: udp: zrh02-srv03:5060 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: *: sipbkp.demo.ch:* Jun 11 21:35:45 zrh02-srv03 /usr/local/sbin/kamailio[7135]: WARNING: tls [tls_init.c:793]: tls_h_mod_init_f(): openssl bug #1491 (crash/mem leaks on low memory) workaround enabled (on low memory tls operations will fail preemptively) with free memory thresholds 13107200 and 6553600 bytes Jun 11 21:35:45 zrh02-srv03 /usr/local/sbin/kamailio[7135]: NOTICE: tls [tls_domain.c:1136]: ksr_tls_fix_domain(): registered server_name callback handler for socket [:0], server_name='' ... Jun 11 21:35:46 zrh02-srv03 kernel: [304361.950608] traps: kamailio[7147] general protection ip:7f5d209a344b sp:7ffe6ae5adb8 error:0 in libcrypto.so.1.1[7f5d207b5000+29b000] Jun 11 21:35:46 zrh02-srv03 systemd[1]: Started Kamailio SIP Server. Jun 11 21:35:54 zrh02-srv03 /usr/local/sbin/kamailio[7161]: CRITICAL: [core/pass_fd.c:277]: receive_fd(): EOF on 26 Jun 11 21:35:54 zrh02-srv03 /usr/local/sbin/kamailio[7135]: ALERT: [main.c:788]: handle_sigs(): child process 7147 exited by a signal 11 Jun 11 21:35:54 zrh02-srv03 /usr/local/sbin/kamailio[7135]: ALERT: [main.c:791]: handle_sigs(): core was generated Jun 11 21:35:54 zrh02-srv03 systemd[1]: kamailio.service: Main process exited, code=exited, status=1/FAILURE Jun 11 21:35:54 zrh02-srv03 systemd[1]: kamailio.service: Failed with result 'exit-code'. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/. Find the GDB manual and other documentation resources online at: http://www.gnu.org/software/gdb/documentation/. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/local/sbin/kamailio...done. [New LWP 7147] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/usr/local/sbin/kamailio -m 5000 -M 128 -P /run/kamailio/kamailio.pid -f /confi'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7f5d209a344b in X509_LOOKUP_by_subject () from /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 (gdb) bt #0 0x7f5d209a344b in X509_LOOKUP_by_subject () from /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 #1 0x7f5d209a3a5b in X509_STORE_CTX_get_by_subject () from /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 #2 0x7f5d209a418d in X509_STORE_CTX_get1_issuer () from /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 #3 0x7f5d209a9207 in ?? () from /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 #4 0x7f5d209a9f96 in X509_verify_cert () from /usr/
[SR-Users] Kamailio 5.5.0 | CRITICAL: [core/pass_fd.c:277]: receive_fd(): EOF on 26
Dear all, I setup a Kamailio 5.5.0 (from GIT) on a ubuntu Ubuntu 18.04.5 LTS and I have some error with the libssl/ libmysql, seems not happening every time. Regarding the config file, it's a config running correctly on a Kamailio 5.3.x on a centos 7 I have attached the returned error and the result of the core file. Any idea ? BR Laurent version: kamailio 5.5.0 (x86_64/linux) 66370c flags: 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_BLOCKLIST, HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED 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: 66370c compiled on 07:23:15 Jun 11 2021 with gcc 7.5.0 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: loading modules under config path: /usr/local/lib64/kamailio/modules/ Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: Listening on Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: udp: 80.132.9.112:5060 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: udp: 80.132.9.112:6000 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: tcp: 80.132.9.112:5060 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: tcp: 80.132.9.112:6000 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: tls: 80.132.9.112:5061 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: Aliases: Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: tls: zrh02-srv03:5061 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: tcp: zrh02-srv03:6000 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: tcp: zrh02-srv03:5060 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: udp: zrh02-srv03:6000 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: udp: zrh02-srv03:5060 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: *: sipbkp.demo.ch:* Jun 11 21:35:45 zrh02-srv03 /usr/local/sbin/kamailio[7135]: WARNING: tls [tls_init.c:793]: tls_h_mod_init_f(): openssl bug #1491 (crash/mem leaks on low memory) workaround enabled (on low memory tls operations will fail preemptively) with free memory thresholds 13107200 and 6553600 bytes Jun 11 21:35:45 zrh02-srv03 /usr/local/sbin/kamailio[7135]: NOTICE: tls [tls_domain.c:1136]: ksr_tls_fix_domain(): registered server_name callback handler for socket [:0], server_name='' ... Jun 11 21:35:46 zrh02-srv03 kernel: [304361.950608] traps: kamailio[7147] general protection ip:7f5d209a344b sp:7ffe6ae5adb8 error:0 in libcrypto.so.1.1[7f5d207b5000+29b000] Jun 11 21:35:46 zrh02-srv03 systemd[1]: Started Kamailio SIP Server. Jun 11 21:35:54 zrh02-srv03 /usr/local/sbin/kamailio[7161]: CRITICAL: [core/pass_fd.c:277]: receive_fd(): EOF on 26 Jun 11 21:35:54 zrh02-srv03 /usr/local/sbin/kamailio[7135]: ALERT: [main.c:788]: handle_sigs(): child process 7147 exited by a signal 11 Jun 11 21:35:54 zrh02-srv03 /usr/local/sbin/kamailio[7135]: ALERT: [main.c:791]: handle_sigs(): core was generated Jun 11 21:35:54 zrh02-srv03 systemd[1]: kamailio.service: Main process exited, code=exited, status=1/FAILURE Jun 11 21:35:54 zrh02-srv03 systemd[1]: kamailio.service: Failed with result 'exit-code'. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/. Find the GDB manual and other documentation resources online at: http://www.gnu.org/software/gdb/documentation/. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/local/sbin/kamailio...done. [New LWP 7147] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/usr/local/sbin/kamailio -m 5000 -M 128 -P /run/kamailio/kamailio.pid -f /confi'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7f5d209a344b in X509_LOOKUP_by_subject () from /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 (gdb) bt #0 0x7f5d209a344b in X509_LOOKUP_by_subject () from /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 #1 0x7f5d209a3a5b in X509_STORE_CTX_get_by_subject () from /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 #2 0x7f5d209a418d in X509_STORE_CTX_get1_issuer () from /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 #3 0x7f5d209a9207 in ?? () from /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 #4 0x7f5d209a9f96 in X509_verify_cert () from /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 #5 0x7f5d20caf337 in ?? () from /usr/lib/x86_64-linux-gnu/libssl.so.1.1 #6 0x7f5d20cd037b in ?? () from /usr/lib/x86_64-linux-gnu/libssl.so.1.1 #7 0x7f5d20cd2995 in ?? () from /usr/lib/x86_64-linux-gnu/libssl.so.1.1 #8 0x7f5d20ccc48c in ?? () from
Re: [SR-Users] RTPengine with rejected RE-INVITE when port is changing
Hello, Sorry for the confusion. The point is the following: 1) call is setup correctly 2) just after one side send a RE-INVITE with a new port and new codec. 3) The other leg reject the RE-INVITE with a 415 During the RE-INVITE, the first RTP relay on RTPengine is removed (with a delay of 30 sec). As the RE-INVITE with the new port is rejected the current RTP relay is still used, so we must not delete them. BR Laurent -Original Message- From: sr-users On Behalf Of Daniel-Constantin Mierla Sent: jeudi, 5 décembre 2019 11:46 To: sr-users@lists.kamailio.org; Daniel Tryba Subject: Re: [SR-Users] RTPengine with rejected RE-INVITE when port is changing On 05.12.19 11:33, Daniel Tryba wrote: > On Thu, Dec 05, 2019 at 09:37:51AM +0000, Laurent Schweizer wrote: >> Hello, >> >> I already see old post about this : >> https://opensips.org/pipermail/users/2014-November/030451.html >> >> but I???m interested to know if now they is a solution >> >> so the issue is a RE-INVITE rejected (415 Unsupported Media or 488 ) and the >> RTP port is changing. >> Is that case the old RTP relay (I???m using RTPengine) is destroyed after >> 30sec. >> Any way to restore them ? > I'm confused: > - opensips != kamailio > - rtpproxy != rtpengine > > But RFC 3261 states (page 16): > >During the session, either Alice or Bob may decide to change the >characteristics of the media session. This is accomplished by >sending a re-INVITE containing a new media description. This re- >INVITE references the existing dialog so that the other party knows >that it is to modify an existing session instead of establishing a >new session. The other party sends a 200 (OK) to accept the change. >The requestor responds to the 200 (OK) with an ACK. If the other >party does not accept the change, he sends an error response such as >488 (Not Acceptable Here), which also receives an ACK. However, the >failure of the re-INVITE does not cause the existing call to fail - >the session continues using the previously negotiated >characteristics. Full details on session modification are in Section >14. > > So if this happens with kamailio/rtpengine that is a bug in (I presume) > rtpengine. RTPEngine itself doesn't send SIP replies. Typically the 415 or 488 are sent by the endpoints. Kamailio doesn't do it by default, but of course can do it if explicitely wanted in the kamailio .cfg routing actions. My guess is that the endpoint sends the 415/488, so all this doesn't have to do anything with rtpengine/kamailio -- that can be checked by looking at the sip network traffic on kamailio server to see where 415/488 is coming from. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - April 27-29, 2020, in Berlin -- www.kamailioworld.com ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] RTPengine with rejected RE-INVITE when port is changing
Hello, I already see old post about this : https://opensips.org/pipermail/users/2014-November/030451.html but I’m interested to know if now they is a solution so the issue is a RE-INVITE rejected (415 Unsupported Media or 488 ) and the RTP port is changing. Is that case the old RTP relay (I’m using RTPengine) is destroyed after 30sec. Any way to restore them ? BR Laurent ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] Kamailio 5.0.8 | authentification issue only with TCP/TLS
Hi Henning,
Hi all,
Maybe my first assumption was wrong, the wrong result is changing ☹.
I have added some extra debug info in modules/auth_db/authorize.c to display
not only the calculated hash but also the username, domain and password
if (calc_ha1) {
/* Only plaintext passwords are stored in database,
* we have to calculate HA1 */
auth_api.calc_HA1(HA_MD5, &_username->whole, _domain, ,
0, 0, _ha1);
LM_DBG("FOR NU HA1 string calculated: %s username:\'%.*s\'
realm:\'%.*s\' pass:\'%.*s\' \n", _ha1 , _username->user.len,
ZSW(_username->user.s) , (_domain->len) , ZSW(_domain->s), result.len ,
result.s);
} else {
memcpy(_ha1, result.s, result.len);
_ha1[result.len] = '\0';
}
return 0;
and I see for the same username different password … of course password was
not changed in DB
password are not random, it’s password from other user, just one case that is
different is the “0” (we don’t have any user with a password like this )
Aug 30 09:37:02 de5029 kamailio[21409]: DEBUG: auth_db [authorize.c:199]:
get_ha1(): FOR NU HA1 string calculated: 5057166924cd85af0250c36d24eb
username:'90707009764' realm:'pbxs.peoplefone.de' pass:'H3--D'
Aug 30 09:37:02 de5029 kamailio[21409]: DEBUG: auth_db [authorize.c:199]:
get_ha1(): FOR NU HA1 string calculated: 7547ba1f80a651437908d050493086f9
username:'90707009764' realm:'pbxs.peoplefone.de' pass:'R3--2'
Aug 30 09:37:03 de5029 kamailio[21409]: DEBUG: auth_db [authorize.c:199]:
get_ha1(): FOR NU HA1 string calculated: 8947348b1af4cba356532c3b49dba559
username:'90707009764' realm:'pbxs.peoplefone.de' pass:'72--s'
Aug 30 09:37:03 de5029 kamailio[21409]: DEBUG: auth_db [authorize.c:199]:
get_ha1(): FOR NU HA1 string calculated: 348ce71603d44a0dd3303d8e07e155d8
username:'90707009764' realm:'pbxs.peoplefone.de' pass:'X-g'
Aug 30 09:37:04 de5029 kamailio[21409]: DEBUG: auth_db [authorize.c:199]:
get_ha1(): FOR NU HA1 string calculated: 7fc7adfa1f3a18d27988ffbe42ecfdfd
username:'90707009764' realm:'pbxs.peoplefone.de' pass:'0'
Aug 30 09:37:35 de5029 kamailio[21409]: DEBUG: auth_db [authorize.c:199]:
get_ha1(): FOR NU HA1 string calculated: b313ccfd2848fdc245cc1490607e6eb7
username:'90707009764' realm:'pbxs.peoplefone.de' pass:'s---w'
I’m using a mysql/percona DB with 3 server so I’m using the db_cluster module…
Any idea ?
BR
Laurent
From: Henning Westerholt
Sent: jeudi, 29 août 2019 18:28
To: Kamailio (SER) - Users Mailing List ; Laurent
Schweizer
Subject: Re: [SR-Users] Kamailio 5.0.8 | authentification issue only with
TCP/TLS
Hello Laurent,
(you might want to anonymize your msg dumps bit on this public list)
You probably did already this steps, but nevertheless some debugging ideas:
- capture a longer network trace and compare the network data of a working
against non-working case
- try to see to find a pattern (e.g. does it happens during a certain time,
only to certain users or devices)
- have a look to network interface statistics on server and router/firewall if
maybe some corruption is caused from an interface
- have a look to other network services that are using the same network
infrastructure to see if they are also affected
Cheers,
Henning
Am 29.08.19 um 10:58 schrieb Laurent Schweizer:
Hello,
I try to get some log,
I only see that password seems wrong but he was not changed and registration of
this user was ok just before ☹
Any idea how to debug this ?
Aug 29 10:21:38 de5029 kamailio[22615]: DEBUG: auth [api.c:288]:
auth_check_response(): check_response: Our result =
'bc946bb4ea732eb35d11d0970631c6f8'
Aug 29 10:21:38 de5029 kamailio[22615]: DEBUG: auth [api.c:298]:
auth_check_response(): check_response: Authorization failed
Aug 29 10:21:38 de5029 kamailio[22615]: WARNING:
Re: [SR-Users] Kamailio 5.0.8 | authentification issue only with TCP/TLS
Hello, I try to get some log, I only see that password seems wrong but he was not changed and registration of this user was ok just before ☹ Any idea how to debug this ? Aug 29 10:21:38 de5029 kamailio[22615]: DEBUG: auth [api.c:288]: auth_check_response(): check_response: Our result = 'bc946bb4ea732eb35d11d0970631c6f8' Aug 29 10:21:38 de5029 kamailio[22615]: DEBUG: auth [api.c:298]: auth_check_response(): check_response: Authorization failed Aug 29 10:21:38 de5029 kamailio[22615]: WARNING:
Re: [SR-Users] Kamailio 5.0.8 | authentification issue only with TCP/TLS
Wireshark was missing .
From: Laurent Schweizer
Sent: lundi, 26 août 2019 10:25
To: 'Kamailio (SER) - Users Mailing List'
Subject: Kamailio 5.0.8 | authentification issue only with TCP/TLS
Dear all,
I have a kamailio running in version 5.0.8 and since fee weeks we have an issue
with different users connected in TCP or TLS, sometimes authorization like for
REGISTER are rejected and after a moment (can be few minute or hours) it work
again and of course no change was done in the password
We see this issue with different device, snom swyx, ... and on UDP we have no
issue.
I can see that when the Register is rejected it's with the error -2, so wrong
password...
# Authentication route
route[AUTH] {
if (is_method("REGISTER"))
{
# authenticate requests
if (!auth_check("$fd", "subscriber", "1")) {
switch($retcode) {
case -1:
sl_send_reply("503","Service not
available");
exit;
case -2:
xlog("L_WARN", "auth error -2 username
$au - src ip: $si \n");
auth_challenge("$fd", "0");
exit;
I have attached an example of a trace where we can see a first REGISTER
accepted and less than 2 minutes after a new one is rejected. ( in between
they is a REGISTER without any Authorization header)
Any idea ?
BR
Laurent
<>
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] Kamailio 5.0.8 | authentification issue only with TCP/TLS
Dear all,
I have a kamailio running in version 5.0.8 and since fee weeks we have an issue
with different users connected in TCP or TLS, sometimes authorization like for
REGISTER are rejected and after a moment (can be few minute or hours) it work
again and of course no change was done in the password
We see this issue with different device, snom swyx, ... and on UDP we have no
issue.
I can see that when the Register is rejected it's with the error -2, so wrong
password...
# Authentication route
route[AUTH] {
if (is_method("REGISTER"))
{
# authenticate requests
if (!auth_check("$fd", "subscriber", "1")) {
switch($retcode) {
case -1:
sl_send_reply("503","Service not
available");
exit;
case -2:
xlog("L_WARN", "auth error -2 username
$au - src ip: $si \n");
auth_challenge("$fd", "0");
exit;
I have attached an example of a trace where we can see a first REGISTER
accepted and less than 2 minutes after a new one is rejected. ( in between
they is a REGISTER without any Authorization header)
Any idea ?
BR
Laurent
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] Kamailio with RTPengine, allow source port of RTP to change during a call
Hello, I'm using the RTPengine with Kamailio and I have a question for a specific case. I have some customer that are changing the source port of the RTP stream during the call ( no re-invite) I think it's more a NAT issue that a user agent issue... I see in the doc that I can handle this case with the "media handover" but in that case the rtpengine will allow a change of the source port but also of the source IP. Any possibility to allow only a change of the source port so source IP must still be the same ? Thanks BR Laurent ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] authentification issue when nb user increase
Hello, I have a proxy with Kamailio 5.0.6 working since few month without any issue. Around 4500 locations and 5300 contacts This weekend we move a very old proxy (Kamailio 3.3.2 with an old server )to this new one, adding around 14’000 users and 15’000 contacts. Yesterday when calls was starting we get an big issue with this new proxy, lot of phones was disconnected and some calls was rejected. I see that the issue was the authentication (done via a mysql DB with the cluster db module) many phone get a failure and was disconnected, mostly phone connected via TCP or TLS we see less issue with UDP even we have much more . The issue was not the number of TCP/TLS connection as we see the REGISTER and the 401 going back, so connection was correctly done Currently it’s working but I don’t know exactly why ☹, I mean I have done a change but it has really no relation … , during the same time I get another issue, some calls have no voice… We are using rtpengine (on the old proxy we was using rtpproxy) and with the rtproxy we already face a long time ago such case and to solve it we setup multiple rtpproxy (on the same host) So I try to do the same, I setup a second rtpengine on the same host and when I reload the config with : kamcmd rtpengine.reload all registration was working perfectly ... As they is no relation with the registration end the rtpengine I don't know why now it's working. Any idea ? BR Laurent ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] : hight shared memory usage
Hello, No, both server have the same script, the only difference is that they are connected to different DB. We increase the max TLS connections because we plan to move some customer on this proxy and we want to be ready to accept more than 2K TLS connection . Laurent -Message d'origine- De : Henning Westerholt Envoyé : mercredi, 24 octobre 2018 22:46 À : sr-users@lists.kamailio.org Cc : Laurent Schweizer Objet : [JUNK-SPAM] Re: [SR-Users] : hight shared memory usage Am Mittwoch, 24. Oktober 2018, 15:24:05 CEST schrieb Laurent Schweizer: > I have 2 proxy running and we have a very big difference of memory > usage between them, moreover we have more connected users on the proxy > with less memory usage. > > We have this issue on the first proxy, today we have to increase the > shared memory as it was no more possible to setup new TCP connection. > > We use the same version of the proxy, script is quite the same, one > difference, on the proxy with the issue we increase the number of max > TLS connection to 20K > > Any idea ? > is TLS consuming more memory than TCP or UDP ? Hello Laurent, TLS is using more memory than TCP and than UDP, due to the higher workload and overhead for crypto/connection tracking. But looking to your registered user count this should not make a big difference in the end. Do you have maybe a different usage pattern on the first proxy comparing to the second one? So that different parts of the cfg or the code are executed? Why do you increased the number of max TLS connections on the first proxy, you had also some issues here? > First proxy (with high memory usage): > > > [cycle #: 3; if constant make sure server lives] Kamailio Runtime > Details: > kamailio 5.0.6 (x86_64/linux) > now: Wed Oct 24 15:18:55 2018 > up_since: Wed Oct 24 13:21:12 2018 > uptime: 7063 > > Transaction Statistics: > tmx:UAS_transactions = 56240tmx:active_transactions = 4 > tmx:UAC_transactions = 0tmx:inuse_transactions = 18 > > Stateless Server Statistics: > sl:sent_replies = 134317sl:sent_err_replies = 0 > > UsrLoc Statistics: > usrloc:location_ch-contacts = 1463 usrloc:location_ch-users = 1181 > usrloc:location_ch-expires = 1076 usrloc:registered_users = 1181 > > Core Statistics: > core:rcv_requests = 214220 core:rcv_replies = 179145 > core:fwd_requests = 5495core:fwd_replies = 73 > > Shared Memory Statistics: > shmem:fragments = 529 shmem:real_used_size = > 15862690496 shmem:free_size = 36566109504 shmem:total_size = > 5242880 shmem:max_used_size = 16198927224 shmem:used_size = > 15854961104 > > > > cat /proc/net/netstat | cut -d" " -f12-17 ; cat /proc/net/sockstat TW > TWRecycled TWKilled PAWSPassive PAWSActive PAWSEstab > 339118 0 684 3195 0 4648 > InBcastOctets OutBcastOctets InCsumErrors InNoECTPkts InECT1Pkts > InECT0Pkts > 14620680 0 0 19142166496 9683 133135 > sockets: used 1951 > TCP: inuse 1029 orphan 0 tw 2 alloc 1036 mem 15 > UDP: inuse 540 mem 446 > UDPLITE: inuse 0 > RAW: inuse 0 > FRAG: inuse 0 memory 0 > > > > --- > > > Second proxy (memory is OK) : > > [cycle #: 2; if constant make sure server lives] Kamailio Runtime > Details: > kamailio 5.0.6 (x86_64/linux) > now: Wed Oct 24 15:19:39 2018 > up_since: Mon Jul 2 00:31:48 2018 > uptime: 9902871 > > Transaction Statistics: > tmx:UAS_transactions = 86712048 tmx:active_transactions = 92 > tmx:UAC_transactions = 0tmx:inuse_transactions = 178 > > Stateless Server Statistics: > sl:sent_replies = 641635175 sl:sent_err_replies = 0 > > UsrLoc Statistics: > usrloc:location-contacts = 3971 usrloc:location-users = 3845 > usrloc:location-expires = 286685usrloc:registered_users = 3845 > > Core Statistics: > core:rcv_requests = 752644955 core:rcv_replies = 1181197213 > core:fwd_requests = 14482059core:fwd_replies = 206909 > > Shared Memory Statistics: > shmem:fragments = 28437 shmem:real_used_size = 56447456 > shmem:free_size = 2091036192shmem:total_size = 2147483648 > shmem:max_used_size = 82099768 shmem:used_size = 43354160 > > > cat /proc/net/netstat | cut -d" " -f12-17 ; cat /proc/net/sockstat TW > TWRecycled TWKilled PAWSPassive PAWSActive PAWSEstab > 273625 0 0 0 0 3524 > InBcastOctets OutBcastOctets InCsumErrors InNoECTPkts InECT1Pkts > InECT0Pkts > 2010 0 1 179031265416 81564 21432766 > sockets: used 4964 > TCP: inuse 576 orph
Re: [SR-Users] : hight shared memory usage
More info :
kamcmd core.tcp_info
{
readers: 10
max_connections: 20409
max_tls_connections: 20409
opened_connections: 908
opened_tls_connections: 709
write_queued_bytes: 0
}
kamcmd tls.info
{
max_connections: 20409
opened_connections: 709
clear_text_write_queued_bytes: 0
}
Any idea is welcome
BR
Laurent
De : sr-users De la part de Laurent
Schweizer
Envoyé : mercredi, 24 octobre 2018 15:54
À : Kamailio (SER) - Users Mailing List
Objet : Re: [SR-Users] : hight shared memory usage
On more info on the shared mem usage :
tcpconn_new(957): -1274304104
kamcmd mod.stats all shm
Module: core
{
sip_msg_shm_clone(495): 196272
msg_lump_cloner(984): 55648
create_avp(175): 424
tcpconn_new(957): -1274304104
build_req_buf_from_sip_req(2162): 42704
counters_prefork_init(207): 51200
cfg_clone_str(130): 160
cfg_shmize(217): 984
init_pt(113): 8
init_pt(108): 8
init_pt(107): 7000
cfg_parse_str(906): 80
register_timer(1012): 360
cfg_register_ctx(47): 96
init_tcp(4649): 8192
init_tcp(4643): 32768
init_tcp(4635): 8
init_tcp(4628): 8
init_tcp(4621): 8
init_tcp(4615): 8
init_tcp(4603): 8
init_avps(90): 8
init_avps(89): 8
init_dst_blacklist(437): 16384
init_dst_blacklist(430): 8
timer_alloc(515): 96
init_dns_cache(369): 8
init_dns_cache(361): 16384
init_dns_cache(354): 16
init_dns_cache(345): 8
init_timer(284): 8
init_timer(283): 16384
init_timer(282): 8
init_timer(281): 8
init_timer(270): 8
init_timer(238): 8
init_timer(221): 278544
init_timer(220): 8
init_timer(207): 8
cfg_child_cb_new(830): 64
sr_cfg_init(361): 8
sr_cfg_init(354): 8
sr_cfg_init(347): 8
sr_cfg_init(335): 8
sr_cfg_init(323): 8
shm_core_lock_init(153): 8
Total: -1273580144
}
De : sr-users
mailto:sr-users-boun...@lists.kamailio.org>>
De la part de Laurent Schweizer
Envoyé : mercredi, 24 octobre 2018 15:24
À : sr-users@lists.kamailio.org<mailto:sr-users@lists.kamailio.org>
Objet : [SR-Users] : hight shared memory usage
Dear all,
I have 2 proxy running and we have a very big difference of memory usage
between them, moreover we have more connected users on the proxy with less
memory usage.
We have this issue on the first proxy, today we have to increase the shared
memory as it was no more possible to setup new TCP connection.
We use the same version of the proxy, script is quite the same, one difference,
on the proxy with the issue we increase the number of max TLS connection to 20K
Any idea ?
is TLS consuming more memory than TCP or UDP ?
BR
Laurent
First proxy (with high memory usage):
[cycle #: 3; if constant make sure server lives]
Kamailio Runtime Details:
kamailio 5.0.6 (x86_64/linux)
now: Wed Oct 24 15:18:55 2018
up_since: Wed Oct 24 13:21:12 2018
uptime: 7063
Transaction Statistics:
tmx:UAS_transactions = 56240tmx:active_transactions = 4
tmx:UAC_transactions = 0tmx:inuse_transactions = 18
Stateless Server Statistics:
sl:sent_replies = 134317sl:sent_err_replies = 0
UsrLoc Statistics:
usrloc:location_ch-contacts = 1463 usrloc:location_ch-users = 1181
usrloc:location_ch-expires = 1076 usrloc:registered_users = 1181
Core Statistics:
core:rcv_requests = 214220 core:rcv_replies = 179145
core:fwd_requests = 5495core:fwd_replies = 73
Shared Memory Statistics:
shmem:fragments = 529 shmem:real_used_size = 15862690496
shmem:free_size = 36566109504 shmem:total_size = 5242880
shmem:max_used_size = 16198927224 shmem:used_size = 15854961104
cat /proc/net/netstat | cut -d" " -f12-17 ; cat /proc/net/sockstat
TW TWRecycled TWKilled PAWSPassive PAWSActive PAWSEstab
339118 0 684 3195 0 4648
InBcastOctets OutBcastOctets InCsumErrors InNoECTPkts InECT1Pkts InECT0Pkts
14620680 0 0 19142166496 9683 133135
sockets: used 1951
TCP: inuse 1029 orphan 0 tw 2 alloc 1036 mem 15
UDP: inuse 540 mem 446
UDPLITE: inuse 0
RAW: inuse 0
FRAG: inuse 0 memory 0
---
Second proxy (memory is OK) :
[cycle #: 2; if constant make sure server lives]
Kamailio Runtime Details:
kamailio 5.0.6 (x86_64/linux)
now: Wed Oct 24 15:19:39 2018
up_since: Mon Jul 2 00:31:48 2018
uptime: 9902871
Transaction Statistics:
tmx:UAS_transactions = 86712048 tmx:active_transactions = 92
tmx:UAC_transactions = 0tmx:inuse_transactions = 178
Stateless Server Statistics:
sl:sent_replies = 641635175 sl:sent_err_replies = 0
UsrLoc Statistics:
usrloc:lo
Re: [SR-Users] : hight shared memory usage
On more info on the shared mem usage :
tcpconn_new(957): -1274304104
kamcmd mod.stats all shm
Module: core
{
sip_msg_shm_clone(495): 196272
msg_lump_cloner(984): 55648
create_avp(175): 424
tcpconn_new(957): -1274304104
build_req_buf_from_sip_req(2162): 42704
counters_prefork_init(207): 51200
cfg_clone_str(130): 160
cfg_shmize(217): 984
init_pt(113): 8
init_pt(108): 8
init_pt(107): 7000
cfg_parse_str(906): 80
register_timer(1012): 360
cfg_register_ctx(47): 96
init_tcp(4649): 8192
init_tcp(4643): 32768
init_tcp(4635): 8
init_tcp(4628): 8
init_tcp(4621): 8
init_tcp(4615): 8
init_tcp(4603): 8
init_avps(90): 8
init_avps(89): 8
init_dst_blacklist(437): 16384
init_dst_blacklist(430): 8
timer_alloc(515): 96
init_dns_cache(369): 8
init_dns_cache(361): 16384
init_dns_cache(354): 16
init_dns_cache(345): 8
init_timer(284): 8
init_timer(283): 16384
init_timer(282): 8
init_timer(281): 8
init_timer(270): 8
init_timer(238): 8
init_timer(221): 278544
init_timer(220): 8
init_timer(207): 8
cfg_child_cb_new(830): 64
sr_cfg_init(361): 8
sr_cfg_init(354): 8
sr_cfg_init(347): 8
sr_cfg_init(335): 8
sr_cfg_init(323): 8
shm_core_lock_init(153): 8
Total: -1273580144
}
De : sr-users De la part de Laurent
Schweizer
Envoyé : mercredi, 24 octobre 2018 15:24
À : sr-users@lists.kamailio.org
Objet : [SR-Users] : hight shared memory usage
Dear all,
I have 2 proxy running and we have a very big difference of memory usage
between them, moreover we have more connected users on the proxy with less
memory usage.
We have this issue on the first proxy, today we have to increase the shared
memory as it was no more possible to setup new TCP connection.
We use the same version of the proxy, script is quite the same, one difference,
on the proxy with the issue we increase the number of max TLS connection to 20K
Any idea ?
is TLS consuming more memory than TCP or UDP ?
BR
Laurent
First proxy (with high memory usage):
[cycle #: 3; if constant make sure server lives]
Kamailio Runtime Details:
kamailio 5.0.6 (x86_64/linux)
now: Wed Oct 24 15:18:55 2018
up_since: Wed Oct 24 13:21:12 2018
uptime: 7063
Transaction Statistics:
tmx:UAS_transactions = 56240tmx:active_transactions = 4
tmx:UAC_transactions = 0tmx:inuse_transactions = 18
Stateless Server Statistics:
sl:sent_replies = 134317sl:sent_err_replies = 0
UsrLoc Statistics:
usrloc:location_ch-contacts = 1463 usrloc:location_ch-users = 1181
usrloc:location_ch-expires = 1076 usrloc:registered_users = 1181
Core Statistics:
core:rcv_requests = 214220 core:rcv_replies = 179145
core:fwd_requests = 5495core:fwd_replies = 73
Shared Memory Statistics:
shmem:fragments = 529 shmem:real_used_size = 15862690496
shmem:free_size = 36566109504 shmem:total_size = 5242880
shmem:max_used_size = 16198927224 shmem:used_size = 15854961104
cat /proc/net/netstat | cut -d" " -f12-17 ; cat /proc/net/sockstat
TW TWRecycled TWKilled PAWSPassive PAWSActive PAWSEstab
339118 0 684 3195 0 4648
InBcastOctets OutBcastOctets InCsumErrors InNoECTPkts InECT1Pkts InECT0Pkts
14620680 0 0 19142166496 9683 133135
sockets: used 1951
TCP: inuse 1029 orphan 0 tw 2 alloc 1036 mem 15
UDP: inuse 540 mem 446
UDPLITE: inuse 0
RAW: inuse 0
FRAG: inuse 0 memory 0
---
Second proxy (memory is OK) :
[cycle #: 2; if constant make sure server lives]
Kamailio Runtime Details:
kamailio 5.0.6 (x86_64/linux)
now: Wed Oct 24 15:19:39 2018
up_since: Mon Jul 2 00:31:48 2018
uptime: 9902871
Transaction Statistics:
tmx:UAS_transactions = 86712048 tmx:active_transactions = 92
tmx:UAC_transactions = 0tmx:inuse_transactions = 178
Stateless Server Statistics:
sl:sent_replies = 641635175 sl:sent_err_replies = 0
UsrLoc Statistics:
usrloc:location-contacts = 3971 usrloc:location-users = 3845
usrloc:location-expires = 286685usrloc:registered_users = 3845
Core Statistics:
core:rcv_requests = 752644955 core:rcv_replies = 1181197213
core:fwd_requests = 14482059core:fwd_replies = 206909
Shared Memory Statistics:
shmem:fragments = 28437 shmem:real_used_size = 56447456
shmem:free_size = 2091036192shmem:total_size = 2147483648
shmem:max_used_size = 82099768 shmem:used_size = 43354160
cat /proc/net/netstat | cut -d" " -f12-17 ; cat /proc/net/sockstat
TW TWRecycled TWKilled PAWSPassive PAWSActive PAWS
[SR-Users] : hight shared memory usage
Dear all, I have 2 proxy running and we have a very big difference of memory usage between them, moreover we have more connected users on the proxy with less memory usage. We have this issue on the first proxy, today we have to increase the shared memory as it was no more possible to setup new TCP connection. We use the same version of the proxy, script is quite the same, one difference, on the proxy with the issue we increase the number of max TLS connection to 20K Any idea ? is TLS consuming more memory than TCP or UDP ? BR Laurent First proxy (with high memory usage): [cycle #: 3; if constant make sure server lives] Kamailio Runtime Details: kamailio 5.0.6 (x86_64/linux) now: Wed Oct 24 15:18:55 2018 up_since: Wed Oct 24 13:21:12 2018 uptime: 7063 Transaction Statistics: tmx:UAS_transactions = 56240tmx:active_transactions = 4 tmx:UAC_transactions = 0tmx:inuse_transactions = 18 Stateless Server Statistics: sl:sent_replies = 134317sl:sent_err_replies = 0 UsrLoc Statistics: usrloc:location_ch-contacts = 1463 usrloc:location_ch-users = 1181 usrloc:location_ch-expires = 1076 usrloc:registered_users = 1181 Core Statistics: core:rcv_requests = 214220 core:rcv_replies = 179145 core:fwd_requests = 5495core:fwd_replies = 73 Shared Memory Statistics: shmem:fragments = 529 shmem:real_used_size = 15862690496 shmem:free_size = 36566109504 shmem:total_size = 5242880 shmem:max_used_size = 16198927224 shmem:used_size = 15854961104 cat /proc/net/netstat | cut -d" " -f12-17 ; cat /proc/net/sockstat TW TWRecycled TWKilled PAWSPassive PAWSActive PAWSEstab 339118 0 684 3195 0 4648 InBcastOctets OutBcastOctets InCsumErrors InNoECTPkts InECT1Pkts InECT0Pkts 14620680 0 0 19142166496 9683 133135 sockets: used 1951 TCP: inuse 1029 orphan 0 tw 2 alloc 1036 mem 15 UDP: inuse 540 mem 446 UDPLITE: inuse 0 RAW: inuse 0 FRAG: inuse 0 memory 0 --- Second proxy (memory is OK) : [cycle #: 2; if constant make sure server lives] Kamailio Runtime Details: kamailio 5.0.6 (x86_64/linux) now: Wed Oct 24 15:19:39 2018 up_since: Mon Jul 2 00:31:48 2018 uptime: 9902871 Transaction Statistics: tmx:UAS_transactions = 86712048 tmx:active_transactions = 92 tmx:UAC_transactions = 0tmx:inuse_transactions = 178 Stateless Server Statistics: sl:sent_replies = 641635175 sl:sent_err_replies = 0 UsrLoc Statistics: usrloc:location-contacts = 3971 usrloc:location-users = 3845 usrloc:location-expires = 286685usrloc:registered_users = 3845 Core Statistics: core:rcv_requests = 752644955 core:rcv_replies = 1181197213 core:fwd_requests = 14482059core:fwd_replies = 206909 Shared Memory Statistics: shmem:fragments = 28437 shmem:real_used_size = 56447456 shmem:free_size = 2091036192shmem:total_size = 2147483648 shmem:max_used_size = 82099768 shmem:used_size = 43354160 cat /proc/net/netstat | cut -d" " -f12-17 ; cat /proc/net/sockstat TW TWRecycled TWKilled PAWSPassive PAWSActive PAWSEstab 273625 0 0 0 0 3524 InBcastOctets OutBcastOctets InCsumErrors InNoECTPkts InECT1Pkts InECT0Pkts 2010 0 1 179031265416 81564 21432766 sockets: used 4964 TCP: inuse 576 orphan 0 tw 3 alloc 681 mem 105 UDP: inuse 3908 mem 3117 UDPLITE: inuse 0 RAW: inuse 0 FRAG: inuse 0 memory 0 ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] kamailio 5.0.6 | segfault bad msg or missing FROM header
Hello, Unfortunately I don't have the SIP signaling, they was no trace when it happens and I don't know the user that create this issue. I will also check the memory just in case, but I think it's more a malformed message. BR Laurent -Message d'origine- De : sr-users De la part de Mojtaba Envoyé : mercredi, 26 septembre 2018 09:18 À : Kamailio (SER) - Users Mailing List Objet : Re: [SR-Users] kamailio 5.0.6 | segfault bad msg or missing FROM header Hi, As i see the dump.txt file, Please paste the SIP signalling to check more. As the log, the From header may be malformed syntax. because when parsing the From header, the issue is occurred. This error is raised when Form header isn't parse properly. Also check the shared and private memory. May be in while parsing the sip message, "out of memory" is occurred to. Whit Regards. Mojtaba Esfandiari.S On Wed, Sep 26, 2018 at 9:58 AM Laurent Schweizer wrote: > > Dear all, > > > > I have setup few weeks ago a kamailio 5.0.6, was working correctly till last > night where 2 time he stop with a segfault error : > > > > > > Sep 25 23:36:19 ch0012 kamailio[18696]: ERROR: > [core/parser/parse_from.c:53]: parse_from_header(): bad msg or missing > FROM header > > Sep 25 23:36:19 ch0012 kernel: kamailio[18696]: segfault at 0 ip > 004d7c4f sp 7fff16135130 error 4 in > kamailio[40+42b000] > > Sep 25 23:36:19 ch0012 kernel: kamailio[18682]: segfault at 0 ip > 004d7c4f sp 7fff16135130 error 4 in > kamailio[40+42b000] > > Sep 25 23:36:19 ch0012 kamailio[18696]: ERROR: siptrace > [siptrace.c:535]: sip_trace_prepare(): cannot parse FROM header > > Sep 25 23:36:19 ch0012 kamailio[18682]: ERROR: > [core/parser/parse_from.c:53]: parse_from_header(): bad msg or missing > FROM header > > Sep 25 23:36:19 ch0012 kamailio[18682]: ERROR: siptrace > [siptrace.c:535]: sip_trace_prepare(): cannot parse FROM header > > Sep 25 23:36:19 ch0012 abrt-hook-ccpp: Process 18696 (kamailio) of > user 0 killed by SIGSEGV - ignoring (repeated crash) > > Sep 25 23:36:19 ch0012 abrt-hook-ccpp: Process 18682 (kamailio) of > user 0 killed by SIGSEGV - dumping core > > Sep 25 23:36:20 ch0012 abrt-hook-ccpp: Saved core dump of pid 18696 to > core.18696 at / (2294079488 bytes) > > Sep 25 23:36:20 ch0012 kamailio[18759]: CRITICAL: > [core/pass_fd.c:277]: receive_fd(): EOF on 31 > > Sep 25 23:36:20 ch0012 kamailio[18679]: ALERT: [main.c:743]: > handle_sigs(): child process 18696 exited by a signal 11 > > Sep 25 23:36:20 ch0012 kamailio[18679]: ALERT: [main.c:746]: > handle_sigs(): core was generated > > Sep 25 23:36:20 ch0012 kamailio[18679]: INFO: [main.c:768]: > handle_sigs(): terminating due to SIGCHLD > > Sep 25 23:36:20 ch0012 kamailio[18759]: INFO: [main.c:823]: > sig_usr(): signal 15 received > > Sep 25 23:36:20 ch0012 kamailio[18754]: INFO: [main.c:823]: > sig_usr(): signal 15 received > > Sep 25 23:36:20 ch0012 kamailio[18758]: INFO: [main.c:823]: > sig_usr(): signal 15 received > > Sep 25 23:36:20 ch0012 kamailio[18757]: INFO: [main.c:823]: > sig_usr(): signal 15 received > > Sep 25 23:36:20 ch0012 kamailio[18753]: INFO: [main.c:823]: > sig_usr(): signal 15 received > > Sep 25 23:36:20 ch0012 kamailio[18752]: INFO: [main.c:823]: > sig_usr(): signal 15 received > > Sep 25 23:36:20 ch0012 kamailio[18756]: INFO: [main.c:823]: > sig_usr(): signal 15 received > > Sep 25 23:36:20 ch0012 kamailio[18751]: INFO: [main.c:823]: > sig_usr(): signal 15 received > > Sep 25 23:36:20 ch0012 kamailio[18746]: INFO: [main.c:823]: > sig_usr(): signal 15 received > > Sep 25 23:36:20 ch0012 kamailio[18747]: INFO: [main.c:823]: > sig_usr(): signal 15 received > > Sep 25 23:36:20 ch0012 kamailio[18750]: INFO: [main.c:823]: > sig_usr(): signal 15 received > > > > I have exported from the core file some info (file is attached), any idea ? > > > > BR > > > > Laurent > > > > ___ > Kamailio (SER) - Users Mailing List > sr-users@lists.kamailio.org > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users -- --Mojtaba Esfandiari.S ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] kamailio 5.0.6 | segfault bad msg or missing FROM header
Dear all,
I have setup few weeks ago a kamailio 5.0.6, was working correctly till last
night where 2 time he stop with a segfault error :
Sep 25 23:36:19 ch0012 kamailio[18696]: ERROR:
[core/parser/parse_from.c:53]: parse_from_header(): bad msg or missing FROM
header
Sep 25 23:36:19 ch0012 kernel: kamailio[18696]: segfault at 0 ip
004d7c4f sp 7fff16135130 error 4 in kamailio[40+42b000]
Sep 25 23:36:19 ch0012 kernel: kamailio[18682]: segfault at 0 ip
004d7c4f sp 7fff16135130 error 4 in kamailio[40+42b000]
Sep 25 23:36:19 ch0012 kamailio[18696]: ERROR: siptrace [siptrace.c:535]:
sip_trace_prepare(): cannot parse FROM header
Sep 25 23:36:19 ch0012 kamailio[18682]: ERROR:
[core/parser/parse_from.c:53]: parse_from_header(): bad msg or missing FROM
header
Sep 25 23:36:19 ch0012 kamailio[18682]: ERROR: siptrace [siptrace.c:535]:
sip_trace_prepare(): cannot parse FROM header
Sep 25 23:36:19 ch0012 abrt-hook-ccpp: Process 18696 (kamailio) of user 0
killed by SIGSEGV - ignoring (repeated crash)
Sep 25 23:36:19 ch0012 abrt-hook-ccpp: Process 18682 (kamailio) of user 0
killed by SIGSEGV - dumping core
Sep 25 23:36:20 ch0012 abrt-hook-ccpp: Saved core dump of pid 18696 to
core.18696 at / (2294079488 bytes)
Sep 25 23:36:20 ch0012 kamailio[18759]: CRITICAL: [core/pass_fd.c:277]:
receive_fd(): EOF on 31
Sep 25 23:36:20 ch0012 kamailio[18679]: ALERT: [main.c:743]:
handle_sigs(): child process 18696 exited by a signal 11
Sep 25 23:36:20 ch0012 kamailio[18679]: ALERT: [main.c:746]:
handle_sigs(): core was generated
Sep 25 23:36:20 ch0012 kamailio[18679]: INFO: [main.c:768]:
handle_sigs(): terminating due to SIGCHLD
Sep 25 23:36:20 ch0012 kamailio[18759]: INFO: [main.c:823]: sig_usr():
signal 15 received
Sep 25 23:36:20 ch0012 kamailio[18754]: INFO: [main.c:823]: sig_usr():
signal 15 received
Sep 25 23:36:20 ch0012 kamailio[18758]: INFO: [main.c:823]: sig_usr():
signal 15 received
Sep 25 23:36:20 ch0012 kamailio[18757]: INFO: [main.c:823]: sig_usr():
signal 15 received
Sep 25 23:36:20 ch0012 kamailio[18753]: INFO: [main.c:823]: sig_usr():
signal 15 received
Sep 25 23:36:20 ch0012 kamailio[18752]: INFO: [main.c:823]: sig_usr():
signal 15 received
Sep 25 23:36:20 ch0012 kamailio[18756]: INFO: [main.c:823]: sig_usr():
signal 15 received
Sep 25 23:36:20 ch0012 kamailio[18751]: INFO: [main.c:823]: sig_usr():
signal 15 received
Sep 25 23:36:20 ch0012 kamailio[18746]: INFO: [main.c:823]: sig_usr():
signal 15 received
Sep 25 23:36:20 ch0012 kamailio[18747]: INFO: [main.c:823]: sig_usr():
signal 15 received
Sep 25 23:36:20 ch0012 kamailio[18750]: INFO: [main.c:823]: sig_usr():
signal 15 received
I have exported from the core file some info (file is attached), any idea ?
BR
Laurent
(gdb) bt full
#0 0x004d7c4f in crcitt_string_array (dst=0x7fb458d06941
"66b7", src=0x7fff161351c0, size=2) at core/crc.c:237
i = 0
ccitt = 65535
c = 0x0
len = 10706350
str_len = 4
__FUNCTION__ = "crcitt_string_array"
#1 0x7fb458af54c1 in calc_crc_suffix (msg=0x7fb45cccf4d8,
tag_suffix=0x7fb458d06941 "66b7") at ../../core/tags.h:55
ss_nr = 2
suffix_source = {{s = 0x0, len = 10706350}, {s = 0x0, len = 0}, {s =
0x417ad0 <_start> "1\355I\211\321^H\211\342H\203\344\360PTI\307\300pTs", len =
370376624}}
#2 0x7fb458af6114 in sl_reply_helper (msg=0x7fb45cccf4d8, code=400,
reason=0x7fb457439828 "Missing Required Header in Request", tag=0x0) at
sl_funcs.c:166
buf = {s = 0x0, len = 0}
dset = {s = 0x0, len = 0}
dst = {send_sock = 0x0, to = {s = {sa_family = 2, sa_data =
"\023\304.\246\263\067\000\000\000\000\000\000\000"}, sin = {sin_family = 2,
sin_port = 50195, sin_addr = {s_addr = 934520366}, sin_zero =
"\000\000\000\000\000\000\000"}, sin6 = {sin6_family = 2, sin6_port = 50195,
sin6_flowinfo = 934520366,
sin6_addr = {__in6_u = {__u6_addr8 = '\000' ,
__u6_addr16 = {0, 0, 0, 0, 0, 0, 0, 0}, __u6_addr32 = {0, 0, 0, 0}}},
sin6_scope_id = 0}}, id = 0, proto = 0 '\000', send_flags = {f = 0, blst_imask
= 0}}
dummy_bm = {to_tag_val = {s = 0x417ad0 <_start>
"1\355I\211\321^H\211\342H\203\344\360PTI\307\300pTs", len = 370376624}}
backup_mhomed = 32692
ret = 1556935896
text = {s = 0x7fb457439828 "Missing Required Header in Request", len =
34}
backup_rt = 0
ctx = {rec_lev = 0, run_flags = 0, last_retcode = 1243967538, jmp_env =
{{__jmpbuf = {140733563755152, 6738787, 7886016, 132727312, 7886016,
1537599782384, 7889841, 7886021}, __mask_was_saved = 56, __saved_mask = {__val
= {140412626337808, 140733563755024, 30064771073, 0, 140412627784928, 7886016,
680160329744, 7889680, 7886021, 56, 14041262400,
21474836480, 10706311, 0, 140411070840832, 140412627067872}
pmsg = {id = 4294967295, pid = 0, tval = {tv_sec = 0, tv_usec = 8180},
fwd_send_flags = {f = 28722, blst_imask =
Re: [SR-Users] ul.add | path & socket not correctly set
Hello,
Thanks it’s working and I will upgrade to 5.1
BR
Laurent
De : Daniel-Constantin Mierla [mailto:mico...@gmail.com]
Envoyé : lundi, 9 juillet 2018 10:54
À : Kamailio (SER) - Users Mailing List ; Laurent
Schweizer
Objet : Re: [SR-Users] ul.add | path & socket not correctly set
Hello,
few things for your version 5.0.x:
- rpc ul.add command doesn't have the last two parameters: received and
socket -- those were added in 5.1 -- so socket is not going to be set no matter
parameter you give
- path parameter was expecting "0" (s:0) in order not to set it -- for
coherence I pushed a patch to skip setting it if '.' is given
However, if you want to set one of the last two parameters, you have to upgrade
to 5.1.
Cheers,
Daniel
On 09.07.18 10:37, Daniel-Constantin Mierla wrote:
Hello,
I will check it -- reminders are good, somehow first message was not noticed...
Cheers,
Daniel
On 08.07.18 13:15, Laurent Schweizer wrote:
Dear all,
Any idea how to solve it ?
BR
Laurent
De : sr-users [mailto:sr-users-boun...@lists.kamailio.org] De la part de
Laurent Schweizer
Envoyé : lundi, 25 juin 2018 22:13
À : Kamailio (SER) - Users Mailing List
<mailto:sr-users@lists.kamailio.org>
Objet : [SR-Users] ul.add | path & socket not correctly set
Dear all,
I have kamailio 5.0.6 and I have an issue to add permanent location
When I add a location with :
kamcmd ul.add location_ch d...@peoplefone.ch<mailto:d...@peoplefone.ch> sip:
demo@95.128.80.122:5060<mailto:demo@95.128.80.122:5060> 0 0.0 . 0 128 6111 .
udp:95.128.80.3:5060
then I get the following insertion:
kamcmd ul.lookup location_ch demo@
{
AoR: demo
Contacts: {
Contact: {
Address: sip:demo@95.128.80.122:5060
Expires: permanent
Q: 0.00
Call-ID:
dfjrewr12386fd6-...@kamailio.mi<mailto:dfjrewr12386fd6-...@kamailio.mi>
CSeq: 1
User-Agent: SIP Router MI Server
Received: [not set]
Path: .
State: CS_SYNC
Flags: 0
CFlags: 128
Socket: [not set]
Methods: 6111
Ruid: ulcx-5b243cb5-67c6-31
Instance: [not set]
Reg-Id: 0
Server-Id: 0
Tcpconn-Id: 0
Keepalive: 0
Last-Keepalive: 0
Last-Modified: 0
}
}
As you can see the Path value is set to “.” But it must be set to [not set]
The Socket is also not set.
Any idea ?
BR
Laurent
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org<mailto:sr-users@lists.kamailio.org>
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla -- www.asipto.com<http://www.asipto.com>
www.twitter.com/miconda<http://www.twitter.com/miconda> --
www.linkedin.com/in/miconda<http://www.linkedin.com/in/miconda>
Kamailio World Conference -- www.kamailioworld.com<http://www.kamailioworld.com>
--
Daniel-Constantin Mierla -- www.asipto.com<http://www.asipto.com>
www.twitter.com/miconda<http://www.twitter.com/miconda> --
www.linkedin.com/in/miconda<http://www.linkedin.com/in/miconda>
Kamailio World Conference -- www.kamailioworld.com<http://www.kamailioworld.com>
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] ul.add | path & socket not correctly set
Dear all,
Any idea how to solve it ?
BR
Laurent
De : sr-users [mailto:sr-users-boun...@lists.kamailio.org] De la part de
Laurent Schweizer
Envoyé : lundi, 25 juin 2018 22:13
À : Kamailio (SER) - Users Mailing List
Objet : [SR-Users] ul.add | path & socket not correctly set
Dear all,
I have kamailio 5.0.6 and I have an issue to add permanent location
When I add a location with :
kamcmd ul.add location_ch d...@peoplefone.ch<mailto:d...@peoplefone.ch> sip:
demo@95.128.80.122:5060<mailto:demo@95.128.80.122:5060> 0 0.0 . 0 128 6111 .
udp:95.128.80.3:5060
then I get the following insertion:
kamcmd ul.lookup location_ch demo@
{
AoR: demo
Contacts: {
Contact: {
Address: sip:demo@95.128.80.122:5060
Expires: permanent
Q: 0.00
Call-ID:
dfjrewr12386fd6-...@kamailio.mi<mailto:dfjrewr12386fd6-...@kamailio.mi>
CSeq: 1
User-Agent: SIP Router MI Server
Received: [not set]
Path: .
State: CS_SYNC
Flags: 0
CFlags: 128
Socket: [not set]
Methods: 6111
Ruid: ulcx-5b243cb5-67c6-31
Instance: [not set]
Reg-Id: 0
Server-Id: 0
Tcpconn-Id: 0
Keepalive: 0
Last-Keepalive: 0
Last-Modified: 0
}
}
As you can see the Path value is set to "." But it must be set to [not set]
The Socket is also not set.
Any idea ?
BR
Laurent
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] ul.add | path & socket not correctly set
Dear all,
I have kamailio 5.0.6 and I have an issue to add permanent location
When I add a location with :
kamcmd ul.add location_ch d...@peoplefone.ch sip: demo@95.128.80.122:5060 0 0.0
. 0 128 6111 . udp:95.128.80.3:5060
then I get the following insertion:
kamcmd ul.lookup location_ch demo@
{
AoR: demo
Contacts: {
Contact: {
Address: sip:demo@95.128.80.122:5060
Expires: permanent
Q: 0.00
Call-ID: dfjrewr12386fd6-...@kamailio.mi
CSeq: 1
User-Agent: SIP Router MI Server
Received: [not set]
Path: .
State: CS_SYNC
Flags: 0
CFlags: 128
Socket: [not set]
Methods: 6111
Ruid: ulcx-5b243cb5-67c6-31
Instance: [not set]
Reg-Id: 0
Server-Id: 0
Tcpconn-Id: 0
Keepalive: 0
Last-Keepalive: 0
Last-Modified: 0
}
}
As you can see the Path value is set to "." But it must be set to [not set]
The Socket is also not set.
Any idea ?
BR
Laurent
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] select outgoing interface
Hi Alex,
Thanks for the fast solution !
BR
Laurent
-Message d'origine-
De : sr-users [mailto:sr-users-boun...@lists.kamailio.org] De la part de Alex
Balashov
Envoyé : lundi, 23 avril 2018 10:34
À : Kamailio (SER) - Users Mailing List <sr-users@lists.kamailio.org>
Objet : Re: [SR-Users] select outgoing interface
Hi Laurent,
You can either rely on Kamailio to do this using the mhomed=1 core config
directive, more particularly described here:
https://www.kamailio.org/wiki/cookbooks/5.1.x/core#mhomed
Or you can turn this off, and manually steer outgoing requests by using the $fs
PV. It is writable, e.g.
listen=udp:x.x.x.x:5060
listen=udp:y.y.y.y:5060
route[RELAY] {
...
$fs = 'udp:x.x.x.x:5060';
if(!t_relay())
sl_reply_error();
exit;
}
If you are moving traffic between interfaces and using Record-Route, be sure to
turn this setting on:
https://kamailio.org/docs/modules/5.1.x/modules/rr.html#rr.p.enable_double_rr
-- Alex
On Mon, Apr 23, 2018 at 08:28:27AM +, Laurent Schweizer wrote:
>
> Dear all,
>
> I have a config with multiple interface( multiple IP in same subnet) and want
> to know how I can select the interface used to send a request (UDP).
> The best is the possibility to choose for each request the outgoing interface
> but if it's not possible I think I can also work with a solution where the
> outgoing interface is defined globally ?
> I need this because one provider request one IP for inbound call and one IP
> for outbound call .
>
>
> Thanks
>
> Laurent
>
>
>
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
--
Alex Balashov | Principal | Evariste Systems LLC
Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] select outgoing interface
Dear all, I have a config with multiple interface( multiple IP in same subnet) and want to know how I can select the interface used to send a request (UDP). The best is the possibility to choose for each request the outgoing interface but if it's not possible I think I can also work with a solution where the outgoing interface is defined globally ? I need this because one provider request one IP for inbound call and one IP for outbound call . Thanks Laurent ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] how to check if pseudo-variable contains a String
Hello, I think I found it BR Laurent De : sr-users [mailto:sr-users-boun...@lists.kamailio.org] De la part de Laurent Schweizer Envoyé : jeudi, 8 mars 2018 11:11 À : sr-users@lists.kamailio.org Objet : [SR-Users] how to check if pseudo-variable contains a String Cet expéditeur n’a pas passé les vérifications relatives à la détection des fraudes et n’est peut-être pas la personne qu’il prétend être. En savoir plus sur l’ usurpation d’identités<http://aka.ms/LearnAboutSpoofing> Votre avis<http://aka.ms/SafetyTipsFeedback> Dear all, I have a question regarding pseudo-variable, how can I check if a pseudo-variable contains a specific string ? Like to check if $ct contains “transport=tcp”. Thanks BR Laurent ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] how to check if pseudo-variable contains a String
Dear all, I have a question regarding pseudo-variable, how can I check if a pseudo-variable contains a specific string ? Like to check if $ct contains "transport=tcp". Thanks BR Laurent ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
