- sr-users - kamailio.org

Use of interface name or listening socket name as DMQ server_socket
by Ben Kaufman 10 Jun '22

10 Jun '22

Kamailio allows the use of an interface name (eth0 for example), as the identifier for the listen directive. Additionally it allows assignment of a name to be used as an identifier. This can be used, as indicated in the documentation: A unique name can be set for sockets to simplify the selection of the socket for sending out. For example, the rr and path modules can use the socket name to advertise it in header URI parameter and use it as a shortcut to select the corresponding socket for routing subsequent requests. I'm wondering if there is a way to get allow either of these parameters to be used to define DMQ's server_socket parameter. This would be useful in containerization situations where the local IP address is assigned dynamically. Here's what I'm attempting: #!KAMAILIO loadmodule "tm" loadmodule "sl" loadmodule "dmq" loadmodule "textops" listen=udp:eth0:5060 name "sip5060" listen=udp:eth0:5090 name "sip5090" modparam("dmq", "server_address", "sip:dmq_quicktest:5090") modparam("dmq", "notification_address", "sip:dmq-bus:5090") modparam("dmq", "server_socket", "sip5090" ) ## Above line doesn't work, neither does the line below: #modparam("dmq", "server_socket", "udp:eth0:5090" ) modparam("dmq", "multi_notify", 1) modparam("dmq", "num_workers", 3) modparam("dmq", "ping_interval", 30) request_route { exit; } I get the following error during startup: 0(1) ERROR: dmq [dmq.c:241]: mod_init(): server_uri is not a socket the proxy is listening on Thoughts? I realize that I can configure and pass static networking with the containers, but I'm looking for a way to have this set on the fly - especially when testing, etc. Ben Kaufman

2 1

SIP trunk challange
by Mihai 10 Jun '22

10 Jun '22

Hello ! I have this issue with the telco provider they give the sip trunk on a private conection with private ips, the problem is that i am trying to relocate the sip trunk in remote server and I've tried though basic networking/tunnels/vpn and no go; their sbc is dropping requests and rejects if they are more via headers, they force me to use that conection and the ip allocated. The challenge is how to this is in kamailio, basically i just want to transport the trunk (similiar to a reverse proxy for web) to its new destination and from there handle everything. Any hints on how to achieve this?

2 1

Kamailio vs FreeSWITCH as SBC
by Unai Rodriguez 09 Jun '22

09 Jun '22

Dear List, I’m looking at using Kamailio as SBC. This would replace our current FreeSWITCH-based SBCs. What are your thoughts on this move? Would there be any known reasons why Kamailio would be superior to FreeSWITCH as an SBC? Thank you so much Unai Rodriguez

3 3

t_drop_replies can't be used on a route?
by David Villasmil 09 Jun '22

09 Jun '22

Hello guys, I have a failure route which calls another route, and on this route I need to t_drop_replies(); But i'm getting: [core/cfg.y:3510]: yyerror_at(): parse error in config file /etc/kamailio/include/relay_routes.cfg, line 143, column 20: Command cannot be used in the block Any way to fix this without me having to use it in the failure_route? Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337

1 0

remove header in async processing (e.g. by http_async_client)
by Henning Westerholt 09 Jun '22

09 Jun '22

Hello, I'd like to remove headers during async processing e.g. in a route called from http_async_client(..). The usual textops functions are not working here. Adding headers could be done using something like rtjson, but it do not offer a remove header function. I could of course loop the request locally, but this is not that "nice". Any other suggestions for this case? Or just the rtjson module needs some extensions? Thank you, Henning -- Henning Westerholt - https://skalatan.de/blog/ Kamailio services - https://gilawa.com<https://gilawa.com/>

1 1

Siremis startup helper service for systemd
by Joseph Goettgens 09 Jun '22

09 Jun '22

Hi, I had some difficulties getting Siremis 5.3 to run under Debian 11 Bullseye. It turned out that the problem was the creation of the Siremis socket: <UnixSockLocal name="unixsocklocal" address="/run/siremis/siremis_rpc.sock" timeout="3.0"/> There is a warning in siremisJRCommands.xml that points out that systemd has to be reconfigured as sockets in /tmp are no longer shared (PrivateTmp setting). By the same token, /run/siremis/siremis_rpc.sock cannot be created as the httpd server is not allowed to write to /run, i.e. it can neither create the socket nor the siremis directory. The permanent creation of the siremis directory with suitable access rights is also not possible, since /run is mounted as tmpfs in the default configuration. At least the directory has to be created at boot time, which can be done with a small helper service. This is working for me (siremis-helper.service): [Unit] Description=Siremis Helper Service After=network.target [Service] Type=oneshot ExecStartPre=/usr/bin/mkdir /var/run/siremis ExecStart=/usr/bin/chown www-data:www-data /var/run/siremis [Install] WantedBy=multi-user.target It is enabled the usual way with systemctl "systemctl start --now siremis-helper". Siremis now works with jsonrpc commands and the procedure would mean that installing Siremis on a newer Debian system would definitely require some attention. Does anyone have any objections to the above procedure?

1 0

Re-establishment of a closed TCP connection
by Vitalii Krutsitskyi 09 Jun '22

09 Jun '22

Hello General overview of the infrastructure: Client (Cisco Hardware) ---> AWS NLB ---> Kamailio Instances The client has a time limit for the opened TCP connections - 10 minutes. This is a hardcoded value that can't not be changed. Regardless of the traffic that flows through the connection, it is closed after 10 minutes. Problem: in case of long-running calls above 10 minutes it is not possible for Kamailio to send back SIP traffic back to the client using the original TCP connection. The client has been asked to either increase the time limit or send SIP reinvites - none of that is possible due to some client's infrastructure limitations. Question: is it possible to force Kamailio to open a new TCP connection and associate it with the call? Client has a 5060 port always opened which can accept incoming connections.

3 2

ipops dns_query not working using Kemi
by Thomas de Rooij | CM.com 09 Jun '22

09 Jun '22

Hi all, We are trying to do a DNS query using Kemi: KSR.ipops.dns_query(domain, "xyz") The result is always -3. This is returned here: https://github.com/kamailio/kamailio/blob/5.5.4/src/modules/ipops/ipops_pv.… It seems weird to me that the error code is returned because the same non-Kemi code works just fine. Could it be related to this issue: https://github.com/kamailio/kamailio/issues/2052 Thanks. Kind regards, Thomas

3 2

remove headers with less than 5 characters with textops
by Patrick Karton 07 Jun '22

07 Jun '22

Hello im trying to textops module to remove headers with name length less than 5 characters with regular expression but it seems impossible or the module does not handle $ char remove_hf_re("^.{1,5}$")

3 3

Siremis JSONRPC problem on Bullseye
by Joseph Goettgens 07 Jun '22

07 Jun '22

Hi, I seem to have a problem setting up Siremis 5.3 on a Debian 11 box using the Kamailio 5.6.0 release (installed from repo). When I enter something like core.uptime into the JSONRPC Command Panel, I get a "System Internal Error" alert. The Apache error log then says: [Mon Jun 06 10:48:41.459377 2022] [php7:notice] [pid 22322] [client 192.168.xxx.xxx:45030] socket bind failed: No such file or directory, referer: http://deb11srv1-kamailio/siremis/sipadmin/jrcmds The path siremis/sipadmin/jrcmds obviously does not seem to exist and I assume that one needs some internal adjustments for some paths. As far as the socket is concerned, siremis/modules/sipadmin/service/siremisJRCommands.xml has the definition: UnixSockRemote name="unixsockremote" address="/var/run/kamailio/kamailio_rpc.sock" timeout="3.0"/> and the corresponding definition in /etc/kamailio/kamailio.cfg is: modparam("jsonrpcs", "dgram_socket", "/var/run/kamailio/kamailio_rpc.sock") modparam("jsonrpcs", "dgram_mode", 0666) which looks fine to me. I also checked for the existence of the socket and its access rights. Any suggestions?

2 1

t_cancel_callid - doesn't insert Reason header, if called from branch 0
by Pavel Veselovsky 07 Jun '22

07 Jun '22

Hallo all, I defined branch_failure routing block via t_on_branch_failure() In the branch_failure route, in case of "408 Request timeout" I am sending CANCEL with reason "t_cancel_callid("$ci", "$cs", "22", "408")". If the t_cancel_callid("$ci", "$cs", "22", "408") is called in branch_failure for branch idx 0, the CANCEL is sent, but Reason header is missing there. Why? (I expect that t_cancel_callid() should insert Reason header regardless of branch it is called from) If the t_cancel_callid is called in branch idx !=0, the CANCEL contains Reason header with cause as expected. Thanks for clarification of this behavior, Pavel. P.S. code snipset: event_route[tm:branch-failure:primary] { if ($T(reply_code) == "408") { if ($avp(branch_idx) == $T_branch_idx) { if (t_cancel_callid("$ci", "$cs", "22", "408")) { xlog("L_INFO", "CANCEL sent ci:$ci, cs:$cs 408"); } else { xlog("L_INFO", "CANCEL not sent ... ci:$ci, cs:$cs 408"); } $var(_palotmp_) = "sip:" + $avp(replaced_cfnry_target_number) + "@" + $dd + ":" + $dp + ";user=phone"; append_branch($var(_palotmp_),"1.0"); t_relay(); return; } } }

3 3

Fatal Python error: failed releasing import lock after fork
by Nigel Daniels 06 Jun '22

06 Jun '22

The logs appear as follows: Fatal Python error: failed releasing import lock after fork Current thread 0x 7(13) DEBUG: <core> [core/utils/sruid.c:121]: sruid_init(): root for sruid is [srid-62930e67-d-] (0 / 16) kamailio | 00007fe8fb8a4180 (most recent call first): kamailio | <no Python frame> kamailio | 7(13) DEBUG: <core> [core/sr_module.c:875]: init_mod_child(): idx 7 rank -2: tm [ctl handler] kamailio | 7(13) DEBUG: tm [callid.c:136]: child_init_callid(): callid: '06d932e436730fa0-13(a)10.10.0.4' kamailio | 7(13) DEBUG: <core> [core/sr_module.c:875]: init_mod_child(): idx 7 rank -2: tmx [ctl handler] kamailio | 7(13) DEBUG: tmx [tmx_mod.c:262]: child_init(): rank is (-2) kamailio | 7(13) DEBUG: <core> [core/sr_module.c:875]: init_mod_child(): idx 7 rank -2: sl [ctl handler] kamailio | 7(13) DEBUG: <core> [core/sr_module.c:875]: init_mod_child(): idx 7 rank -2: ctl [ctl handler] kamailio | 7(13) DEBUG: <core> [core/sr_module.c:875]: init_mod_child(): idx 7 rank -2: debugger [ctl handler] kamailio | 7(13) DEBUG: debugger [debugger_mod.c:224]: child_init(): rank is (-2) kamailio | 7(13) DEBUG: <core> [core/sr_module.c:875]: init_mod_child(): idx 7 rank -2: app_python3 [ctl handler] kamailio | 7(13) DEBUG: app_python3 [apy_kemi.c:234]: sr_apy_kemi_exec_func_ex(): execution of method: .info kamailio | 7(13) DEBUG: app_python3 [apy_kemi.c:266]: sr_apy_kemi_exec_func_ex(): param[1] for: info is str: ===== kamailio.child_init(-2) kamailio | kamailio | 7(13) INFO: <core> [core/kemi.c:106]: sr_kemi_core_info(): ===== kamailio.child_init(-2) kamailio | 7(13) DEBUG: ctl [ctl.c:329]: mod_child(): ctl: mod_child(0), fork_process=0, csl=0x556774893180 kamailio | 7(13) DEBUG: ctl [ctl.c:336]: mod_child(): ctl: 0 io_listen_loop(1, 0x556774893180) kamailio | 7(13) INFO: ctl [io_listener.c:213]: io_listen_loop(): io_listen_loop: using epoll_lt io watch method (config) kamailio | 7(13) DEBUG: ctl [io_listener.c:245]: io_listen_loop(): io_listen_loop: adding socket 8, type 2, transport 3 (/var/run/kamailio//kamailio_ctl) kamailio | 7(13) DEBUG: ctl [../../core/io_wait.h:374]: io_watch_add(): processing io_watch_add(0x7fe8f9aef380, 8, 2, 0x556774893180) - fd_no=0 Running python 3.8.10 using the suggested. # ----------------- setting module-specific parameters --------------- # ----- tm params ----- # auto-discard branches from previous serial forking leg modparam("tm", "failure_reply_mode", 3) # default retransmission timeout: 30sec modparam("tm", "fr_timer", 30000) # default invite retransmission timeout after 1xx: 120sec modparam("tm", "fr_inv_timer", 120000) # ----- debugger params ----- modparam("debugger", "cfgtrace", 1) ####### Routing Logic ######## modparam("app_python3", "load", "/opt/kamailio/etc/kamailio.py") cfgengine "python"a import sys import KSR as KSR def dumpObj(obj): for attr in dir(obj): KSR.info("obj.%s = %s\n" % (attr, getattr(obj, attr))) def mod_init(): KSR.info("===== from Python mod init\n") dumpObj(KSR) return kamailio() class kamailio: def __init__(self): KSR.info('===== kamailio.__init__\n') def child_init(self, rank): KSR.info('===== kamailio.child_init(%d)\n' % rank) return 0 def ksr_request_route(self, msg): KSR.info("===== request - from kamailio python script\n") KSR.setdsturi("sip:alice@127.0.0.1:5080") KSR.tm.t_on_branch("ksr_branch_route_one") KSR.tm.t_on_reply("ksr_onreply_route_one") KSR.tm.t_on_failure("ksr_failure_route_one") KSR.sl.send_reply(100, "Trying") if KSR.tm.t_relay() < 0 : KSR.sl.send_reply(500, "Server error") return 1 def ksr_reply_route(self, msg): KSR.info("===== response - from kamailio python script\n") return 1 def ksr_onsend_route(self, msg): KSR.info("===== onsend route - from kamailio python script\n") return 1 def ksr_branch_route_one(self, msg): KSR.info("===== branch route - from kamailio python script\n") return 1 def ksr_onreply_route_one(self, msg): KSR.info("===== onreply route - from kamailio python script\n") return 1 def ksr_failure_route_one(self, msg): KSR.info("===== failure route - from kamailio python script\n") return 1 Any help is appreciated, thanks. -- - Nigel

2 3

SNMP, export concurrent calls count
by ZZ Wave 30 May '22

30 May '22

Hello. Debian 10, Kamailio 5.2.1 I want to monitor concurrent calls in/out per every trunk connected to this proxy (it's done with dialog profiles), and export this to Zabbix. But I can't find in snmpstats documentation how to export user-defined variables. Help me please. Maybe SNMP isn't the best solution for that...

2 1

Centos kamailio.repo file is not updated
by Patrick Wakano 30 May '22

30 May '22

Hello ist, I've noticed some of the latest releases do not have their repo mentioned in the https://rpm.kamailio.org/centos/kamailio.repo The repos are there, it is just the kamailio.repo file missing some of the newer versions like 5.4.7, 4.5.8, 5.5.4, 5.6.0... Cheers, Patrick

3 3

Fedora RPMs
by Tim Anderson 30 May '22

30 May '22

Hi, I can't find any RPMs for Fedora 35 or 36. Have they moved somewhere other than rpm.kamailio.org? Regards, Tim

3 2

DNS Failover try next destination on receiving code other than 503
by Patrick Karton 30 May '22

30 May '22

Hello, im using DNS Failover and everything works well except i would like to try other resolved ips when i receive a 408 from the previous ones As far as i know only a received 503 will trigger next destinations and there is no config parameters in tm module to handle that behaviour. so how can i implement it ? set a failure route before relay and just call t_relay() after again ? also is there a way in failure route to know how many destinations are left to exit failure route. Thanks for help.

2 3

KEMI Python Syntax
by Olivier Roy 30 May '22

30 May '22

Hello, I am writing some Kamailio scripts using app_python3. I understand that the KSR module is automatically generated by Kamailio. So when I import KSR from KSR I don't get any syntax from my IDE since it doesn't know where KSR is. My question: is there a way to generate a KSR.py file that can be used for autocompletion and syntax highlighting? Thanks. Olivier

2 1

get and store destination ip address and port that the request will be sent to
by Patrick Karton 30 May '22

30 May '22

Hello is there a way or pseudo var to get ip address & port that the request will be sent to and save it in to another variable. i want a way to get it to store it. im not able to save it with to_ip and to_port of the onsend_route. TThanks.

2 1

Find Values in User part of Diversion URI
by Lewis Hutchinson 30 May '22

30 May '22

Sorry if this is a super basic ask but I can't seem to work it out, I have got a work around but for my own sanity wanted to post the question on here. In Kamailio Native 5.5.2 I want to be able to look into this field $(di{uri.user}) and "find" or see if it "contains" a value i.e Diversion: "TEST" sip:112233445566@xxx.xxx.xxx.xxx;user=phone; find 234 or contains 234 I know how to do this in in KEMI Python but for the life of me cant get my head around it in Native. 2ndly is there an opposite to {s.numeric} Removes all non-numeric parts of string. I want the ability to strip all numeric parts. Keep us the good work. Lewis

3 4

TLS connection failure. Not sure if system behavior is correct.
by Володимир Іванець 27 May '22

27 May '22

Hello all! My test Kamailio setup (now updated to version 5.5.4) that was working with MS Teams some time ago, now stopped :) I was wondering if someone could tell me if the current behavior is correct or if there is a problem? Here is a screenshot of the packet capture: [image: image.png] I thought that after MS Teams side sent Change Cipher Spec request, Kamailio should respond with ACK. But instead it just starts sending data (I believe it sends OPTIONS request. sipdump module captured it). Is this correct? There seems to be no issues in the Kamailio debug log: May 20 15:29:05 server kamailio[28961]: 14(28975) DEBUG: <core> [core/io_wait.h:782]: io_watch_chg(): DBG: io_watch_chg (0xae9560, 24, 0x1, 0xffffffff) fd_no=20 called May 20 15:29:05 server kamailio[28961]: 14(28975) DEBUG: <core> [core/io_wait.h:600]: io_watch_del(): DBG: io_watch_del (0xae9560, 25, -1, 0x0) fd_no=20 called May 20 15:29:05 server kamailio[28961]: 14(28975) DEBUG: <core> [core/tcp_main.c:4471]: handle_tcpconn_ev(): sending to child, events 1 May 20 15:29:05 server kamailio[28961]: 14(28975) DEBUG: <core> [core/tcp_main.c:4144]: send2child(): selected tcp worker idx:1 proc:11 pid:28972 for activity on [tls:172.16.30.206:5062], 0x7fad6a70f6c8 May 20 15:29:05 server kamailio[28961]: 11(28972) DEBUG: <core> [core/tcp_read.c:1737]: handle_io(): received n=8 con=0x7fad6a70f6c8, fd=6 May 20 15:29:05 server kamailio[28961]: 11(28972) DEBUG: tls [tls_domain.c:1208]: tls_lookup_private_key(): Private key lookup for SSL_CTX-0x7fad6a5e1eb8: (nil) May 20 15:29:05 server kamailio[28961]: 11(28972) DEBUG: <core> [core/tcp_main.c:2720]: tcpconn_do_send(): sending... May 20 15:29:05 server kamailio[28961]: 11(28972) DEBUG: <core> [core/tcp_main.c:2753]: tcpconn_do_send(): after real write: c= 0x7fad6a70f6c8 n=2279 fd=6 May 20 15:29:05 server kamailio[28961]: 11(28972) DEBUG: <core> [core/tcp_main.c:2754]: tcpconn_do_send(): buf= May 20 15:29:05 server kamailio[28961]: 7 May 20 15:29:05 server kamailio[28961]: 11(28972) DEBUG: <core> [core/io_wait.h:375]: io_watch_add(): processing io_watch_add(0xb555c0, 6, 2, 0x7fad6a70f6c8) - fd_no=1 May 20 15:29:05 server kamailio[28961]: 11(28972) DEBUG: tls [tls_domain.c:1208]: tls_lookup_private_key(): Private key lookup for SSL_CTX-0x7fad6a5e1eb8: (nil) May 20 15:29:05 server kamailio[28961]: 11(28972) DEBUG: tls [tls_domain.c:790]: sr_ssl_ctx_info_callback(): SSL handshake done May 20 15:29:05 server kamailio[28961]: 11(28972) DEBUG: tls [tls_domain.c:794]: sr_ssl_ctx_info_callback(): SSL disable renegotiation May 20 15:29:05 server kamailio[28961]: 11(28972) DEBUG: tls [tls_server.c:542]: tls_connect(): TLS connect successful May 20 15:29:05 server kamailio[28961]: 11(28972) DEBUG: tls [tls_server.c:549]: tls_connect(): tls_connect: new connection to 52.114.132.46:5061 using TLSv1/SSLv3 ECDHE-RSA-AES256-GCM-SHA384 256 May 20 15:29:05 server kamailio[28961]: 11(28972) DEBUG: tls [tls_server.c:552]: tls_connect(): tls_connect: sending socket: 172.16.30.206:0 May 20 15:29:05 server kamailio[28961]: 11(28972) DEBUG: tls [tls_server.c:418]: tls_dump_cert_info(): tls_connect: server certificate subject:/CN=sip.pstnhub.microsoft.com May 20 15:29:05 server kamailio[28961]: 11(28972) DEBUG: tls [tls_server.c:422]: tls_dump_cert_info(): tls_connect: server certificate issuer:/C=US/O=Microsoft Corporation/CN=Microsoft RSA TLS CA 01 May 20 15:29:05 server kamailio[28961]: 11(28972) DEBUG: <core> [core/tcp_main.c:2720]: tcpconn_do_send(): sending... May 20 15:29:05 server kamailio[28961]: 11(28972) DEBUG: <core> [core/tcp_main.c:2753]: tcpconn_do_send(): after real write: c= 0x7fad6a70f6c8 n=509 fd=6 May 20 15:29:05 server kamailio[28961]: 11(28972) DEBUG: <core> [core/tcp_main.c:2754]: tcpconn_do_send(): buf= May 20 15:29:05 server kamailio[28961]: ▒4▒▒▒▒.▒2T$-▒▒ o▒w)▒(▒▒^▒D▒U{xn9▒' ▒&▒t▒▒)▒▒?▒d▒=g▒▒?▒▒▒4/▒▒▒▒-R+▒tR▒H,▒o▒D2r ▒5Q?m▒▒9▒▒#▒O▒▒▒\eϣ▒݄"▒z=▒U▒? May 20 15:29:05 server kamailio[28961]: 14(28975) DEBUG: <core> [core/io_wait.h:600]: io_watch_del(): DBG: io_watch_del (0xae9560, 24, -1, 0x0) fd_no=19 called May 20 15:29:05 server kamailio[28961]: 14(28975) DEBUG: <core> [core/tcp_main.c:4471]: handle_tcpconn_ev(): sending to child, events 1 May 20 15:29:05 server kamailio[28961]: 14(28975) DEBUG: <core> [core/tcp_main.c:4144]: send2child(): selected tcp worker idx:2 proc:12 pid:28973 for activity on [tls:172.16.30.206:5062], 0x7fad6a6f25a0 May 20 15:29:05 server kamailio[28961]: 12(28973) DEBUG: <core> [core/tcp_read.c:1737]: handle_io(): received n=8 con=0x7fad6a6f25a0, fd=6 May 20 15:29:05 server kamailio[28961]: 12(28973) DEBUG: tls [tls_domain.c:1208]: tls_lookup_private_key(): Private key lookup for SSL_CTX-0x7fad6a5e1eb8: (nil) May 20 15:29:05 server kamailio[28961]: 11(28972) DEBUG: <core> [core/tcp_read.c:304]: tcp_read_data(): EOF on connection 0x7fad6a70f6c8 (state: 0, flags: 18) - FD 6, bytes 0, rd-flags 10000 ([52.114.132.46]:5061 -> [52.114.132.46]:0)11(28972) DEBUG: <coreTCP closed event creation triggered (reason: 0) May 20 15:29:05 server kamailio[28961]: 11(28972) DEBUG: <core> [core/tcp_read.c:192]: tcp_emit_closed_event(): no callback registering for handling TCP closed event May 20 15:29:05 server kamailio[28961]: 11(28972) DEBUG: <core> [core/tcp_read.c:1503]: tcp_read_req(): EOF May 20 15:29:05 server kamailio[28961]: 11(28972) DEBUG: <core> [core/io_wait.h:600]: io_watch_del(): DBG: io_watch_del (0xb555c0, 6, -1, 0x10) fd_no=2 called May 20 15:29:05 server kamailio[28961]: 11(28972) DEBUG: <core> [core/tcp_read.c:1878]: handle_io(): removing from list 0x7fad6a70f6c8 id 2 fd 6, state 2, flags 18, main fd 25, refcnt 2 ([52.114.132.46]:5061 -> [52.114.132.46]:0) May 20 15:29:05 server kamailio[28961]: 11(28972) DEBUG: <core> [core/tcp_read.c:1659]: release_tcpconn(): releasing con 0x7fad6a70f6c8, state -1, fd=6, id=2 ([52.114.132.46]:5061 -> [52.114.132.46]:0) May 20 15:29:05 server kamailio[28961]: 11(28972) DEBUG: <core> [core/tcp_read.c:1660]: release_tcpconn(): extra_data 0x7fad6a70f008 May 20 15:29:05 server kamailio[28961]: 14(28975) DEBUG: <core> [core/tcp_main.c:3574]: handle_tcp_child(): reader response= 7fad6a70f6c8, -1 from 1 May 20 15:29:05 server kamailio[28961]: 14(28975) DEBUG: tls [tls_server.c:729]: tls_h_tcpconn_close_f(): Closing SSL connection 0x7fad6a70f008 Thank you!

1 1

Debian: Kamailio: -> FIN - SYN -> on new port
by Kevin Browne 26 May '22

26 May '22

Hi, am looking for some specific Kamailio help i cant seem to find anywhere ( # running Kamailio on Debian/buster ... ## after receipt of tcp FIN, port is closed. when signaling is required again from Kamailio side. Kam is attempting SYN on FINd (closed) port. this is rejected RST. How to change SYN to re-establish tcp on new ephemeral port? ## another description, same problem: FIN received from (external) cisco (call owner) due to port recycling, not to keep port open after x minutes. everything is as expected re ACKs and such. When Kam wants to send REFER to cisco after the FIN, tcp attempts a SYN (as we'd expect) but sends SYN on old closed port. ## Where to change this Kam/OS/other is where i'm attempting to identify, then figure how to change. Thank you.

2 1

TOPOS + RE-INVITE problem - Contact IP not updated
by c c 24 May '22

24 May '22

It seems that TOPOS is not working properly on RE-INVITE and stop masking IP and contact on some RE-INVITE. When a RE-INVITE is send with Kamailio IP as Request-URI TOPOS is not operating. Note : we are using the HTABLE trick to rewrite $ru and match the call but we would need to have TOPOS re-evaluating the dialog once done. We use a standard configuration with 2 modifications. 1. in route[DISPATCH] to set the HTABLE if(is_method("INVITE")) { $sht(ct=>$ci::$ft) = $sel(contact.uri); } 1. in route[WITHINDLG] to find the call if R-URI = myself if(has_totag() && uri==myself) { if($sht(ct=>$ci::$ft) != $null && $T_reply_code > 400) $shtex(ct=>$ci::$ft) = 10 ; if($sht(ct=>$ci::$tt) != $null) { $ru = $sht(ct=>$ci::$tt); if (is_method("BYE")) $shtex(ct=>$ci::$tt) = 10 ; route(RELAY); } } As you can see in the PCAP the RE-INVITE goes directly to calling stating with the Contact not updated and the 200 OK is also sent to called party with wrong Contact info too. [ https://github.com/kamailio/kamailio/files/8730489/topos-issue.zip ] This behavior breaks the BYE procedure. Any advice ? Chris

2 1

Load balancer and consult transfer
by Anh Cao 24 May '22

24 May '22

Hi all, I'm building an simple PBX with 1 Kamailio as load balancer for several Asterisk servers. My issue is if an extension is in-call on Asterisk#1 wants to consult transfer to another number, it makes another call and Kamailio forward this new call to another Asterisk and cause call tranfer will fail. Does anyone here have tips or sugestions to resolve this? Thanks in advance for your help. Best regards

3 3

Kamailio v5.6.0 Released - new major version is out
by Daniel-Constantin Mierla 23 May '22

23 May '22

Kamailio v5.6.0 is out – it comes with 7 new modules and a considerable set of improvements touching again more than 90 existing modules. You can read detailed release notes at: * https://www.kamailio.org/w/kamailio-v5-6-0-release-notes/ Many thanks to all developers and community members that made possible this release. v5.6.0 brings more flexibility and optimizations across many components, plenty of new variables and transformations, load balancer enhancements, generic iterators for SIP headers and body lines, alternative http client, NATS PubSub connector, improvements to STIR/SHAKEN, IMS/VoLTE, rtpengine and tls as well as more functions exported to KEMI interface ... just to list only a few here. Enjoy Kamailio v5.5.0! Thank you for flying Kamailio! Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - Online: June 20-23, 2022 * https://www.asipto.com/sw/kamailio-advanced-training-online/

4 3

Releasing Kamailio v5.6.0
by Daniel-Constantin Mierla 23 May '22

23 May '22

Hello, with some effort directed lately to convert the wiki content to markdown files and host them on github, it's time to now to nail down the path to release nest major release for Kamailio, respectively v5.6.0. What's new in this major release as well as upgrade guidelines have to be built, but I hope to be done in time to release Kamailio v5.6.0 either on Monday, June 23, 2022 or on Wednesday, June 25, 2022. Should anyone consider a different release planning, let's discuss it. If anyone wants to help with them, the content has to be added to the github wiki repository: * https://github.com/kamailio/kamailio-wiki If not there, new files have to be created and linked from the main page. The wiki is built with mkdocs into html and made available for browsing at: * https://kamailio.org/wikidocs/ Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - Online: June 20-23, 2022 * https://www.asipto.com/sw/kamailio-advanced-training-online/

2 3

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