sr-users September 2019

sr-users@lists.kamailio.org

57 participants
82 discussions

Kamailio IMS setup - user online - unable to call
by Jack R 12 Sep '19

12 Sep '19

Hi All, We have installed Kamailio as IMS setup pcscf icscf scscf - 3 instances running on Ubuntu.. Users alice and bob are online however unable to call. When we check the logs the FHoSS is hunting for values in sh_subscription table for alice / bob user. Can you please share: 1. A sample database table values to be inserted across all tables in FHoSS helpful for the call and 2, Maybe, if possible, some description to understand table structures/ importance of fields of FHoSS. Thanks and Regards, Jack.

2 1

Help with "routines:ssl3_read_bytes:sslv3 alert bad certificate" kamailio TLS error
by david＠aslo.us 12 Sep '19

12 Sep '19

Hello everyone, I am trying to configure TLS in kamailio (5.2.4) following this guide: [ http://www.kamailio.org/dokuwiki/doku.php/tls:create-certificates ]( http://www.kamailio.org/dokuwiki/doku.php/tls:create-certificates ) Modules: #!define WITH_MYSQL #!define WITH_AUTH #!define WITH_USRLOCDB #!define WITH_PRESENCE #!define WITH_ALIASDB #!define WITH_IMC #!define WITH_TLS When i try to connect via command line, this is the result (just including relevant parts): $ openssl s_client -connect 192.X.X.X:5061 -tls1 CONNECTED(00000003) depth=1 C = XX, ST = XXXX, L = XXXXXX, O = XXX CA, CN = XXX CA verify error:num=19:self signed certificate in certificate chain verify return:0 --- No client certificate CA names sent --- SSL handshake has read 2550 bytes and written 336 bytes --- --- Start Time: 1567787935 Timeout : 7200 (sec) Verify return code: 19 (self signed certificate in certificate chain) --- read:errno=0 Now, when I setup my clients, they connect to the server, but they can't send messages or make calls. This is the TLS startup LOG: Sep 6 16:41:57 aslo-kamailio /usr/sbin/kamailio[5845]: INFO: tls [tls_mod.c:372]: mod_init(): With ECDH-Support! Sep 6 16:41:57 aslo-kamailio /usr/sbin/kamailio[5845]: INFO: tls [tls_mod.c:375]: mod_init(): With Diffie Hellman Sep 6 16:41:57 aslo-kamailio /usr/sbin/kamailio[5845]: CRITICAL: tls [tls_init.c:671]: 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.0k 28 May 2019" (0x101000bf).#012 Please make sure a compatible version is used (tls_force_run in kamailio.cfg will override this check) Sep 6 16:41:57 aslo-kamailio /usr/sbin/kamailio[5845]: WARNING: tls [tls_init.c:680]: init_tls_h(): tls_force_run turned on, ignoring openssl version mismatch Sep 6 16:41:57 aslo-kamailio /usr/sbin/kamailio[5845]: WARNING: tls [tls_init.c:778]: init_tls_h(): openssl bug #1491 (crash/mem leaks on low memory) workaround enabled (on low memory tls operations will fail preemptively) with free memory thresholds 12582912 and 6291456 bytes Sep 6 16:41:57 aslo-kamailio /usr/sbin/kamailio[5845]: INFO: <core> [core/cfg/cfg_ctx.c:595]: cfg_set_now(): tls.low_mem_threshold1 has been changed to 12582912 Sep 6 16:41:57 aslo-kamailio /usr/sbin/kamailio[5845]: INFO: <core> [core/cfg/cfg_ctx.c:595]: cfg_set_now(): tls.low_mem_threshold2 has been changed to 6291456 Sep 6 16:41:57 aslo-kamailio /usr/sbin/kamailio[5845]: INFO: <core> [main.c:2669]: main(): processes (at least): 24 - shm size: 67108864 - pkg size: 8388608 Sep 6 16:41:57 aslo-kamailio /usr/sbin/kamailio[5845]: INFO: <core> [core/udp_server.c:153]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 Sep 6 16:41:57 aslo-kamailio /usr/sbin/kamailio[5845]: INFO: <core> [core/udp_server.c:205]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 Sep 6 16:41:57 aslo-kamailio /usr/sbin/kamailio[5845]: INFO: tls [tls_domain.c:303]: ksr_tls_fill_missing(): TLSs<default>: tls_method=12 Sep 6 16:41:57 aslo-kamailio /usr/sbin/kamailio[5845]: INFO: tls [tls_domain.c:315]: ksr_tls_fill_missing(): TLSs<default>: certificate='/etc/certs/192.X.X.X/cert.pem' Sep 6 16:41:57 aslo-kamailio /usr/sbin/kamailio[5845]: INFO: tls [tls_domain.c:322]: ksr_tls_fill_missing(): TLSs<default>: ca_list='/etc/certs/demoCA/cert.pem' Sep 6 16:41:57 aslo-kamailio /usr/sbin/kamailio[5845]: INFO: tls [tls_domain.c:329]: ksr_tls_fill_missing(): TLSs<default>: crl='(null)' Sep 6 16:41:57 aslo-kamailio /usr/sbin/kamailio[5845]: INFO: tls [tls_domain.c:333]: ksr_tls_fill_missing(): TLSs<default>: require_certificate=0 Sep 6 16:41:57 aslo-kamailio /usr/sbin/kamailio[5845]: INFO: tls [tls_domain.c:340]: ksr_tls_fill_missing(): TLSs<default>: cipher_list='(null)' Sep 6 16:41:57 aslo-kamailio /usr/sbin/kamailio[5845]: INFO: tls [tls_domain.c:347]: ksr_tls_fill_missing(): TLSs<default>: private_key='/etc/certs/192.X.X.X/key.pem' Sep 6 16:41:57 aslo-kamailio /usr/sbin/kamailio[5845]: INFO: tls [tls_domain.c:351]: ksr_tls_fill_missing(): TLSs<default>: verify_certificate=0 Sep 6 16:41:57 aslo-kamailio /usr/sbin/kamailio[5845]: INFO: tls [tls_domain.c:354]: ksr_tls_fill_missing(): TLSs<default>: verify_depth=9 Sep 6 16:41:57 aslo-kamailio /usr/sbin/kamailio[5845]: NOTICE: tls [tls_domain.c:1087]: ksr_tls_fix_domain(): registered server_name callback handler for socket [:0], server_name='<default>' ... Sep 6 16:41:57 aslo-kamailio /usr/sbin/kamailio[5845]: INFO: tls [tls_domain.c:707]: set_verification(): TLSs<default>: No client certificate required and no checks performed Sep 6 16:41:57 aslo-kamailio /usr/sbin/kamailio[5845]: INFO: tls [tls_domain.c:303]: ksr_tls_fill_missing(): TLSc<default>: tls_method=12 Sep 6 16:41:57 aslo-kamailio /usr/sbin/kamailio[5845]: INFO: tls [tls_domain.c:315]: ksr_tls_fill_missing(): TLSc<default>: certificate='(null)' Sep 6 16:41:57 aslo-kamailio /usr/sbin/kamailio[5845]: INFO: tls [tls_domain.c:322]: ksr_tls_fill_missing(): TLSc<default>: ca_list='(null)' Sep 6 16:41:57 aslo-kamailio /usr/sbin/kamailio[5845]: INFO: tls [tls_domain.c:329]: ksr_tls_fill_missing(): TLSc<default>: crl='(null)' Sep 6 16:41:57 aslo-kamailio /usr/sbin/kamailio[5845]: INFO: tls [tls_domain.c:333]: ksr_tls_fill_missing(): TLSc<default>: require_certificate=0 Sep 6 16:41:57 aslo-kamailio /usr/sbin/kamailio[5845]: INFO: tls [tls_domain.c:340]: ksr_tls_fill_missing(): TLSc<default>: cipher_list='(null)' Sep 6 16:41:57 aslo-kamailio /usr/sbin/kamailio[5845]: INFO: tls [tls_domain.c:347]: ksr_tls_fill_missing(): TLSc<default>: private_key='(null)' Sep 6 16:41:57 aslo-kamailio /usr/sbin/kamailio[5845]: INFO: tls [tls_domain.c:351]: ksr_tls_fill_missing(): TLSc<default>: verify_certificate=0 Sep 6 16:41:57 aslo-kamailio /usr/sbin/kamailio[5845]: INFO: tls [tls_domain.c:354]: ksr_tls_fill_missing(): TLSc<default>: verify_depth=9 Sep 6 16:41:57 aslo-kamailio /usr/sbin/kamailio[5845]: INFO: tls [tls_domain.c:710]: set_verification(): TLSc<default>: Server MAY present invalid certificate Sep 6 16:41:58 aslo-kamailio /usr/sbin/kamailio[5862]: INFO: jsonrpcs [jsonrpcs_sock.c:443]: jsonrpc_dgram_process(): a new child 0/5862 Sep 6 16:41:58 aslo-kamailio /usr/sbin/kamailio[5866]: INFO: ctl [io_listener.c:214]: io_listen_loop(): io_listen_loop: using epoll_lt io watch method (config) This is my tls.cfg file: [server:default] method = TLSv1 verify_certificate = no require_certificate = no private_key = /etc/certs/192.X.X.X/key.pem certificate = /etc/certs/192.X.X.X/cert.pem ca_list = /etc/certs/demoCA/cert.pem #crl = /etc/kamailio/tls/crl.pem # --- # This is the default client domain profile. # Settings in this domain will be used for all outgoing # TLS connections that do not match any other # client domain in this configuration file. # We require that servers present valid certificate. # [client:default] method = TLSv1 verify_certificate = no require_certificate = no These are the relevant parts of my kamailio.cfg: # alias="sip.mydomain.com" alias=192.X.X.X:5060 alias=192.X.X.X:5061 /* uncomment and configure the following line if you want Kamailio to * bind on a specific interface/port/proto (default bind on all available) */ listen=udp:192.X.X.X:5060 listen=tcp:192.X.X.X:5060 listen=tls:192.X.X.X:5061 #!ifdef WITH_TLS enable_tls=yes /* upper limit for TLS connections */ tls_max_connections=2048 #!endif #!ifdef WITH_TLS # ----- tls params ----- modparam("tls", "config", "/etc/kamailio/tls.cfg") modparam("tls", "tls_force_run", 1) #!endif These are the errors that show up everytime i try to connect with a client: Sep 6 16:53:42 aslo-kamailio /usr/sbin/kamailio[5870]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:14094412:SSL routines:ssl3_read_bytes:sslv3 alert bad certificate Sep 6 16:53:42 aslo-kamailio /usr/sbin/kamailio[5870]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f7c4e3ddd00 r: 0x7f7c4e3ddd80 (-1) Sep 6 16:53:43 aslo-kamailio /usr/sbin/kamailio[5874]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:14094412:SSL routines:ssl3_read_bytes:sslv3 alert bad certificate Sep 6 16:53:43 aslo-kamailio /usr/sbin/kamailio[5874]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f7c4e3ddd00 r: 0x7f7c4e3ddd80 (-1) Sep 6 16:53:44 aslo-kamailio /usr/sbin/kamailio[5875]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:14094412:SSL routines:ssl3_read_bytes:sslv3 alert bad certificate Sep 6 16:53:44 aslo-kamailio /usr/sbin/kamailio[5875]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f7c4e3ddd00 r: 0x7f7c4e3ddd80 (-1) Any help would be greatly appreciated. Regards.

2 1

Kamailio status get Active (Exited)
by Gaurav Bmotra 11 Sep '19

11 Sep '19

hi i m using kamailio 5.1, with -m 512 -M 8 it stop registering user SIP anf in status it shows ------------------------------ ● kamailio.service - LSB: Start the Kamailio SIP proxy server Loaded: loaded (/etc/init.d/kamailio; generated) Active: active (exited) since Sat 2019-09-07 11:05:16 UTC; 3 days ago Docs: man:systemd-sysv-generator(8) Sep 11 06:38:36 talk /usr/local/sbin/kamailio[17708]: INFO: <core> [main.c:819]: sig_usr(): signal 15 received Sep 11 06:38:36 talk /usr/local/sbin/kamailio[17677]: INFO: <core> [main.c:819]: sig_usr(): signal 15 received Sep 11 06:38:36 talk /usr/local/sbin/kamailio[17714]: INFO: <core> [main.c:819]: sig_usr(): signal 15 received Sep 11 06:38:36 talk /usr/local/sbin/kamailio[17685]: INFO: <core> [main.c:819]: sig_usr(): signal 15 received Sep 11 06:38:36 talk /usr/local/sbin/kamailio[17681]: {1 1094155754 NOTIFY TwGwmzx4wINnraJs1Gh3Kg..} INFO: <core> [main.c:819]: sig_usr(): s… received Sep 11 06:38:36 talk /usr/local/sbin/kamailio[17704]: INFO: <core> [main.c:819]: sig_usr(): signal 15 received Sep 11 06:38:36 talk /usr/local/sbin/kamailio[17689]: INFO: <core> [main.c:819]: sig_usr(): signal 15 received Sep 11 06:38:36 talk /usr/local/sbin/kamailio[17693]: INFO: <core> [main.c:819]: sig_usr(): signal 15 received Sep 11 06:38:36 talk /usr/local/sbin/kamailio[17691]: INFO: <core> [main.c:819]: sig_usr(): signal 15 received Sep 11 06:38:36 talk /usr/local/sbin/kamailio[17674]: INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized Hint: Some lines were ellipsized, use -l to show in full. --------------------------------------------------------------------- plz help thank you -- *Regards:* Gaurav Kumar

2 1

Can't connect to db
by Andrew Chen 10 Sep '19

10 Sep '19

Hi all, I just installed kamailio 5.2.4 on two separate aws instances in two separate regions. Both regions uses the same configuration template and share the same db in AWS RDS. The issue I see is this: - SJO location was able to launch fine without any issues. - ASH location could not start up kamailio process due to db connection failure: Sep 10 21:24:13 ashmainkama51 /usr/sbin/kamailio[8043]: ERROR: db_mysql [km_my_con.c:139]: db_mysql_new_connection(): driver error: Too many connections Sep 10 21:24:13 ashmainkama51 /usr/sbin/kamailio[8043]: ERROR: <core> [db.c:319]: db_do_init2(): could not add connection to the pool Sep 10 21:24:13 ashmainkama51 /usr/sbin/kamailio[8045]: ERROR: db_mysql [km_my_con.c:139]: db_mysql_new_connection(): driver error: Too many connections Sep 10 21:24:13 ashmainkama51 /usr/sbin/kamailio[8045]: ERROR: <core> [db.c:319]: db_do_init2(): could not add connection to the pool Sep 10 21:24:13 ashmainkama51 /usr/sbin/kamailio[8045]: ERROR: carrierroute [db_carrierroute.c:141]: carrierroute_db_open(): can't connect to database. Sep 10 21:24:13 ashmainkama51 /usr/sbin/kamailio[8045]: ERROR: <core> [core/sr_module.c:847]: init_mod_child(): error while initializing module carrierroute (/usr/lib/x86_64-linux-gnu/kamailio/modules/carrierroute.so) (idx: 30 rank: 18 desc: [tcp receiver (generic) child=9]) - In ASH instance, I can manually mysql to the RDS host using the credentials in the config file. - I checked db user permissions and it's opened for the subnet in our ASH location (which is also proven using manual connection). So I don't get why one works and the other doesn't Thoughts? -- Andy Chen Sr. Telephony Lead Engineer -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.*

2 2

LCR lcr_id short or int?
by Grant Bagdasarian 10 Sep '19

10 Sep '19

Hello, The database tables definition for 5.2.x mentions the lcr_id parameter being of unsigned short type, while in the code I only see definitions of type int. Is it safe to assume the parameter is of type int, so the database column can also be set to an integer type? Regards, Grant

2 7

Share variable into reply route.
by Zhan Bazarov 09 Sep '19

09 Sep '19

Hello, we ran into a trouble with sharing variable into reply route... We are going to match asterisk's uniqueid with rtpengine records like this: route[from_asterisk]{ $var(UniqueId)=$hdr(X-UniqueId); $var(rtp_flags) = $var(rtp_flags) + " label={uid:$var(UniqueId),stream:outgoing} record-call=on"; rtpengine_manage($var(rtp_flags)); } reply_route[from_pstn]{ rtpengine_manage("replace-origin replace-session-connection ICE=remove RTP/AVP rtcp-mux-demux label={uid:$var(UniqueId),stream:outgoing"); } and it doesn't work... The one possible way what we found its using $shv instead of $var... But its unsecure way, cuz it may confus our bussines logic... Do you have any idea how to implement this? Many thanks!

3 2

How to install kamailio symbols for debugging
by YASIN CANER 09 Sep '19

09 Sep '19

Hello, I want to debug kamailio with gdb or try to get core.dump file but i failed. GDB wants to kamailio symbols. How to install them? on Ubuntu - raspberry PI Best regards. Yasin CANER

4 3

Error Users - 604 Does not exist anywhere - HSS User Unknown
by Jack R 08 Sep '19

08 Sep '19

Hi, We have installed Kamailio as IMS setup pcscf icscf scscf - 3 instances running on Ubuntu.. 1. 2 Sip client registers successfully (shows Online) as 'bob(a)net1.test' and 'alice(a)net1.test' 2. When we check server logs: Invite request shows 'bob@IP address' i.e. ' bob(a)10.0.0.10' 3. However, in HSS it is registered as 'bob(a)net1.test'. 4. When the request from SCSCF goes to ISCSF it gives Error: Users - 604 Does not exist anywhere - HSS User Unknown. As it compares 'bob(a)10.0.0.10' with 'bob(a)net1.test'. Please help and advise how everywhere (SCSCF, PCSCF) during query/comparisons it can take 'bob(a)net1.test' and not 'bob(a)10.0.0.10' Thanks and Regards, Jack.

1 1

Kamailio - PfSense Firewall - inbound/outbound rules
by Youssef Boujraf 06 Sep '19

06 Sep '19

Dear All, I am evaluating the kamailio proxy 5.2 server with rtpproxy on an internal network. Everything are ok. Now, I would like to evalute Kamailio proxy from outside (internet) but I have some difficulties to setup my PfSense firewall to enable inbound & outbound rules, network settings and kamailio.cfg. The issues are : Setup correctly Network files : * /etc/hostname 127.0.0.1 localhost ip_private codecsip.mydomain codecsip ip_public codecsip.mydomain codecsip * /etc/hosts file codesip * dns * /etc/resolv.conf nameserver 8.8.8.8Setup /etc/kamailio/kamailio.cfg :#!define WITH_MYSQL #!define WITH_AUTH #!define WITH_USRLOCDB #!define WITH_NAT #!define WITH_TLS /* uncomment the next line to disable the auto discovery of local aliases based on reverse DNS on IPs (default on) */ #auto_aliases=no /* add local domain aliases */ alias="codecsip.mydomain" #!ifdef WITH_NAT # ----- rtpproxy params ----- # modparam("rtpproxy", "rtpproxy_sock", "udp:127.0.0.1:7722") modparam("rtpproxy", "rtpproxy_sock", "unix:/var/run/rtpproxy/rtpproxy.sock") Setup etc/default/rtpproxy : CONTROL_SOCK=udp:127.0.0.1:7722 EXTRA_OPTS="-l <IP-address>" Where <IP-address> is the external IP address of your host. Regarding the firewall rules, it will be great to identify which rules I need to create : Inbound and outbound rules and NAT 1:1 ? If anyone have any information it could be great Best regards, Youssef

2 1

Kamailio HA
by Christian Attanasio 06 Sep '19

06 Sep '19

Hi everyone I use kamailio 5.1 with rtpengine and I would like to set up a simple warm standby or hot standby system for my sip server. on the web I found various discussions and posts that led me to deepen them the dispatcher, dmq, dmq_usrloc, db_cluster and p_usrloc modules. now, though, I'm a little confused: what approach do you recommend for this system? I thought of using two identical servers: Kam01 10.10.10.2 Kam02 10.10.10.3 Hostname cluster.mydomain.com each with its own mariadb and implementing data replication (with the dmq module? Or db_cluster and sqlops?). in this scenario is it necessary to also use the dispatcher module or implement a high available system with keepalives and floating ip? thanks, Christian

1 0

← Newer
1
2
3
4
5
6
7
8
9
Older →

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users September 2019