- sr-users - kamailio.org

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

Kamalio & Asterisk integration erroneous behavior, setup issue
by Aristeidis Tsitras 05 Sep '19

05 Sep '19

new to the area and trying to setup Kamailio with Asterisk in a single machine. All users will register to Kamailio's port and in case of need for media, it will be forwarded to Asterisk, that is my intention. All of my work is based on the following link https://kb.asipto.com/asterisk:realtime:kamailio-4.0.x-asterisk-11.3.0-astdb. Here is what i have done: - Debian 8, 64 bit machine with mysql and odbc - *root@kamast: ~ $ lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 8.11 (jessie) Release: 8.11 Codename: jessie root@kamast: ~ $ uname -a Linux kamast 3.16.0-10-amd64 #1 SMP Debian 3.16.72-1 (2019-08-13) x86_64 GNU/Linux root@kamast: ~ $ * - Kamailio 5.2 installed from Kamailio's deb repository - Asterisk 13LTS installed from source - Used the same passwords such as kamailiorw and asterisk_password, since this is a test system, for proof of concept. I did import to the mysql>asterisk database 3 users 2200, 2201 and 2202. Then created in sip.conf the same 3 users with the same credentials. Then on 3 PCs i used softphones (Jitsi, Zoiper) and registered each account to a softphone. Problems: - Cannot see the users in the Asterisk's cli, sip show peers - I can see users only in Kamailio with kamctl ul show - A call between the extensions goes to voicemail. It never reaches the other destination eg 2200 calls 2201 and in Asterisk's console i am getting a message that 2201 is absent and it goes to voicemail. The same with any other extension. Attached you can find: 1. Kamailio.cfg 2. Asterisk's sip.conf 3. Asterisk's extension.conf 4. The import that i have done to mysql for the user creation. I would appreciate if someone could point me to the error and help me fix it please?

3 7

$Au being set to $fu instead of $fU
by Joel Serrano 05 Sep '19

05 Sep '19

Hi, Testing on latest master deb nightly build from last night I've noticed that when $au is not available, $Au is being set to $fu (uri) instead of $fU (username). Docs: https://www.kamailio.org/wiki/cookbooks/devel/pseudovariables ... $Au - Acc username: username for accounting purposes. It's a selective pseudo variable (inherited from acc module). It returns auth username ($au) if exists or From username ($fU) otherwise. ... I have the following log in several places in a test box: xlog("L_NOTICE", "[DEBUG] Au=$Au au=$au aU=$aU fU=$fU fu=$fu - \n"); And when I run through them (on both request and reply routes) I get the following: Aug 8 14:37:43 csbc01 csbc[9478]: NOTICE: {1 21564 REGISTER d8df9be1-1702e20b(a)A.B.C.D} <script>: [DEBUG] Au=1002366(a)some.domain au=<null> aU=<null> fU=1002366 fu=sip:1002366@some.domain - Aug 8 14:37:43 csbc01 csbc[9479]: NOTICE: {1 21565 REGISTER d8df9be1-1702e20b(a)A.B.C.D} <script>: [DEBUG] Au=1002366(a)some.domain au=1002366 aU=1002366 fU=1002366 fu=sip:1002366@some.domain - Aug 8 14:37:43 csbc01 csbc[9484]: NOTICE: {2 21565 REGISTER d8df9be1-1702e20b(a)A.B.C.D} <script>: [DEBUG] Au=1002366(a)some.domain au=<null> aU=<null> fU=1002366 fu=sip:1002366@some.domain - Those 3 logs belong to the same flow from different places in the config script. I would expect $Au to never have a "@some.domain" in it, so I assume in some place the replacement is not being done with $fU but with $fu. @Devs: I'm happy to create a GH issue for tracking etc if required, please let me know! Cheers, Joel.

2 3

How to detect miss call and accomplished call
by Anuran Barman 05 Sep '19

05 Sep '19

Hi, I want to show call logs in my SIP app. How can I do this with Kamailio? I want to do it from the *kamailio.cfg *file. Is it possible to do it from where? I guess Dialog module should be used for this, but can not figure out how to do it. I want minimalist feature like who call whom with timestamp, thats all. How can I do this?

3 9

Kamailio-IMS system
by Hạnh Nguyễn 05 Sep '19

05 Sep '19

Dear Mrs/Mss, I am Hanh, I am from Viet Nam. I am writting this email because I have an issue when I download The log-file and the config-files on website https://www.kamailio.org/w/2016/02/kamailio-ims-getting-started-box/. When I click on https://www.dropbox.com/s/ehkzi9pbhlp7njc/Kamailio-IMS%20config-files.zip?d… to download The log-file which I really need on this time, the page displays 404 Error - Link not found. So I can not download. I hope I will receive a new link from you soon. I look forward to hearing from you. Sincerely, Hanh Nguyen

2 1

Planning the next major release - v5.3.0
by Daniel-Constantin Mierla 04 Sep '19

04 Sep '19

Hello, it's about the time to set the milestones to the next major release - v5.3.0. There are 6 new modules and many other enhancements to existing components in git master branch, also during the last irc devel meeting it was proposed to freeze after summer holidays. At this moment I would propose Wednesday, September 4, 2019 to freeze the development. Then the release should be about one month later, after testing interval. In case there are people willing a bit more time for development, we can freeze one week later, September 11, or another date -- your suggestions here. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

3 5

Using Kamailio IMS for making a call
by supreeth herle 04 Sep '19

04 Sep '19

Hello Everyone, I have successfully setup a VM in OpenStack with Kamailio IMS, rtpengine and FoHSS using the instructions mentioned in the guide which i wrote (attached to this mail), all running in the machine. I am using the existing alice and bob IMPUs created in FoHSS. But, when I try to call each other the call doesnt go through and I observe in the wireshark traces that S-CSCF is replying to I-CSCF that "403, Forbidden - Domain not served". Can somebody please tell me do I need any additional components to make a call or am i missing some configuration? It would be great if someone can help me troubleshooting this issue. I have attached the pcap file for your reference. Many thanks in advance. Regards, Supreeth

1 0

Kamailio stops processing requests over UDP
by Juha Heinanen 04 Sep '19

04 Sep '19

I'm returning to an old issue, where Kamailio stops processing incoming requests. Now it turned out that only requests over UDP are not processed. Requests over TCP work fine. Debug log doesn't show anything about the requests over UDP, but wireshark sees them coming. core.ps shows that main process - attendant and all udp receiver processes are alive. Any ideas what could cause Kamailio (5.2 version) to stop processing requests over UDP? What additional info should I try to get? -- Juha

4 21

Hello Group - I have a "challenge"
by Kevin Greene 04 Sep '19

04 Sep '19

I recently did the upgrade from v4.4 to 5.2 (via Yum). When starting Kamailio, I get these three errors. Not sure if they are related or not but I do not think so. Have spent a lot of time searching on Google for the answer and have not found the solution. [root@ids kamailio]# kamctl restart INFO: Stopping Kamailio : INFO: stopped INFO: Starting Kamailio : INFO: started (pid: 44608) [root@ids kamailio]# tail -f /var/log/sipserver.log Sep 4 00:39:06 ids /usr/sbin/kamailio[44608]: ERROR: <core> [core/pvapi.c:1119]: pv_parse_spec2(): wrong char [t/116] in [$mt] at [2 (0)] Sep 4 00:39:06 ids /usr/sbin/kamailio[44608]: ERROR: <core> [core/dprint.c:451]: log_prefix_init(): wrong format[{$mt $hdr(CSeq) $ci} ] Sep 4 00:39:06 ids /usr/sbin/kamailio[44626]: ERROR: <core> [core/receive.c:319]: receive_msg(): no request_route {...} and no other config routing engine registered The last error is repeated many times (each time a remote user tries to connect I think). I can send any additional files if needed. Thanks. I am burning out on this upgrade. Kevin

2 1

Unexpected BYEs from dialog module
by Alex Balashov 03 Sep '19

03 Sep '19

Hi, I am running 4.3.5:1b0c0a, which I am aware is an EOL'd release train, and have a problem with the dialog module I am baffled by. On many calls - I can't find any correlation to particular kinds of endpoints - I see spoofed BYEs come out of Kamailio after a minute and a half, as if the call had hit a dialog timeout or the dialog module's dead peer detection (OPTIONS pinging) kicked it out. The thing is, neither of those explanations seem to be borne out by the parameters of the calls under investigation. The dialog timeout on these calls is set to 7200, and the dialog keepalives aren't enabled in either direction. If they were, it'd be logged. Calls that are terminated in this manner also see the following log message: WARNING: dialog [dlg_req_within.c:214]: bye_reply_cb(): inconsitent dlg timer data on dlg 0x7f9997317e48 [3390:9644] with clid '1996679936_133218050(a)x.x.x.x' and tags '2bb17663-co4006-INS001' 'as7925780d' But I don't think this is unusual for a dialog-spoofed BYE; presumably this is due to a 200 OK for the BYE from both ends. So anyway, I am trying to track down anything else that could inadvertently cause dialog to hang up calls relatively quickly in that release, or inadvertently set the dialog timeout parameter to something lower than is apparent from the logging and the config. If anyone has any pointers, that would not go unappreciated! Many thanks, -- Alex -- 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/

2 6

crash/mem leaks on low memory
by Gaurav Bmotra 03 Sep '19

03 Sep '19

hi i m using kamailio 5.1 on Ubuntu 18.04 i m geting this error in logs and it stop registration form soft-phone plz help me -------------------------------------------------------------------------------------------------------- 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 th -------------------------------------------------------------------------------------------------------- kamailio.service - LSB: Start the Kamailio SIP proxy server Loaded: loaded (/etc/init.d/kamailio; generated) Active: active (exited) since Tue 2019-09-03 12:09:19 UTC; 26min ago Docs: man:systemd-sysv-generator(8) Process: 27237 ExecStart=/etc/init.d/kamailio start (code=exited, status=0/SUCCESS) Sep 03 12:09:18 talk /usr/local/sbin/kamailio[27270]: INFO: <core> [core/cfg/cfg_ctx.c:595]: cfg_set_now(): tls.low_mem_threshold2 has been changed to 7077888 Sep 03 12:09:18 talk /usr/local/sbin/kamailio[27270]: INFO: <core> [main.c:2636]: main(): processes (at least): 27 - shm size: 536870912 - pkg size: 8388608 Sep 03 12:09:18 talk /usr/local/sbin/kamailio[27270]: ERROR: dispatcher [dispatcher.c:813]: ds_warn_fixup(): failover functions used, but required AVP parameters are NULL -- feature disabled Sep 03 12:09:18 talk /usr/local/sbin/kamailio[27270]: INFO: <core> [core/udp_server.c:153]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 Sep 03 12:09:18 talk /usr/local/sbin/kamailio[27270]: INFO: <core> [core/udp_server.c:205]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 Sep 03 12:09:18 talk /usr/local/sbin/kamailio[27270]: ERROR: <core> [core/tcp_main.c:2850]: tcp_init(): bind(c, 0x7f0b41b001f4, 16) on 172.31.35.49:5091 : Address already in use Sep 03 12:09:18 talk /usr/local/sbin/kamailio[27270]: INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized -- thank you *Regards:* Gaurav Kumar

3 3

evapi mismatch version
by bill＠novatrope.us 02 Sep '19

02 Sep '19

Hi All Installed Kam 5.2.4, but now getting version mismatch on evapi. ERROR: <core> [core/sr_module.c:348]: version_control(): module version mismatch for /usr/lib64/kamailio/modules/evapi.so; core: kamailio 5.2.4 (x86_64/linux); module: kamailio 5.1.6 (x86_64/linux) Anybody know how to get the correct evapi version. I am running centos 7 Bill

3 2

Issue with uac_replace
by David Costa 01 Sep '19

01 Sep '19

Greetings, I have a Kamailio proxy with uac_replace for To and From Headers. So far everything has worked correctly. However, I now have a client who encodes my Calling Number too and I'm getting some issues in the restore mechanics. I have the restore setup as "auto" and it's info is stored in "vsf" and "vst" parameters of Record-Route. On replies sent by my client I have the following Record-Route and From Header (Note : My Kamailio has two IPs which makes it insert two RR headers ): Record-Route: <sip:xxx.xxx.xxx.xxx;r2=on;lr;ftag=99A730303736313103579CC4;tbk_i=1_2_Y;tbk_ o=128_11_Y;vsf=AAAAABgGBAMDAAUBBQAJDndyAwMcHwIdHQsWHwUDNw--;vst=AAAAABgGBAMH DQgJDQECA3RyAwMcHwIdGgQeHAIFAnVzZXI9cGhvbmU-;did=f74.78e2> Record-Route: <sip:xxx.xxx.xxx.xxx;r2=on;lr;ftag=99A730303736313103579CC4;tbk_i=1_2_Y;tbk_ o=128_11_Y;vsf=AAAAABgGBAMDAAUBBQAJDndyAwMcHwIdHQsWHwUDNw--;vst=AAAAABgGBAMH DQgJDQECA3RyAwMcHwIdGgQeHAIFAnVzZXI9cGhvbmU-;did=f74.78e2> From: "+351411110097" <sip:I2116446I_500@xxx.xxx.xxx.xxx>;tag=99A730303736313103579CC4 In this case the restore is done correctly When the client sends me a BYE request I have the following Route Header and To Header Route : <sip:xxx.xxx.xxx.xxx;r2=on;lr;ftag=99A730303736313103579CC4;tbk_i=1_2_Y;tbk_ o=128_11_Y;vsf=AAAAABgGBAMDAAUBBQAJDndyAwMcHwIdHQsWHwUDNw--;vst=AAAAABgGBAMH DQgJDQECA3RyAwMcHwIdGgQeHAIFAnVzZXI9cGhvbmU-;did=f74.78e2>,<sip:xxx.xxx.xxx. xxx;r2=on;lr;ftag=99A730303736313103579CC4;tbk_i=1_2_Y;tbk_o=128_11_Y;vsf=AA AAABgGBAMDAAUBBQAJDndyAwMcHwIdHQsWHwUDNw--;vst=AAAAABgGBAMHDQgJDQECA3RyAwMcH wIdGgQeHAIFAnVzZXI9cGhvbmU-;did=f74.78e2> To : "+351411110097" <sip:I2116446I_500@xxx.xxx.xxx.xxx>;tag=99A730303736313103579CC4 In this scenario, the To after restore is : To :"+351411110097" <sip:Q4525417L_<>Gxxx.xxx.xxx.xxx>;tag=99A730303736313103579CC4, which throws an internal error on Kamailio about bad URI and also makes our MediaGateway reply with a "Bad Request". Can this error be caused by the restore of the uac_replace mechanics? Both Record Route URIs are on different headers while the both Route URIs are on the same Route header. Can this be the reason? If you need more information please let me know. Best Regards David Costa

2 1

Re: [SR-Users] controlling presence with new module `pua_json`
by Henning Westerholt 30 Aug '19

30 Aug '19

Hello Bill, (please keep the list in CC) yes, this seems to be the case. Just looked briefly to the code, it does an assignment in some cases. E.g. if no Presentity* data is given it will just use the From* information. And then it should later output an error from pua_json_update_presentity(..) if there is not the necessary data. Do you see any error message like this? Another idea - does it works if you add more "missing" data in the curl requests? Cheers, Henning Am 28.08.19 um 21:16 schrieb bill(a)novatrope.us: > Henning: Good point. > > I do see a number of errors in the log. It looks like the json routine > is looking for data that is not in the http query as specified by the > author. > > > 17(125579) DEBUG: json [json_mod.c:70]: _json_extract_field(): > Event-Name: [update] > 17(125579) DEBUG: json [json_mod.c:70]: _json_extract_field(): > Event-Package: [dialog] > 17(125579) DEBUG: json [json_mod.c:70]: _json_extract_field(): Json-c > error - failed to extract field [Presentity] > 17(125579) DEBUG: json [json_mod.c:70]: _json_extract_field(): > Presentity: [] > 17(125579) DEBUG: json [json_mod.c:70]: _json_extract_field(): Json-c > error - failed to extract field [Presentity-User] > 17(125579) DEBUG: json [json_mod.c:70]: _json_extract_field(): > Presentity-User: [] > 17(125579) DEBUG: json [json_mod.c:70]: _json_extract_field(): Json-c > error - failed to extract field [Presentity-Realm] > 17(125579) DEBUG: json [json_mod.c:70]: _json_extract_field(): > Presentity-Realm: [] > 17(125579) DEBUG: json [json_mod.c:70]: _json_extract_field(): From: > [sip:1020101@<IP of phone>] > 17(125579) DEBUG: json [json_mod.c:70]: _json_extract_field(): > From-User: [1020101] > 17(125579) DEBUG: json [json_mod.c:70]: _json_extract_field(): > From-Realm: [<IP of phone>] > 17(125579) DEBUG: json [json_mod.c:70]: _json_extract_field(): Json-c > error - failed to extract field [From-URI] > 17(125579) DEBUG: json [json_mod.c:70]: _json_extract_field(): > From-URI: [] > 17(125579) DEBUG: json [json_mod.c:70]: _json_extract_field(): To: > [sip:1020108@<IP of server>:50060] > 17(125579) DEBUG: json [json_mod.c:70]: _json_extract_field(): > To-User: [1020108] > 17(125579) DEBUG: json [json_mod.c:70]: _json_extract_field(): Json-c > error - failed to extract field [To-URI] > 17(125579) DEBUG: json [json_mod.c:70]: _json_extract_field(): To-URI: [] > 17(125579) DEBUG: json [json_mod.c:70]: _json_extract_field(): > Call-ID: [1020101@<IP of phone>] > 17(125579) DEBUG: json [json_mod.c:70]: _json_extract_field(): Json-c > error - failed to extract field [From-Tag] > 17(125579) DEBUG: json [json_mod.c:70]: _json_extract_field(): > From-Tag: [] > 17(125579) DEBUG: json [json_mod.c:70]: _json_extract_field(): Json-c > error - failed to extract field [To-Tag] > 17(125579) DEBUG: json [json_mod.c:70]: _json_extract_field(): To-Tag: [] > 17(125579) DEBUG: json [json_mod.c:70]: _json_extract_field(): Json-c > error - failed to extract field [Direction] > 17(125579) DEBUG: json [json_mod.c:70]: _json_extract_field(): > Direction: [] > 17(125579) DEBUG: json [json_mod.c:70]: _json_extract_field(): State: > [Confirmed] > 17(125579) DEBUG: presence [event_list.c:348]: search_event(): start > event= [dialog/5] > > On 8/28/19 12:00 PM, Henning Westerholt wrote: >> Hello Bill, >> >> just giving some generic debug pointers here: >> >> - do you see any errors in the kamailio log file? >> >> - do you see any SIP traffic (e.g. by observing with ngrep, wireshark >> etc..) to the phone after your curl command? >> >> Cheers, >> >> Henning >> >> Am 28.08.19 um 19:04 schrieb bill(a)novatrope.us: >>> Hi all: >>> >>> I am trying to use the procedure for setting BLF lights described in >>> https://blog.voipxswitch.com/2018/02/22/kamailio-controlling-presence-with-… >>> >>> >>> WIthout success. >>> >>> My configuration is 1 Grandstream GXP2130 phone behind a NAT on a >>> public IP. (IPP in example below) >>> >>> Kamailio is running on public IP (IPK in example) listening on port >>> 50060 >>> >>> The command I am sending: >>> >>> curl -d >>> '{"Call-ID":"1020101@<IPP>","Event-Category":"presence","Event-Name":"update","Event-Package":"dialog","Expires":"3600","To":"sip:1020108@<IPK>:50060","To-User":"1020108","To-Realm":"<IPK>:50060","From":"sip:1020101@<IPP>","From-User":"1020101","From-Realm":"<IPP>","State":"Confirmed"}' >>> >>> http://localhost:8080/presence/ >>> {"Call-ID":"1020101@<IPP>","Event-Category":"presence","Event-Name":"update","Event-Package":"dialog","Expires":"3600","To":"sip:1020108@<IPK>:50060","To-User":"1020108","To-Realm":"<IPK>:50060","From":"sip:1020101@<IPP>","From-User":"1020101","From-Realm":"<IPP>","State":"Confirmed"} >>> >>> >>> >>> >>> Kamailio appears to be processing the command OK, so I think I am just >>> not setting it up properly> >>> >>> Anybody having any luck with this procedure, let me know how you are >>> getting it to work. >>> >>> >>> Bill >>> >>> >>> >>> _______________________________________________ >>> Kamailio (SER) - Users Mailing List >>> sr-users(a)lists.kamailio.org >>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users -- Henning Westerholt - https://skalatan.de/blog/ Kamailio services - https://skalatan.de/services

2 1

Info: Upgrading kamcli to work with Python3
by Daniel-Constantin Mierla 30 Aug '19

30 Aug '19

Hello, with the perspective that Python2 is going to be removed from the major Linux distributes starting with the beginning of next year, the work to upgrade kamcli to run with Python3 has been started. >From now on, master branch of kamcli is expected to work only with Python3: * https://github.com/kamailio/kamcli There is still work to be done to upgrade all the code, but any use of it should be done with Python3 and eventual issues to be filed on bug tracker. Of course, pull requests are welcome as always! Who wants to use the version for Python2 has to use the code from git branch v1.2-python2. That branch is probably not going to receive any new feature, it will be kept for use with older systems (as well as a running option during the upgrade period to Python3). Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

1 0

IMC module not sending messages to members of a conference room
by david＠aslo.us 29 Aug '19

29 Aug '19

2 1

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