- sr-users - kamailio.org

Unregister with Multiple Contacts
by Charles Phillips 21 Feb '21

21 Feb '21

Happy Friday! To clean up contacts that have sent requests to unregister (Expires: 0) I am executing the following after a 200 OK response from the upstream server: reg_fetch_contacts("location", "$fu", "un_reg"); xlog("L_INFO", "Removing unregistered contact From: $si To: $tu Ruid: $ulc(un_reg=>ruid)\n"); unregister("location", "$fu", "$ulc(un_reg=>ruid)”); This produces the desired result when there is only one contact per AoR, but when multiple contacts are present, it seems to delete the first ruid (which makes sense as I am only providing the $fu). So, the question, can I select the contact by call-id or some other unique identifier specific to the desired contact that I can grab from the transaction? Reading the reg_fetch_contact and unregister docs, they do not seem to provide for selection beyond uri. - Charles

2 3

loose_route() does not find socket by name
by Juha Heinanen 21 Feb '21

21 Feb '21

I'm returning to this thread, since after some more testing, I found that loose_route() does not (at least always) detect that a pair of route headers denotes itself. In config I have defined: listen=tls:192.x.x.x:8005 name "ext_tls" modparam("rr", "sockname_mode", 1) and Route header looks like this: ROUTE: <sip:tenantX.teams.tutpro.com:8005;transport=tls;r2=on;sn=ext_tls;lr;n1;avp=savp;pm=0>,<sip:192.x.x.x:5070;transport=tcp;r2=on;lr;n1;avp=savp;pm=0> Then this code: loose_route(); if ($du != "") { xinfo("Routing in-dialog $rm <$ru> from <$fu> to <$du> based on route uri\n"); } produces to syslog: INFO: Routing in-dialog ACK <...> from <...> to <...> based on route uri -- Juha

1 3

Connection between Kamailio and redirect server
by Igor Potjevlesh 18 Feb '21

18 Feb '21

Hello ! I will have to connect my Kamailio proxies to a routing server which will receive INVITE and replies with 302 and a list of a SIP Contact where (gateways, IP, prefixes or whatever we want) the call must be routed to. I'm wondering what would be the best approach to handle with Kamalio those 302 and then proceed with the routing? For the moment, we use to work with carrierroute. But, since the redirect server will take the routing decision, I believe that carrierroute will no be useful anymore. Thank you for your inputs/experience. Regards, Igor. -- L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast. https://www.avast.com/antivirus

3 4

Kamailio (docker) not even starting
by Nuñez, Mario 18 Feb '21

18 Feb '21

Hello, I started from scratch by getting this Docker image: https://hub.docker.com/layers/kamailio/kamailio/5.4.4-trusty/images/sha256-… Then running: docker pull kamailio/kamailio:5.4.4-trusty Then starting an container with the command: docker run -d --name mykamailio -h mykamailio -p "5060-5061:5060-5061" -p "5060:5060/udp" -p "5064-5065:5064-5065" -p "5064-5065:5064-5065/udp" -p "7000-7001:7000-7001" -p "7000:7000/udp" -e "KAMAILIO_LOG_LEVEL=info" -e "KAMAILIO_ENABLE_ROLES=websockets,message,presence_query,presence_sync,presence_notify_sync,registrar_sync" -e "RABBITMQ_HOSTS=rabbitmq.local" --cap-add IPC_LOCK --cap-add SYS_NICE --cap-add SYS_RESOURCE --cap-add NET_RAW kamailio/kamailio:5.4.4-trusty I get into container using cli and ran: Kamtcl start Then container stopped with this log: Listening on udp: 127.0.0.1:5060 udp: 172.17.0.4:5060 tcp: 127.0.0.1:5060 tcp: 172.17.0.4:5060 Aliases: tcp: mykamailio:5060 tcp: localhost:5060 0(1) INFO: <core> [core/tcp_main.c:4984]: init_tcp(): using epoll_lt as the io watch method (auto detected) udp: mykamailio:5060 udp: localhost:5060 0(1) INFO: rr [../outbound/api.h:52]: ob_load_api(): unable to import bind_ob - maybe module is not loaded 0(1) INFO: rr [rr_mod.c:185]: mod_init(): outbound module not available 0(1) INFO: <core> [main.c:2854]: main(): processes (at least): 33 - shm size: 67108864 - pkg size: 8388608 0(1) INFO: <core> [core/udp_server.c:154]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 0(1) INFO: <core> [core/udp_server.c:206]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 0(1) INFO: <core> [core/udp_server.c:154]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 0(1) INFO: <core> [core/udp_server.c:206]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 21(28) INFO: jsonrpcs [jsonrpcs_sock.c:443]: jsonrpc_dgram_process(): a new child 0/28 23(30) INFO: ctl [io_listener.c:214]: io_listen_loop(): io_listen_loop: using epoll_lt io watch method (config) 0(1) ALERT: <core> [main.c:780]: handle_sigs(): child process 77 exited normally, status=255 0(1) INFO: <core> [main.c:808]: handle_sigs(): terminating due to SIGCHLD 2(9) INFO: <core> [main.c:863]: sig_usr(): signal 15 received 1(8) INFO: <core> [main.c:863]: sig_usr(): signal 15 received 4(11) INFO: <core> [main.c:863]: sig_usr(): signal 15 received 5(12) INFO: <core> [main.c:863]: sig_usr(): signal 15 received 7(14) INFO: <core> [main.c:863]: sig_usr(): signal 15 received 10(17) INFO: <core> [main.c:863]: sig_usr(): signal 15 received 8(15) INFO: <core> [main.c:863]: sig_usr(): signal 15 received 9(16) INFO: <core> [main.c:863]: sig_usr(): signal 15 received 3(10) INFO: <core> [main.c:863]: sig_usr(): signal 15 received 11(18) INFO: <core> [main.c:863]: sig_usr(): signal 15 received 14(21) INFO: <core> [main.c:863]: sig_usr(): signal 15 received 17(24) INFO: <core> [main.c:863]: sig_usr(): signal 15 received 15(22) INFO: <core> [main.c:863]: sig_usr(): signal 15 received 12(19) INFO: <core> [main.c:863]: sig_usr(): signal 15 received 18(25) INFO: <core> [main.c:863]: sig_usr(): signal 15 received 6(13) INFO: <core> [main.c:863]: sig_usr(): signal 15 received 13(20) INFO: <core> [main.c:863]: sig_usr(): signal 15 received 16(23) INFO: <core> [main.c:863]: sig_usr(): signal 15 received 23(30) INFO: <core> [main.c:863]: sig_usr(): signal 15 received 22(29) INFO: <core> [main.c:863]: sig_usr(): signal 15 received 19(26) INFO: <core> [main.c:863]: sig_usr(): signal 15 received 21(28) INFO: <core> [main.c:863]: sig_usr(): signal 15 received 20(27) INFO: <core> [main.c:863]: sig_usr(): signal 15 received 32(39) CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 13 32(39) INFO: <core> [main.c:863]: sig_usr(): signal 15 received 25(32) INFO: <core> [main.c:863]: sig_usr(): signal 15 received 27(34) INFO: <core> [main.c:863]: sig_usr(): signal 15 received 29(36) INFO: <core> [main.c:863]: sig_usr(): signal 15 received 30(37) INFO: <core> [main.c:863]: sig_usr(): signal 15 received 26(33) INFO: <core> [main.c:863]: sig_usr(): signal 15 received 28(35) INFO: <core> [main.c:863]: sig_usr(): signal 15 received 31(38) INFO: <core> [main.c:863]: sig_usr(): signal 15 received 24(31) INFO: <core> [main.c:863]: sig_usr(): signal 15 received 0(1) ERROR: ctl [ctl.c:390]: mod_destroy(): ERROR: ctl: could not delete unix socket /var/run/kamailio//kamailio_ctl: No such file or directory (2) 0(1) INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized Any idea about what could be the problem? Thank you in advance This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavors to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener información confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente y pueden estar protegidos por secreto profesional. Si usted recibe este correo electrónico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningún compromiso para el grupo Atos, salvo ratificación escrita por ambas partes. Aunque se esfuerza al máximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no será responsable de cualesquiera daños que puedan resultar de una transmisión de virus.

2 1

FW: re I am trying to get a webrtc setup going. Here is what I have
by Daniel Siemens 17 Feb '21

17 Feb '21

I have tried to follow the instructions from the site, Kamaillo however won't startup a number of errors below. Is the version on the web rtc site specific to a version? Site is https://github.com/havfo/WEBRTC-to-SIP [root@ec2-sipproxy01 ~]# service kamailio status Redirecting to /bin/systemctl status kamailio.service â- kamailio.service - Kamailio (OpenSER) - the Open Source SIP Server Loaded: loaded (/usr/lib/systemd/system/kamailio.service; enabled; vendor preset: disabled) Active: failed (Result: start-limit) since Fri 2021-02-12 14:52:06 CST; 4 days ago Main PID: 5329 (code=exited, status=255) Feb 12 14:52:05 ec2-sipproxy01.multiservice.com systemd[1]: kamailio.service: main process exited, code=exited, status=255/n/a Feb 12 14:52:05 ec2-sipproxy01.multiservice.com systemd[1]: Unit kamailio.service entered failed state. Feb 12 14:52:05 ec2-sipproxy01.multiservice.com systemd[1]: kamailio.service failed. Feb 12 14:52:06 ec2-sipproxy01.multiservice.com systemd[1]: kamailio.service holdoff time over, scheduling restart. Feb 12 14:52:06 ec2-sipproxy01.multiservice.com systemd[1]: Stopped Kamailio (OpenSER) - the Open Source SIP Server. Feb 12 14:52:06 ec2-sipproxy01.multiservice.com systemd[1]: start request repeated too quickly for kamailio.service Feb 12 14:52:06 ec2-sipproxy01.multiservice.com systemd[1]: Failed to start Kamailio (OpenSER) - the Open Source SIP Server. Feb 12 14:52:06 ec2-sipproxy01.multiservice.com systemd[1]: Unit kamailio.service entered failed state. Feb 12 14:52:06 ec2-sipproxy01.multiservice.com systemd[1]: kamailio.service failed. [root@ec2-sipproxy01 ~]# service kamailio start Redirecting to /bin/systemctl start kamailio.service [root@ec2-sipproxy01 ~]# journalctl -xe -- -- The start-up result is done. Feb 16 15:35:13 ec2-sipproxy01.multiservice.com kamailio[12905]: ERROR: bad config file (4 errors) Feb 16 15:35:13 ec2-sipproxy01.multiservice.com kamailio[12905]: loading modules under config path: /usr/lib64/kamailio/modules/ Feb 16 15:35:13 ec2-sipproxy01.multiservice.com systemd[1]: kamailio.service: main process exited, code=exited, status=255/n/a Feb 16 15:35:13 ec2-sipproxy01.multiservice.com systemd[1]: Unit kamailio.service entered failed state. Feb 16 15:35:13 ec2-sipproxy01.multiservice.com systemd[1]: kamailio.service failed. Feb 16 15:35:13 ec2-sipproxy01.multiservice.com systemd[1]: kamailio.service holdoff time over, scheduling restart. Feb 16 15:35:13 ec2-sipproxy01.multiservice.com systemd[1]: Stopped Kamailio (OpenSER) - the Open Source SIP Server. -- Subject: Unit kamailio.service has finished shutting down -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit kamailio.service has finished shutting down. Feb 16 15:35:13 ec2-sipproxy01.multiservice.com systemd[1]: Started Kamailio (OpenSER) - the Open Source SIP Server. -- Subject: Unit kamailio.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit kamailio.service has finished starting up. -- -- The start-up result is done. Feb 16 15:35:13 ec2-sipproxy01.multiservice.com kamailio[12908]: ERROR: bad config file (4 errors) Feb 16 15:35:13 ec2-sipproxy01.multiservice.com kamailio[12908]: loading modules under config path: /usr/lib64/kamailio/modules/ Feb 16 15:35:13 ec2-sipproxy01.multiservice.com systemd[1]: kamailio.service: main process exited, code=exited, status=255/n/a Feb 16 15:35:13 ec2-sipproxy01.multiservice.com systemd[1]: Unit kamailio.service entered failed state. Feb 16 15:35:13 ec2-sipproxy01.multiservice.com systemd[1]: kamailio.service failed. Feb 16 15:35:13 ec2-sipproxy01.multiservice.com systemd[1]: kamailio.service holdoff time over, scheduling restart. Feb 16 15:35:13 ec2-sipproxy01.multiservice.com systemd[1]: Stopped Kamailio (OpenSER) - the Open Source SIP Server. -- Subject: Unit kamailio.service has finished shutting down -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit kamailio.service has finished shutting down. Feb 16 15:35:13 ec2-sipproxy01.multiservice.com systemd[1]: start request repeated too quickly for kamailio.service Feb 16 15:35:13 ec2-sipproxy01.multiservice.com systemd[1]: Failed to start Kamailio (OpenSER) - the Open Source SIP Server. -- Subject: Unit kamailio.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit kamailio.service has failed. -- -- The result is failed. Feb 16 15:35:13 ec2-sipproxy01.multiservice.com systemd[1]: Unit kamailio.service entered failed state. Feb 16 15:35:13 ec2-sipproxy01.multiservice.com systemd[1]: kamailio.service failed. 2021-02-16T15:35:13.330759-06:00 ec2-sipproxy01.multiservice.com systemd[1]: kamailio.service failed. 2021-02-16T15:35:13.520260-06:00 ec2-sipproxy01.multiservice.com systemd[1]: kamailio.service holdoff time over, scheduling restart. 2021-02-16T15:35:13.520939-06:00 ec2-sipproxy01.multiservice.com systemd[1]: Stopped Kamailio (OpenSER) - the Open Source SIP Server. 2021-02-16T15:35:13.527280-06:00 ec2-sipproxy01.multiservice.com systemd[1]: Started Kamailio (OpenSER) - the Open Source SIP Server. 2021-02-16T15:35:13.540778-06:00 ec2-sipproxy01.multiservice.com kamailio: INFO: tls [tls_init.c:503]: init_tls_compression(): disabling compression... 2021-02-16T15:35:13.547098-06:00 ec2-sipproxy01.multiservice.com kamailio: CRITICAL: <core> [core/cfg.y:3592]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 463, column 4: syntax error 2021-02-16T15:35:13.547118-06:00 ec2-sipproxy01.multiservice.com kamailio: CRITICAL: <core> [core/cfg.y:3592]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 463, column 4: bad command 2021-02-16T15:35:13.547515-06:00 ec2-sipproxy01.multiservice.com kamailio: CRITICAL: <core> [core/cfg.y:3592]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 487, column 1: syntax error 2021-02-16T15:35:13.547528-06:00 ec2-sipproxy01.multiservice.com kamailio: CRITICAL: <core> [core/cfg.y:3592]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 487, column 1: 2021-02-16T15:35:13.547743-06:00 ec2-sipproxy01.multiservice.com kamailio: INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized 2021-02-16T15:35:13.547904-06:00 ec2-sipproxy01.multiservice.com kamailio[12908]: ERROR: bad config file (4 errors) 2021-02-16T15:35:13.548435-06:00 ec2-sipproxy01.multiservice.com kamailio[12908]: loading modules under config path: /usr/lib64/kamailio/modules/ 2021-02-16T15:35:13.555285-06:00 ec2-sipproxy01.multiservice.com systemd[1]: kamailio.service: main process exited, code=exited, status=255/n/a 2021-02-16T15:35:13.555547-06:00 ec2-sipproxy01.multiservice.com systemd[1]: Unit kamailio.service entered failed state. 2021-02-16T15:35:13.555755-06:00 ec2-sipproxy01.multiservice.com systemd[1]: kamailio.service failed. 2021-02-16T15:35:13.769880-06:00 ec2-sipproxy01.multiservice.com systemd[1]: kamailio.service holdoff time over, scheduling restart. 2021-02-16T15:35:13.770589-06:00 ec2-sipproxy01.multiservice.com systemd[1]: Stopped Kamailio (OpenSER) - the Open Source SIP Server. 2021-02-16T15:35:13.770827-06:00 ec2-sipproxy01.multiservice.com systemd[1]: start request repeated too quickly for kamailio.service 2021-02-16T15:35:13.771068-06:00 ec2-sipproxy01.multiservice.com systemd[1]: Failed to start Kamailio (OpenSER) - the Open Source SIP Server. 2021-02-16T15:35:13.771292-06:00 ec2-sipproxy01.multiservice.com systemd[1]: Unit kamailio.service entered failed state. 2021-02-16T15:35:13.771499-06:00 ec2-sipproxy01.multiservice.com systemd[1]: kamailio.service failed. 2021-02-16T15:35:38.243853-06:00 ec2-sipproxy01.multiservice.com kamailio: INFO: tls [tls_init.c:503]: init_tls_compression(): disabling compression... 2021-02-16T15:35:38.250426-06:00 ec2-sipproxy01.multiservice.com kamailio: CRITICAL: <core> [core/cfg.y:3592]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 463, column 4: syntax error 2021-02-16T15:35:38.250444-06:00 ec2-sipproxy01.multiservice.com kamailio: CRITICAL: <core> [core/cfg.y:3592]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 463, column 4: bad command 2021-02-16T15:35:38.250942-06:00 ec2-sipproxy01.multiservice.com kamailio: CRITICAL: <core> [core/cfg.y:3592]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 487, column 1: syntax error 2021-02-16T15:35:38.250954-06:00 ec2-sipproxy01.multiservice.com kamailio: CRITICAL: <core> [core/cfg.y:3592]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 487, column 1: 2021-02-16T15:35:38.251218-06:00 ec2-sipproxy01.multiservice.com kamailio: INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized 2021-02-16T15:35:47.558478-06:00 ec2-sipproxy01.multiservice.com kamailio: INFO: tls [tls_init.c:503]: init_tls_compression(): disabling compression... 2021-02-16T15:35:47.565760-06:00 ec2-sipproxy01.multiservice.com kamailio: CRITICAL: <core> [core/cfg.y:3592]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 463, column 4: syntax error 2021-02-16T15:35:47.565774-06:00 ec2-sipproxy01.multiservice.com kamailio: CRITICAL: <core> [core/cfg.y:3592]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 463, column 4: bad command 2021-02-16T15:35:47.566605-06:00 ec2-sipproxy01.multiservice.com kamailio: CRITICAL: <core> [core/cfg.y:3592]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 487, column 1: syntax error 2021-02-16T15:35:47.566629-06:00 ec2-sipproxy01.multiservice.com kamailio: CRITICAL: <core> [core/cfg.y:3592]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 487, column 1: 2021-02-16T15:35:47.566815-06:00 ec2-sipproxy01.multiservice.com kamailio: INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized 2021-02-16T15:36:00.494995-06:00 ec2-sipproxy01.multiservice.com kamailio: INFO: tls [tls_init.c:503]: init_tls_compression(): disabling compression... 2021-02-16T15:36:00.502491-06:00 ec2-sipproxy01.multiservice.com kamailio: CRITICAL: <core> [core/cfg.y:3592]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 463, column 4: syntax error 2021-02-16T15:36:00.502503-06:00 ec2-sipproxy01.multiservice.com kamailio: CRITICAL: <core> [core/cfg.y:3592]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 463, column 4: bad command 2021-02-16T15:36:00.503042-06:00 ec2-sipproxy01.multiservice.com kamailio: CRITICAL: <core> [core/cfg.y:3592]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 487, column 1: syntax error 2021-02-16T15:36:00.503052-06:00 ec2-sipproxy01.multiservice.com kamailio: CRITICAL: <core> [core/cfg.y:3592]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 487, column 1: 2021-02-16T15:36:00.503240-06:00 ec2-sipproxy01.multiservice.com kamailio: INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized 2021-02-16T15:36:05.742256-06:00 ec2-sipproxy01.multiservice.com kamailio: INFO: tls [tls_init.c:503]: init_tls_compression(): disabling compression... 2021-02-16T15:36:05.749633-06:00 ec2-sipproxy01.multiservice.com kamailio: CRITICAL: <core> [core/cfg.y:3592]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 463, column 4: syntax error 2021-02-16T15:36:05.749647-06:00 ec2-sipproxy01.multiservice.com kamailio: CRITICAL: <core> [core/cfg.y:3592]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 463, column 4: bad command 2021-02-16T15:36:05.750062-06:00 ec2-sipproxy01.multiservice.com kamailio: CRITICAL: <core> [core/cfg.y:3592]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 487, column 1: syntax error 2021-02-16T15:36:05.750072-06:00 ec2-sipproxy01.multiservice.com kamailio: CRITICAL: <core> [core/cfg.y:3592]: yyerror_at(): parse error in config file /etc/kamailio/ka Int eh config file it having issues with rr module I have unloaded It in the above but is wont run 446 if (loose_route()) { 447 #!ifdef WITH_WEBSOCKETS 448 if ($du == "") { 449 if (!handle_ruri_alias()) { 450 xlog("L_ERR", "Bad alias <$ru>\n"); 451 sl_send_reply("400", "Bad Request"); 452 exit; 453 } 454 } 455 #!endif 456 route(DLGURI); 457 if (is_method("ACK")) { 458 # ACK is forwarded statelessy 459 route(NATMANAGE); 460 } else if (is_method("NOTIFY")) { 461 # Add Record-Route for in-dialog NOTIFY as per RFC 6665. 462 # record_route(); 463 } 464 route(RELAY); 465 } else { 466 if (is_method("SUBSCRIBE") && uri == myself) { 467 # in-dialog subscribe requests 468 route(PRESENCE); 469 exit; 470 } 471 if (is_method("ACK")) { 472 if (t_check_trans()) { 473 # no loose-route, but stateful ACK; 474 # must be an ACK after a 487 475 # or e.g. 404 from upstream server 476 route(RELAY); 477 exit; 478 } else { 479 # ACK without matching transaction ... ignore and d Yes I have the RR module /usr/lib64/kamailio/modules/: total 29380 -rwxr-xr-x. 1 root root 127160 Dec 14 12:23 acc_diameter.so -rwxr-xr-x. 1 root root 264912 Dec 14 12:23 acc.so -rwxr-xr-x. 1 root root 49400 Dec 14 12:23 alias_db.so -rwxr-xr-x. 1 root root 858072 Dec 14 12:23 app_jsdt.so -rwxr-xr-x. 1 root root 82264 Dec 14 12:23 async.so -rwxr-xr-x. 1 root root 94792 Dec 14 12:23 auth_db.so -rwxr-xr-x. 1 root root 168352 Dec 14 12:23 auth_diameter.so -rwxr-xr-x. 1 root root 199544 Dec 14 12:23 auth_identity.so -rwxr-xr-x. 1 root root 186696 Dec 14 12:23 auth.so -rwxr-xr-x. 1 root root 325600 Dec 14 12:23 avpops.so -rwxr-xr-x. 1 root root 128952 Dec 14 12:23 avp.so -rwxr-xr-x. 1 root root 53752 Dec 14 12:23 benchmark.so -rwxr-xr-x. 1 root root 21512 Dec 14 12:23 blst.so -rwxr-xr-x. 1 root root 94792 Dec 14 12:23 call_control.so -rwxr-xr-x. 1 root root 90384 Dec 14 12:23 call_obj.so -rwxr-xr-x. 1 root root 44544 Dec 14 12:23 cfg_db.so -rwxr-xr-x. 1 root root 33008 Dec 14 12:23 cfg_rpc.so -rwxr-xr-x. 1 root root 185136 Dec 14 12:23 cfgt.so -rwxr-xr-x. 1 root root 76744 Dec 14 12:23 cfgutils.so -rwxr-xr-x. 1 root root 147656 Dec 14 12:23 corex.so -rwxr-xr-x. 1 root root 29072 Dec 14 12:23 counters.so -rwxr-xr-x. 1 root root 325520 Dec 14 12:23 ctl.so -rwxr-xr-x. 1 root root 108048 Dec 14 12:23 db2_ops.so -rwxr-xr-x. 1 root root 371184 Dec 14 12:23 db_berkeley.so -rwxr-xr-x. 1 root root 192264 Dec 14 12:23 db_cluster.so -rwxr-xr-x. 1 root root 99168 Dec 14 12:23 db_flatstore.so -rwxr-xr-x. 1 root root 227840 Dec 14 12:23 db_mysql.so -rwxr-xr-x. 1 root root 537152 Dec 14 12:23 db_redis.so -rwxr-xr-x. 1 root root 57384 Dec 14 12:23 db_sqlite.so -rwxr-xr-x. 1 root root 247136 Dec 14 12:23 db_text.so -rwxr-xr-x. 1 root root 135240 Dec 14 12:23 db_unixodbc.so -rwxr-xr-x. 1 root root 147216 Dec 14 12:23 debugger.so -rwxr-xr-x. 1 root root 855392 Dec 14 12:23 dialog.so -rwxr-xr-x. 1 root root 408528 Dec 14 12:23 dispatcher.so -rwxr-xr-x. 1 root root 20088 Dec 14 12:23 diversion.so -rwxr-xr-x. 1 root root 87336 Dec 14 12:23 dlgs.so -rwxr-xr-x. 1 root root 219440 Dec 14 12:23 dmq.so -rwxr-xr-x. 1 root root 147600 Dec 14 12:23 domainpolicy.so -rwxr-xr-x. 1 root root 99352 Dec 14 12:23 domain.so -rwxr-xr-x. 1 root root 240576 Dec 14 12:23 drouting.so -rwxr-xr-x. 1 root root 99728 Dec 14 12:23 enum.so -rwxr-xr-x. 1 root root 32432 Dec 14 12:23 evrexec.so -rwxr-xr-x. 1 root root 103160 Dec 14 12:23 exec.so -rwxr-xr-x. 1 root root 32744 Dec 14 12:23 geoip.so -rwxr-xr-x. 1 root root 69824 Dec 14 12:23 group.so -rwxr-xr-x. 1 root root 40424 Dec 14 12:23 gzcompress.so -rwxr-xr-x. 1 root root 374784 Dec 14 12:23 htable.so -rwxr-xr-x. 1 root root 260856 Dec 14 12:23 http_async_client.so -rwxr-xr-x. 1 root root 269776 Dec 14 12:23 http_client.so -rwxr-xr-x. 1 root root 242912 Dec 14 12:23 imc.so -rwxr-xr-x. 1 root root 213968 Dec 14 12:23 ipops.so -rwxr-xr-x. 1 root root 317296 Dec 14 12:23 janssonrpcc.so -rwxr-xr-x. 1 root root 73952 Dec 14 12:23 jansson.so -rwxr-xr-x. 1 root root 106896 Dec 14 12:23 jsonrpcc.so -rwxr-xr-x. 1 root root 260304 Dec 14 12:23 jsonrpcs.so -rwxr-xr-x. 1 root root 73808 Dec 14 12:23 json.so -rwxr-xr-x. 1 root root 78568 Dec 14 12:23 keepalive.so -rwxr-xr-x. 1 root root 44384 Dec 14 12:23 kemix.so -rwxr-xr-x. 1 root root 82216 Dec 14 12:23 kex.so -rwxr-xr-x. 1 root root 15904 Dec 14 12:23 log_custom.so -rwxr-xr-x. 1 root root 28272 Dec 14 12:23 log_systemd.so -rwxr-xr-x. 1 root root 29072 Dec 14 12:23 malloc_test.so -rwxr-xr-x. 1 root root 114856 Dec 14 12:23 mangler.so -rwxr-xr-x. 1 root root 57216 Dec 14 12:23 matrix.so -rwxr-xr-x. 1 root root 32832 Dec 14 12:23 maxfwd.so -rwxr-xr-x. 1 root root 152816 Dec 14 12:23 mediaproxy.so -rwxr-xr-x. 1 root root 252792 Dec 14 12:23 mohqueue.so -rwxr-xr-x. 1 root root 108080 Dec 14 12:23 mqueue.so -rwxr-xr-x. 1 root root 194296 Dec 14 12:23 msilo.so -rwxr-xr-x. 1 root root 179264 Dec 14 12:23 msrp.so -rwxr-xr-x. 1 root root 169232 Dec 14 12:23 mtree.so -rwxr-xr-x. 1 root root 249560 Dec 14 12:23 nathelper.so -rwxr-xr-x. 1 root root 132816 Dec 14 12:23 nat_traversal.so -rwxr-xr-x. 1 root root 218632 Dec 14 12:23 ndb_redis.so -rwxr-xr-x. 1 root root 15760 Dec 14 12:23 nosip.so -rwxr-xr-x. 1 root root 61096 Dec 14 12:23 outbound.so -rwxr-xr-x. 1 root root 49648 Dec 14 12:23 path.so -rwxr-xr-x. 1 root root 69480 Dec 14 12:23 pdb.so -rwxr-xr-x. 1 root root 107288 Dec 14 12:23 pdt.so -rwxr-xr-x. 1 root root 285944 Dec 14 12:23 permissions.so -rwxr-xr-x. 1 root root 82472 Dec 14 12:23 pike.so -rwxr-xr-x. 1 root root 117192 Dec 14 12:23 pipelimit.so -rwxr-xr-x. 1 root root 49504 Dec 14 12:23 prefix_route.so -rwxr-xr-x. 1 root root 40448 Dec 14 12:23 presence_conference.so -rwxr-xr-x. 1 root root 81552 Dec 14 12:23 presence_dialoginfo.so -rwxr-xr-x. 1 root root 19616 Dec 14 12:23 presence_mwi.so -rwxr-xr-x. 1 root root 15480 Dec 14 12:23 presence_profile.so -rwxr-xr-x. 1 root root 15480 Dec 14 12:23 presence_reginfo.so -rwxr-xr-x. 1 root root 1059480 Dec 14 12:23 presence.so -rwxr-xr-x. 1 root root 214064 Dec 14 12:23 presence_xml.so -rwxr-xr-x. 1 root root 7280 Dec 14 12:23 print_lib.so -rwxr-xr-x. 1 root root 20152 Dec 14 12:23 print.so -rwxr-xr-x. 1 root root 69208 Dec 14 12:23 pua_bla.so -rwxr-xr-x. 1 root root 94096 Dec 14 12:23 pua_dialoginfo.so -rwxr-xr-x. 1 root root 40744 Dec 14 12:23 pua_json.so -rwxr-xr-x. 1 root root 110536 Dec 14 12:23 pua_reginfo.so -rwxr-xr-x. 1 root root 48504 Dec 14 12:23 pua_rpc.so -rwxr-xr-x. 1 root root 469376 Dec 14 12:23 pua.so -rwxr-xr-x. 1 root root 57128 Dec 14 12:23 pua_usrloc.so -rwxr-xr-x. 1 root root 192416 Dec 14 12:23 pua_xmpp.so -rwxr-xr-x. 1 root root 472080 Dec 14 12:23 p_usrloc.so -rwxr-xr-x. 1 root root 207928 Dec 14 12:23 pv_headers.so -rwxr-xr-x. 1 root root 872296 Dec 14 12:23 pv.so -rwxr-xr-x. 1 root root 114608 Dec 14 12:23 qos.so -rwxr-xr-x. 1 root root 103704 Dec 14 12:23 ratelimit.so -rwxr-xr-x. 1 root root 325912 Dec 14 12:23 registrar.so -rwxr-xr-x. 1 root root 564528 Dec 14 12:23 rls.so -rwxr-xr-x. 1 root root 232184 Dec 14 12:23 rr.so -rwxr-xr-x. 1 root root 32328 Dec 14 12:23 rtimer.so -rwxr-xr-x. 1 root root 369376 Dec 14 12:23 rtpengine.so -rwxr-xr-x. 1 root root 250480 Dec 14 12:23 rtpproxy.so -rwxr-xr-x. 1 root root 168568 Dec 14 12:23 sanity.so -rwxr-xr-x. 1 root root 560632 Dec 14 12:23 sca.so -rwxr-xr-x. 1 root root 170664 Dec 14 12:23 sctp.so -rwxr-xr-x. 1 root root 204168 Dec 14 12:23 sdpops.so -rwxr-xr-x. 1 root root 502880 Dec 14 12:23 seas.so -rwxr-xr-x. 1 root root 283440 Dec 14 12:23 sipcapture.so -rwxr-xr-x. 1 root root 62312 Dec 14 12:23 sipdump.so -rwxr-xr-x. 1 root root 326352 Dec 14 12:23 siptrace.so -rwxr-xr-x. 1 root root 75352 Dec 14 12:23 sipt.so -rwxr-xr-x. 1 root root 341424 Dec 14 12:23 siputils.so -rwxr-xr-x. 1 root root 121152 Dec 14 12:23 sl.so -rwxr-xr-x. 1 root root 86016 Dec 14 12:23 smsops.so -rwxr-xr-x. 1 root root 189544 Dec 14 12:23 sms.so -rwxr-xr-x. 1 root root 36864 Dec 14 12:23 speeddial.so -rwxr-xr-x. 1 root root 157576 Dec 14 12:23 sqlops.so -rwxr-xr-x. 1 root root 126992 Dec 14 12:23 ss7ops.so -rwxr-xr-x. 1 root root 90344 Dec 14 12:23 sst.so -rwxr-xr-x. 1 root root 32504 Dec 14 12:23 statistics.so -rwxr-xr-x. 1 root root 32752 Dec 14 12:23 statsc.so -rwxr-xr-x. 1 root root 37360 Dec 14 12:23 statsd.so -rwxr-xr-x. 1 root root 57016 Dec 14 12:23 stun.so -rwxr-xr-x. 1 root root 7216 Dec 14 12:23 systemdops.so -rwxr-xr-x. 1 root root 91960 Dec 14 12:23 tcpops.so -rwxr-xr-x. 1 root root 405344 Dec 14 12:23 textops.so -rwxr-xr-x. 1 root root 105624 Dec 14 12:23 textopsx.so -rwxr-xr-x. 1 root root 36680 Dec 14 12:23 timer.so -rwxr-xr-x. 1 root root 558432 Dec 14 12:23 tls.so -rwxr-xr-x. 1 root root 25208 Dec 14 12:23 tmrec.so -rwxr-xr-x. 1 root root 1369096 Dec 14 12:23 tm.so -rwxr-xr-x. 1 root root 138960 Dec 14 12:23 tmx.so -rwxr-xr-x. 1 root root 176800 Dec 14 12:23 topoh.so -rwxr-xr-x. 1 root root 184272 Dec 14 12:23 topos_redis.so -rwxr-xr-x. 1 root root 255600 Dec 14 12:23 topos.so -rwxr-xr-x. 1 root root 95336 Dec 14 12:23 tsilo.so -rwxr-xr-x. 1 root root 61832 Dec 14 12:23 uac_redirect.so -rwxr-xr-x. 1 root root 460072 Dec 14 12:23 uac.so -rwxr-xr-x. 1 root root 61640 Dec 14 12:23 uid_auth_db.so -rwxr-xr-x. 1 root root 62128 Dec 14 12:23 uid_avp_db.so -rwxr-xr-x. 1 root root 70328 Dec 14 12:23 uid_domain.so -rwxr-xr-x. 1 root root 37064 Dec 14 12:23 uid_gflags.so -rwxr-xr-x. 1 root root 40824 Dec 14 12:23 uid_uri_db.so -rwxr-xr-x. 1 root root 57776 Dec 14 12:23 uri_db.so -rwxr-xr-x. 1 root root 99880 Dec 14 12:23 userblacklist.so -rwxr-xr-x. 1 root root 397712 Dec 14 12:23 usrloc.so -rwxr-xr-x. 1 root root 119520 Dec 14 12:23 utils.so -rwxr-xr-x. 1 root root 216192 Dec 14 12:23 websocket.so -rwxr-xr-x. 1 root root 74112 Dec 14 12:23 xcap_client.so -rwxr-xr-x. 1 root root 185760 Dec 14 12:23 xcap_server.so -rwxr-xr-x. 1 root root 340544 Dec 14 12:23 xhttp_pi.so -rwxr-xr-x. 1 root root 380144 Dec 14 12:23 xhttp_prom.so -rwxr-xr-x. 1 root root 90104 Dec 14 12:23 xhttp_rpc.so -rwxr-xr-x. 1 root root 69856 Dec 14 12:23 xhttp.so -rwxr-xr-x. 1 root root 58912 Dec 14 12:23 xlog.so -rwxr-xr-x. 1 root root 166304 Dec 14 12:23 xmpp.so -rwxr-xr-x. 1 root root 135952 Dec 14 12:23 xprint.so I'm not sure but maybe the config generator is for a different version? [root@ec2-sipproxy01 ~]# rpm -qa |grep kamailio kamailio-tls-5.4.3-0.el7.centos.x86_64 kamailio-gzcompress-5.4.3-0.el7.centos.x86_64 kamailio-utils-5.4.3-0.el7.centos.x86_64 kamailio-sctp-5.4.3-0.el7.centos.x86_64 kamailio-unixodbc-5.4.3-0.el7.centos.x86_64 kamailio-5.4.3-0.el7.centos.x86_64 kamailio-xmpp-5.4.3-0.el7.centos.x86_64 kamailio-tcpops-5.4.3-0.el7.centos.x86_64 kamailio-http_async_client-5.4.3-0.el7.centos.x86_64 kamailio-sqlite-5.4.3-0.el7.centos.x86_64 kamailio-json-5.4.3-0.el7.centos.x86_64 kamailio-websocket-5.4.3-0.el7.centos.x86_64 kamailio-mysql-5.4.3-0.el7.centos.x86_64 kamailio-presence-5.4.3-0.el7.centos.x86_64 kamailio-http_client-5.4.3-0.el7.centos.x86_64 kamailio-bdb-5.4.3-0.el7.centos.x86_64 kamailio-outbound-5.4.3-0.el7.centos.x86_64 kamailio-redis-5.4.3-0.el7.centos.x86_64 kamailio-statsd-5.4.3-0.el7.centos.x86_64 kamailio-sipcapture-daemon-config-5.4.3-0.el7.centos.x86_64 kamailio-xhttp-pi-5.4.3-0.el7.centos.x86_64 kamailio-geoip-5.4.3-0.el7.centos.x86_64 kamailio-jansson-5.4.3-0.el7.centos.x86_64 kamailio-sipdump-5.4.3-0.el7.centos.x86_64 ------------------------------------------------------------------ This email is intended solely for the use of the addressee and may contain information that is confidential, proprietary, or both. If you receive this email in error please immediately notify the sender and delete the email. ------------------------------------------------------------------

2 1

Cockroachdb and kamailio 5.4
by Jonathan Hunter 17 Feb '21

17 Feb '21

Hi Guys, Hope all are well? We are looking to implement kamailio with cockroachdb due to the advantages it gives us in terms of postgres management and clustering. I can see from a previous string http://sip-router.1086192.n5.nabble.com/CockroachDB-and-Kamailio-td189233.h… that someone has attempted this and even created their own branch. Has any further work been done on this, and if so has anyone got any advice/tips relating to it? As I am nervous about potentially using a branch and not a general release of kamailio moving forwards. I appreciate you cant support all database types but I would just be interested to hear people’s thoughts on the topic. Many thanks! Jon Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10

2 2

pipelimit with a kamailio cluster
by Daniel Donoghue 17 Feb '21

17 Feb '21

Hello, I have 2 stateful kamailio servers that receive incoming requests, load balanced across the 2 servers by our carrier trunk partners (outside of our control). I am looking at putting certain invites from these trunks into pipelimit to rate limit under some conditions but I have some questions: 1. How will pipelimit establish rates when requests can come in to either of my servers? 2. If pipelimit decides it is time to limit the requests, will both servers respect that limit? 3. does pipelimit rely on a db or can it use dmq, redis or other methods for cross-server communication? 4. Is there a maximum number of pipes that can be defined? Hope somebody can help me answer these questions. With every blessing, — Daniel Donoghue

3 4

haproxy and set_advertised_address()
by Sergey Safarov 16 Feb '21

16 Feb '21

haproxy sed dst_ip address from haproxy protocol https://github.com/kamailio/kamailio/blob/master/src/core/tcp_main.c#L987-L… How I can use this value inside set_advertised_address() function? Like set_advertised_address(dst_ip)

2 2

http_client/http_connect in request_route: INFO: <core> [main.c:857]: sig_usr(): signal 13 received
by Anthony Joseph Messina 16 Feb '21

16 Feb '21

With the following config # ----- http_client params ----- modparam("http_client", "httpredirect", 0) modparam("http_client", "connection_timeout", 2) modparam("http_client", "keep_connections", 1) modparam("http_client", "query_result", 0) modparam("http_client", "httpcon", "api=>https://api.example.com"); and after calling the following from request_route, $xavu(http=>rs)=http_connect("api", "/kamailio/message", "application/json", "$var(message_api)", "$xavu(http=>rb)"); if($xavu(http=>rs)==200) { jansson_get("result.code", $xavu(http=>rb), "$xavu(http=>code)"); jansson_get("result.message", $xavu(http=>rb), "$xavu(http=>message)"); sd_journal_print("LOG_DEBUG", "[$cfg(route)] Result: $xavu(http=>code), $xavu(http=>message)"); sl_send_reply("202", "Accepted"); exit; } I see the following in the log: INFO: <core> [main.c:857]: sig_usr(): signal 13 received It doesn't seem to have any negative effect, but I am wondering if it's something I should look into. If so, any pointers on where/how to begin? -- Anthony - https://messinet.com F9B6 560E 68EA 037D 8C3D D1C9 FF31 3BDB D9D8 99B6

1 0

Advice on handling SIP trunk to a Perimeta SBC
by Björn Bylander 16 Feb '21

16 Feb '21

Hi, So I’m tasked with setting up a SIP trunk to a Perimeta SBC (https://www.metaswitch.com/products/perimeta-sbc). Apparently, > Perimeta hides the topology of networks by rewriting or removing topology-sensitive information from SIP messages. By default, your Session Controller will make the following changes to SIP messages. > > The Session Controller generates new dialog identifiers (call-IDs, From tags and To tags) for each side of the call, so that it does not expose information about your core network to your access networks. > The Session Controller strips Record-Route and Route information from the message. > The Session Controller rewrites Contact and Via headers so that the source IP address is replaced with the local address of the outbound adjacency. > The Session Controller replaces the IP addresses in c= lines in SDP with the addresses it has allocated for media forwarding. For more information on this, see Media addresses and gates. My problem is this: When the Perimeta SBC sends its first INVITE (I can't say anything about any succeeding INVITEs yet) it's added a Record-Route header with the "lr" parameter included which, as far as I can see makes Kamailio think it should use loose routing which is all well I think. But when the SBC sends an ACK for the "200 OK" from the Kamailio side it doesn't include any Route headers and I think that makes it hard for Kamailio (at least with the standard script which is basically what I'm using) to know where to relay the ACK, at least it makes the t_check_trans() call in WITHINDLG after 'is_method("ACK")' return false which makes the script ignore the ACK. Any thoughts or suggestions on how to handle this? Thanks in advance, Björn Bylander

2 1

Usage of ldap/db2_ldap
by DEV 16 Feb '21

16 Feb '21

Hi! I'm trying to use the ldap / db2_ldap module in kamailio but I'm stuck because the docs seem to either be outdated or me being on the wrong track. >From what I understand, I need a single ldap.conf but there are two example files with different syntax: 1) https://github.com/kamailio/kamailio/blob/master/src/modules/db2_ldap/ldap.… 2) https://github.com/kamailio/kamailio/blob/master/src/modules/ldap/etc/ldap.… I'm already using ldap realtime for asterisk and want to switch kamailio to use the same objects by using this schema: https://github.com/kamailio/kamailio/blob/master/src/modules/db2_ldap/ser.s… When using syntax from (1) I receive this error: ERROR: ldap [ldap_mod.c:198]: mod_init(): no section found in config_file [/etc/kamailio/ldap.cfg] I double-checked my conf and it matches (1). When using (2), I got an error, telling me I left some tables unconfigured (even when mixing both syntax). What is the correct syntax to use ldap as my auth module and replace mysql auth tables? Thank you. Kind regards Kevin

3 5

Runnning kamailio (docker) with remote connection with MYSQL (docker) fails on start/restart due to socket or database connection
by Nuñez, Mario 16 Feb '21

16 Feb '21

Hi, I am running docker with this: https://hub.docker.com/layers/kamailio/kamailio/5.4.3-trusty/images/sha256-… and https://hub.docker.com/layers/mysql/library/mysql/8.0.23/images/sha256-8708… I made some configurations in Kamailio container: /etc/default/kamailio RUN_KAMAILIO=yes USER=kamailio GROUP=kamailio CFGFILE=/etc/kamailio/kamailio.cfg DUMP_CORE=yes /etc/kamailio/kamailio.cfg #!define WITH_MYSQL #!define WITH_AUTH #!define WITH_USRLOCDB /etc/kamailio/kamctlrc SIP_DOMAIN=kamailio.org DBENGINE=MYSQL DBHOST=172.19.0.3 DBPORT=3306 DBNAME=kamailio DBRWUSER="kamailio" DBRWPW="kamailiorw" DBROUSER="kamailioro" DBROPW="kamailioro" DBACCESSHOST=172.19.0.5 DBROOTUSER="root" DBROOTPW="whatever" CHARSET="latin1" USERCOL="user" Then I run creation of database: /usr/sbin/kamdbctl create All was ok so I can see in MYSQL database: +------------------+------------+-----------------------+ | user | host | plugin | +------------------+------------+-----------------------+ | root | % | mysql_native_password | | kamailio | 172.19.0.3 | mysql_native_password | | kamailioro | 172.19.0.3 | mysql_native_password | | kamailio | 172.19.0.5 | mysql_native_password | | kamailioro | 172.19.0.5 | mysql_native_password | | kamailio | localhost | mysql_native_password | | kamailioro | localhost | mysql_native_password | | mysql.infoschema | localhost | caching_sha2_password | | mysql.session | localhost | caching_sha2_password | | mysql.sys | localhost | caching_sha2_password | | root | localhost | mysql_native_password | +------------------+------------+-----------------------+ At this point, if I try to restart kamailio i get an error and container will never go up again, so I had to delete it and restart the whole installation and configuration process. Log details are: ==========================================ON RESTART KAMAILIO FROM CONTAINER CONSOLE: Listening on udp: 127.0.0.1:5060 udp: 172.17.0.4:5060 tcp: 127.0.0.1:5060 tcp: 172.17.0.4:5060 Aliases: tcp: mykamailio:5060 tcp: localhost:5060 udp: mykamailio:5060 udp: localhost:5060 0(1) INFO: <core> [core/tcp_main.c:4984]: init_tcp(): using epoll_lt as the io watch method (auto detected) 0(1) INFO: rr [../outbound/api.h:52]: ob_load_api(): unable to import bind_ob - maybe module is not loaded 0(1) INFO: rr [rr_mod.c:185]: mod_init(): outbound module not available 0(1) INFO: <core> [main.c:2834]: main(): processes (at least): 33 - shm size: 67108864 - pkg size: 8388608 0(1) INFO: <core> [core/udp_server.c:154]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 0(1) INFO: <core> [core/udp_server.c:206]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 0(1) INFO: <core> [core/udp_server.c:154]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 0(1) INFO: <core> [core/udp_server.c:206]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 21(28) INFO: jsonrpcs [jsonrpcs_sock.c:443]: jsonrpc_dgram_process(): a new child 0/28 23(30) INFO: ctl [io_listener.c:214]: io_listen_loop(): io_listen_loop: using epoll_lt io watch method (config) 0(1) ALERT: <core> [main.c:774]: handle_sigs(): child process 205 exited normally, status=255 0(1) INFO: <core> [main.c:802]: handle_sigs(): terminating due to SIGCHLD 2(9) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 1(8) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 3(10) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 4(11) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 6(13) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 5(12) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 7(14) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 10(17) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 12(19) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 14(21) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 29(36) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 24(31) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 28(35) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 15(22) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 19(26) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 13(20) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 17(24) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 8(15) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 23(30) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 22(29) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 21(28) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 26(33) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 20(27) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 31(38) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 32(39) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 9(16) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 30(37) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 11(18) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 16(23) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 27(34) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 18(25) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 25(32) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 0(1) ERROR: ctl [ctl.c:390]: mod_destroy(): ERROR: ctl: could not delete unix socket /var/run/kamailio//kamailio_ctl: No such file or directory (2) 0(1) INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized ==========================================SO CONTAINER WAS DOWN, AND THEN IF I TRY TO START CONTAINER AGAIN: Listening on udp: 127.0.0.1:5060 udp: 172.17.0.4:5060 udp: 172.19.0.5:5060 tcp: 127.0.0.1:5060 tcp: 172.17.0.4:5060 tcp: 172.19.0.5:5060 Aliases: tcp: mykamailio:5060 tcp: localhost:5060 udp: mykamailio:5060 udp: localhost:5060 0(1) INFO: <core> [core/tcp_main.c:4984]: init_tcp(): using epoll_lt as the io watch method (auto detected) 0(1) INFO: rr [../outbound/api.h:52]: ob_load_api(): unable to import bind_ob - maybe module is not loaded 0(1) INFO: rr [rr_mod.c:185]: mod_init(): outbound module not available 0(1) INFO: auth [auth_mod.c:346]: mod_init(): qop set, but nonce-count (nonce_count) support disabled 0(1) INFO: <core> [main.c:2834]: main(): processes (at least): 41 - shm size: 67108864 - pkg size: 8388608 0(1) ERROR: db_mysql [km_my_con.c:163]: db_mysql_new_connection(): driver error: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) 0(1) ERROR: <core> [db.c:319]: db_do_init2(): could not add connection to the pool 0(1) ERROR: usrloc [dlist.c:852]: register_udomain(): failed to open database connection 0(1) ERROR: registrar [registrar.c:711]: domain_fixup(): failed to register domain 0(1) ERROR: <core> [core/route.c:1167]: fix_actions(): fixing failed (code=-1) at cfg:/etc/kamailio/kamailio.cfg:698 0(1) ERROR: <core> [core/rvalue.c:3869]: fix_rval_expr(): failure in cfg at line: 698 col: 22 0(1) ERROR: <core> [core/rvalue.c:3869]: fix_rval_expr(): failure in cfg at line: 698 col: 22 0(1) ERROR: <core> [core/route.c:1167]: fix_actions(): fixing failed (code=-1) at cfg:/etc/kamailio/kamailio.cfg:701 error -1 while trying to fix configuration 0(1) INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized ======================================================SO NO WAY TO GET IT UP. Any idea on what could be the problem? I tried giving permissions to some folders in Kamailio docker container: chown kamailio:kamailio /usr/sbin/kam* chmod 755 /usr/sbin/kam* chown -R kamailio:kamailio /etc/kamailio chmod -R 755 /etc/kamailio chown -R root:kamailio /var/run chmod -R 755 /var/run chown -R kamailio:kamailio /run/kamailio chown -R 755 /run/kamailio But had no effect... and I do not know if there is any misconfiguration out there. Indeed I tried to configure it to use remote Postgresql and failed, so I came back to MYSQL as it looks somekind of default config. To Kamailio. Thank you in advance. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavors to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener información confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente y pueden estar protegidos por secreto profesional. Si usted recibe este correo electrónico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningún compromiso para el grupo Atos, salvo ratificación escrita por ambas partes. Aunque se esfuerza al máximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no será responsable de cualesquiera daños que puedan resultar de una transmisión de virus.

1 0

Runnning kamailio (docker) with remote connection with MYSQL (docker) fails on start/restart due to socket or database connection
by Nuñez, Mario 16 Feb '21

16 Feb '21

Hi, I am running docker with this: https://hub.docker.com/layers/kamailio/kamailio/5.4.3-trusty/images/sha256-… and https://hub.docker.com/layers/mysql/library/mysql/8.0.23/images/sha256-8708… I made some configurations in Kamailio container: /etc/default/kamailio RUN_KAMAILIO=yes USER=kamailio GROUP=kamailio CFGFILE=/etc/kamailio/kamailio.cfg DUMP_CORE=yes /etc/kamailio/kamailio.cfg #!define WITH_MYSQL #!define WITH_AUTH #!define WITH_USRLOCDB /etc/kamailio/kamctlrc SIP_DOMAIN=kamailio.org DBENGINE=MYSQL DBHOST=172.19.0.3 DBPORT=3306 DBNAME=kamailio DBRWUSER="kamailio" DBRWPW="kamailiorw" DBROUSER="kamailioro" DBROPW="kamailioro" DBACCESSHOST=172.19.0.5 DBROOTUSER="root" DBROOTPW="whatever" CHARSET="latin1" USERCOL="user" Then I run creation of database: /usr/sbin/kamdbctl create All was ok so I can see in MYSQL database: +------------------+------------+-----------------------+ | user | host | plugin | +------------------+------------+-----------------------+ | root | % | mysql_native_password | | kamailio | 172.19.0.3 | mysql_native_password | | kamailioro | 172.19.0.3 | mysql_native_password | | kamailio | 172.19.0.5 | mysql_native_password | | kamailioro | 172.19.0.5 | mysql_native_password | | kamailio | localhost | mysql_native_password | | kamailioro | localhost | mysql_native_password | | mysql.infoschema | localhost | caching_sha2_password | | mysql.session | localhost | caching_sha2_password | | mysql.sys | localhost | caching_sha2_password | | root | localhost | mysql_native_password | +------------------+------------+-----------------------+ At this point, if I try to restart kamailio i get an error and container will never go up again, so I had to delete it and restart the whole installation and configuration process. Log details are: ==========================================ON RESTART KAMAILIO FROM CONTAINER CONSOLE: Listening on udp: 127.0.0.1:5060 udp: 172.17.0.4:5060 tcp: 127.0.0.1:5060 tcp: 172.17.0.4:5060 Aliases: tcp: mykamailio:5060 tcp: localhost:5060 udp: mykamailio:5060 udp: localhost:5060 0(1) INFO: <core> [core/tcp_main.c:4984]: init_tcp(): using epoll_lt as the io watch method (auto detected) 0(1) INFO: rr [../outbound/api.h:52]: ob_load_api(): unable to import bind_ob - maybe module is not loaded 0(1) INFO: rr [rr_mod.c:185]: mod_init(): outbound module not available 0(1) INFO: <core> [main.c:2834]: main(): processes (at least): 33 - shm size: 67108864 - pkg size: 8388608 0(1) INFO: <core> [core/udp_server.c:154]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 0(1) INFO: <core> [core/udp_server.c:206]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 0(1) INFO: <core> [core/udp_server.c:154]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 0(1) INFO: <core> [core/udp_server.c:206]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 21(28) INFO: jsonrpcs [jsonrpcs_sock.c:443]: jsonrpc_dgram_process(): a new child 0/28 23(30) INFO: ctl [io_listener.c:214]: io_listen_loop(): io_listen_loop: using epoll_lt io watch method (config) 0(1) ALERT: <core> [main.c:774]: handle_sigs(): child process 205 exited normally, status=255 0(1) INFO: <core> [main.c:802]: handle_sigs(): terminating due to SIGCHLD 2(9) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 1(8) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 3(10) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 4(11) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 6(13) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 5(12) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 7(14) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 10(17) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 12(19) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 14(21) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 29(36) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 24(31) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 28(35) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 15(22) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 19(26) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 13(20) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 17(24) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 8(15) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 23(30) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 22(29) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 21(28) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 26(33) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 20(27) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 31(38) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 32(39) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 9(16) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 30(37) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 11(18) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 16(23) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 27(34) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 18(25) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 25(32) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 0(1) ERROR: ctl [ctl.c:390]: mod_destroy(): ERROR: ctl: could not delete unix socket /var/run/kamailio//kamailio_ctl: No such file or directory (2) 0(1) INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized ==========================================SO CONTAINER WAS DOWN, AND THEN IF I TRY TO START CONTAINER AGAIN: Listening on udp: 127.0.0.1:5060 udp: 172.17.0.4:5060 udp: 172.19.0.5:5060 tcp: 127.0.0.1:5060 tcp: 172.17.0.4:5060 tcp: 172.19.0.5:5060 Aliases: tcp: mykamailio:5060 tcp: localhost:5060 udp: mykamailio:5060 udp: localhost:5060 0(1) INFO: <core> [core/tcp_main.c:4984]: init_tcp(): using epoll_lt as the io watch method (auto detected) 0(1) INFO: rr [../outbound/api.h:52]: ob_load_api(): unable to import bind_ob - maybe module is not loaded 0(1) INFO: rr [rr_mod.c:185]: mod_init(): outbound module not available 0(1) INFO: auth [auth_mod.c:346]: mod_init(): qop set, but nonce-count (nonce_count) support disabled 0(1) INFO: <core> [main.c:2834]: main(): processes (at least): 41 - shm size: 67108864 - pkg size: 8388608 0(1) ERROR: db_mysql [km_my_con.c:163]: db_mysql_new_connection(): driver error: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) 0(1) ERROR: <core> [db.c:319]: db_do_init2(): could not add connection to the pool 0(1) ERROR: usrloc [dlist.c:852]: register_udomain(): failed to open database connection 0(1) ERROR: registrar [registrar.c:711]: domain_fixup(): failed to register domain 0(1) ERROR: <core> [core/route.c:1167]: fix_actions(): fixing failed (code=-1) at cfg:/etc/kamailio/kamailio.cfg:698 0(1) ERROR: <core> [core/rvalue.c:3869]: fix_rval_expr(): failure in cfg at line: 698 col: 22 0(1) ERROR: <core> [core/rvalue.c:3869]: fix_rval_expr(): failure in cfg at line: 698 col: 22 0(1) ERROR: <core> [core/route.c:1167]: fix_actions(): fixing failed (code=-1) at cfg:/etc/kamailio/kamailio.cfg:701 error -1 while trying to fix configuration 0(1) INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized ======================================================SO NO WAY TO GET IT UP. Any idea on what could be the problem? I tried giving permissions to some folders in Kamailio docker container: chown kamailio:kamailio /usr/sbin/kam* chmod 755 /usr/sbin/kam* chown -R kamailio:kamailio /etc/kamailio chmod -R 755 /etc/kamailio chown -R root:kamailio /var/run chmod -R 755 /var/run chown -R kamailio:kamailio /run/kamailio chown -R 755 /run/kamailio But had no effect... Thank you in advance. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavors to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener información confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente y pueden estar protegidos por secreto profesional. Si usted recibe este correo electrónico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningún compromiso para el grupo Atos, salvo ratificación escrita por ambas partes. Aunque se esfuerza al máximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no será responsable de cualesquiera daños que puedan resultar de una transmisión de virus.

1 0

Info: Kamailio presentations later today at ClueCon TGI
by Daniel-Constantin Mierla 16 Feb '21

16 Feb '21

Hello, short note to inform that later today will be 3 sessions related to Kamailio at ClueCon TGI (online event): * a workshop about basics of SIP routing with Kamailio * a presentation about DID routing with Kamailio * a presentation about outsourcing services from FreeSwitch to Kamailio The first two are done by me, the last one by Fred Posner. The event is free to attend, by participating to a video conference or watch the youtube stream -- more details at: * https://www.cluecon.com/ Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Funding: https://www.paypal.me/dcmierla

2 2

Re: [SR-Users] Advice on handling SIP trunk to a Perimeta SBC
by Björn Bylander 16 Feb '21

16 Feb '21

Hi again, I'm using Kamailio 5.3.2 by the way. Björn Bylander writes: > Hi, > > So I’m tasked with setting up a SIP trunk to a Perimeta SBC (https://www.metaswitch.com/products/perimeta-sbc). > > Apparently, > > Perimeta hides the topology of networks by rewriting or removing topology-sensitive information from SIP messages. By default, your Session Controller will make the following changes to SIP messages. > > > > The Session Controller generates new dialog identifiers (call-IDs, From tags and To tags) for each side of the call, so that it does not expose information about your core network to your access networks. > > The Session Controller strips Record-Route and Route information from the message. > > The Session Controller rewrites Contact and Via headers so that the source IP address is replaced with the local address of the outbound adjacency. > > The Session Controller replaces the IP addresses in c= lines in SDP with the addresses it has allocated for media forwarding. For more information on this, see Media addresses and gates. > > My problem is this: When the Perimeta SBC sends its first INVITE (I can't say anything about any succeeding INVITEs yet) it's added a Record-Route header with the "lr" parameter included which, as far as I can see makes Kamailio think it should use loose routing which is all well I think. But when the SBC sends an ACK for the "200 OK" from the Kamailio side it doesn't include any Route headers and I think that makes it hard for Kamailio (at least with the standard script which is basically what I'm using) to know where to relay the ACK, at least it makes the t_check_trans() call in WITHINDLG after 'is_method("ACK")' return false which makes the script ignore the ACK. > > Any thoughts or suggestions on how to handle this? > > Thanks in advance, > Björn Bylander

1 0

Kamailio v5.4.4 Released
by Daniel-Constantin Mierla 15 Feb '21

15 Feb '21

Hello, Kamailio SIP Server v5.4.4 stable release is out. This is a maintenance release of the latest stable branch, 5.4, that includes fixes since the release of v5.4.3. There is no change to database schema or configuration language structure that you have to do on previous installations of v5.4.x. Deployments running previous v5.4.x versions are strongly recommended to be upgraded to v5.4.4. For more details about version 5.4.4 (including links and guidelines to download the tarball or from GIT repository), visit: * https://www.kamailio.org/w/2021/02/kamailio-v5-4-4-released/ RPM, Debian/Ubuntu packages will be available soon as well. Many thanks to all contributing and using Kamailio! Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

1 0

Releasing Kamailio v5.4.4
by Daniel-Constantin Mierla 15 Feb '21

15 Feb '21

Hello, I am considering to release Kamailio v5.4.4 sometime next week, likely on Monday, February 15, 2020. This is the usual heads up notification to see if anyone is aware of issues not yet reported to bug tracker and if yes, do it as soon as possible to give them a chance to be fixed. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Funding: https://www.paypal.me/dcmierla

3 4

IMS-PSTN
by eyas barhouk 13 Feb '21

13 Feb '21

Hello dears I'm trying to build an IMS testbed based on kamailio and integrate it with the PSTN network, in order to do that I'm looking for AGCF,MGCF open source solution. Am I able to do the functionality of those nodes based on Kamailio,Asterisk or any other open source? thanks and regards Eyas

1 0

IMS-PSTN
by eyas37＠hotmail.com 12 Feb '21

12 Feb '21

1 0

basic help, In over my head in getting a webrtc up.
by Daniel Siemens 12 Feb '21

12 Feb '21

I am trying to get a webrtc setup going. Here is what I have I have asterisk server at 10.123.244.18. The webrtc works internally from the freepbx UCP application As well as the Raspberry phone allocation. This server doesn't have any nat on it all devices are on local / reouted networks. I have a Proxy server at 10.123.245.30 address. This server is located in AWS and has an elastic IP. On this server I have ngiinx that will load the raspberry phone up. What configuration do I need in kamailio and rtpengine to get this working. If I forward port 8089 in nginx to the /ws side on my asterisk server I can get a call to bridge but with no audio and the call end at 30 seconds when remote. It works internally fine. Likely beccuae the web browser can get to https://10.123.244.18:8089/ws ports fine. Thanks. ------------------------------------------------------------------ This email is intended solely for the use of the addressee and may contain information that is confidential, proprietary, or both. If you receive this email in error please immediately notify the sender and delete the email. ------------------------------------------------------------------

2 1

loose_route() does not find socket by name
by Juha Heinanen 12 Feb '21

12 Feb '21

I did more tests and found that loose_route() does not find socket by name given in ;sn param: Feb 12 10:40:59 lab /usr/bin/sip-proxy[16975]: WARNING: rr [loose.c:799]: rr_do_force_send_socket(): no socket found to match second RR (sip:tenantX.teams.tutpro.com:8007;transport=tls;r2=on;sn=ext_tls;lr;n1;savp=avp;pm=0) In config I have defined: listen=tls:192.x.x.x:8007 name "ext_tls" -- Juha

2 8

Kamailio Memory Leak
by Uttam Giri 11 Feb '21

11 Feb '21

Hi, We have observed increased memory utilization in Kamailio, It increases every day, even though traffic is not increased. We are using Kamailio+RTPEngine in our setup. Phone---->Kamailio+RTPEngine------>Asterisk /etc/kamailio# kamcmd mod.stats all shm Module: core { sip_msg_shm_clone(496): 542688 msg_lump_cloner(986): 178776 build_req_buf_from_sip_req(2218): 111968 xavp_new_value(116): 22240 counters_prefork_init(212): 39680 cfg_clone_str(130): 40 cfg_shmize(217): 712 main_loop(1313): 8 init_pt(107): 8 init_pt(106): 8 init_pt(105): 4592 register_timer(995): 192 init_tcp(4962): 8192 init_tcp(4956): 32768 init_tcp(4947): 8 init_tcp(4940): 8 init_tcp(4933): 8 init_tcp(4927): 8 init_tcp(4915): 8 init_avps(90): 8 init_avps(89): 8 timer_alloc(498): 48 init_dst_blacklist(438): 16384 init_dst_blacklist(430): 8 init_timer(267): 8 init_timer(266): 16384 init_timer(265): 8 init_timer(264): 8 init_timer(253): 8 init_timer(221): 8 init_timer(210): 278544 init_timer(209): 8 init_timer(197): 8 cfg_child_cb_new(829): 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 qm_shm_lock_init(1202): 8 Total: 1253464 } Module: sl { init_sl_stats_child(125): 5952 sl_startup(90): 8 init_sl_stats(110): 8 Total: 5968 } Module: siptrace { mod_init(319): 8 Total: 8 } Module: permissions { Total: 0 } Module: xlog { Total: 0 } Module: rtpengine { rtpp_function_call(2627): 1076024 shm_str_dup(779): 553016 rtpengine_hash_table_init(111): 14336 rtpengine_hash_table_init(96): 2048 rtpengine_hash_table_init(85): 1024 rtpengine_hash_table_init(76): 2048 rtpengine_hash_table_init(67): 2048 rtpengine_hash_table_init(58): 32 add_rtpengine_socks(975): 24 add_rtpengine_socks(956): 64 get_rtpp_set(870): 8 get_rtpp_set(861): 56 mod_init(1596): 8 mod_init(1589): 24 mod_init(1576): 8 mod_init(1569): 8 mod_init(1555): 16 Total: 1650792 } Module: pv { add_shvar(177): 8 add_shvar(170): 64 lock_set_alloc(66): 80 Total: 152 } Module: phonenum { Total: 0 } Module: textops { Total: 0 } Module: rtimer { Total: 0 } Module: tm { _reply_light(496): 1640 build_cell(334): 973848 relay_reply(2058): 69376 init_tm_stats_child(56): 7936 init_tmcb_lists(72): 16 init_tmcb_lists(70): 16 init_hash_table(482): 2097152 Total: 3149984 } Module: kex { pkg_proc_stats_init(79): 1488 Total: 1488 } Module: tmx { tmx_init_pretran_table(90): 256 Total: 256 } Module: utils { conf_init(552): 24 init_shmlock(134): 8 Total: 32 } Module: xhttp_prom { prom_metric_init(134): 8 Total: 8 } Module: dispatcher { ds_ht_init(89): 12288 reindex_dests(723): 768 mod_init(484): 80 ds_avl_insert(3621): 1712 pack_dest(411): 72 ds_ht_init(79): 32 ds_init_data(262): 16 ds_init_data(254): 16 mod_init(339): 8 mod_init(337): 8 ds_ping_active_init(138): 8 Total: 15008 } /etc/kamailio# kamcmd mod.stats all pkg Module: core { init_io_wait(469): 6192 init_modules(885): 16 rpc_hash_add(151): 1024 cnt_hash_add(394): 2048 add_callback(59): 168 register_select_table(458): 48 sr_wtimer_init(351): 136 cfg_new_group(79): 624 fix_sock_str(517): 1024 fix_sock_str(500): 240 add_alias(103): 96 add_alias(99): 96 init_dst_set(89): 32296 grp_hash_add(241): 512 fix_hostname(1457): 56 fix_socket_list(1666): 24 route_new_list(199): 184 fix_param(1114): 88 fix_param(1053): 312 fix_expr(554): 192 init_io_wait(516): 3224 subst_str(514): 720 mk_rval_expr2(2681): 17360 mk_elem(90): 232 mk_new_net(52): 48 tr_new(1730): 240 mk_rval_expr_v(2553): 216 yyparse(2852): 736 mk_rval_expr1(2621): 19096 mk_rval_expr_v(2540): 109152 pv_cache_add(349): 5616 pv_parse_format(1173): 4984 fix_param(1019): 2568 mk_action(118): 44416 cfg_declare(50): 3136 set_mod_param_regex(145): 88 set_mod_param_regex(134): 104 tr_table_add(1959): 360 register_module(233): 28784 register_module(216): 2808 load_module(417): 1552 sr_push_yy_state(1627): 1008 new_sock_info(348): 16 new_sock_info(339): 32 new_sock_info(327): 32 new_sock_info(304): 48 new_sock_info(299): 1200 add_alias(103): 56 add_alias(99): 64 yyparse(677): 40 yyparse(2387): 128 yyparse(658): 144 yyparse(1878): 168 get_hdr_field(116): 232 parse_headers(325): 64 subst_parser(301): 120 subst_parser(291): 1440 subst_parser(274): 640 pp_subst_add(58): 240 sr_push_yy_state(1697): 24 addstr(1445): 69072 rpc_hash_add(105): 16280 str_hash_alloc(59): 512 pv_table_add(236): 17248 pv_init_buffer(2139): 327680 pv_init_buffer(2129): 320 init_nonsip_hooks(43): 24 init_rlist(146): 40 rval_get_str(1259): 3696 route_add(124): 968 str_hash_alloc(59): 768 sr_push_yy_state(1687): 464 pp_define(1819): 568 init_counters(125): 128 cnt_hash_add(341): 27096 str_hash_alloc(59): 1280 Total: 762656 } Module: sl { sl_register_callback(514): 64 Total: 64 } Module: siptrace { mod_init(340): 384 Total: 384 } Module: permissions { get_pathname(243): 64 Total: 64 } Module: xlog { mod_init(212): 4104 xdbg_fixup_helper(498): 616 xlog_fixup_helper(533): 3720 Total: 8440 } Module: rtpengine { child_init(1964): 240 build_rtpp_socks(1791): 8 Total: 248 } Module: pv { pv_parse_xavp_name(541): 112 pv_parse_xavp_name(515): 112 tr_parse_string(2639): 120 tr_parse_string(2628): 120 tr_parse_string(2519): 104 tr_parse_string(2509): 64 tr_parse_string(2484): 64 tr_parse_string(2473): 64 add_var(65): 176 add_var(58): 344 Total: 1280 } Module: phonenum { pv_parse_phonenum_name(131): 32 sr_phonenum_add_item(99): 8 sr_phonenum_add_item(93): 304 Total: 344 } Module: textops { fixup_method(3598): 128 hname_fixup(3528): 504 Total: 632 } Module: rtimer { stm_e_param(384): 112 stm_t_param(299): 48 Total: 160 } Module: tm { Total: 0 } Module: kex { Total: 0 } Module: tmx { Total: 0 } Module: utils { Total: 0 } Module: xhttp_prom { Total: 0 } Module: dispatcher { Total: 0 } /etc/kamailio# kamailio -v version: kamailio 5.4.3 (x86_64/linux) 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_BLACKLIST, 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: unknown compiled with gcc 6.3.0 Any idea which could cause a memory leak. Does any of the module cause an issue? Thanks in Advance. Uttam

3 2

loose_route() fails on domain name
by Juha Heinanen 11 Feb '21

11 Feb '21

Using a domain name in R-R header may not be such a good idea: Feb 11 12:12:06 lab /usr/bin/sip-proxy[735]: WARNING: rr [loose.c:799] rr_do_force_send_socket(): no socket found to match second RR (sip:tenantX.teams.tutpro.com:8007;transport=tls;r2=on;pm=0;savp=avp;lr) Or is there some means to tell K, which FQDN maps to which IP address, when there are many such FQDNs? -- Juha

4 9

ds_mark_dst( ) in DISPATCHER
by alirsm 11 Feb '21

11 Feb '21

Hi, In my failover setting using Dispatcher module, I mark the GW if fails to response. OPTIONS are being sent every 30 sec: failure_route[DISPATCH_FAILOVER]{ if (t_is_canceled()) exit; if (t_check_status("500") or (t_branch_timeout() and !t_branch_replied())) { ds_mark_dst("ip"); if (ds_next_dst()) { t_set_fr(0,1000); t_on_failure("DISPATCH_FAILOVER"); route(RELAY); exit; } } } However, Kamailio still recognize it as active gw ( A.A.A.A is down, no response from OPTIONS being sent) $ sudo sercmd dispatcher.list { SET_NO: 1 SET: { SET_ID: 1 DEST: { URI: sip:A.A.A.A:5060 FLAGS: AP PRIORITY: 0 ATTRS: } DEST: { URI: sip:B.B.B.B:5060 FLAGS: AP PRIORITY: 0 ATTRS: } } } Any help would be appreciated. AL

1 0

R-R to MS Teams Proxy
by Juha Heinanen 11 Feb '21

11 Feb '21

When request is sent from Kamailio to MS Teams SIP Proxy, the top R-R URI needs to contain FQDN of Kamailio SIP proxy instead of its IP address. Document https://skalatan.de/de/blog/kamailio-sbc-teams suggest to replace record_route(); call with record_route_preset("SBC-DNS-DOMAIN:5061;transport=tls", "SBC-IP-ADDR:5060"); That works only in a very simple case where the request came in over UDP or TCP and SIP Proxy has only one listening address, i.e., SBC-IP-ADDR. One way to solve the problem might be a new r_r function that would take FQDN of the top R-R URI as argument or introduction of a pv from where the current record_route() function would take the FQDN if it has been set. Any comments or other solutions? -- Juha

6 19

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