- sr-users - kamailio.org

302 Handling issue in failure route
by Devang Dhandhalya 05 Jul '23

05 Jul '23

Hello All I am handling 302 response in the failure route and when receiving 302 response in kamailio, it's not going into the failure route , kamailio just executing the onreply route when 302 response are received. A few days ago the same code with failure route worked but now it does not. i dont know why kamailio is not executing a failure route from where we can redirect calls to another server. code snippet route[RELAY]{ t_on_reply("MANAGE_REPLY"); t_on_failure("MANAGE_FAILURE"); t_on_branch("MANAGE_BRANCH"); if (!t_relay()) { sl_reply_error(); } exit; } failure_route[MANAGE_FAILURE] { if (t_is_canceled()) { exit; } if (t_check_status("302")){ get_redirects("*"); $ru= $T_rpl($sel(contact.uri)); route(RELAY); } } kamailio version : 5.6.4 Please suggest if I am doing anything wrong. -- Regards, *Devang Dhandhalya* -- *Disclaimer* In addition to generic Disclaimer which you have agreed on our website, any views or opinions presented in this email are solely those of the originator and do not necessarily represent those of the Company or its sister concerns. Any liability (in negligence, contract or otherwise) arising from any third party taking any action, or refraining from taking any action on the basis of any of the information contained in this email is hereby excluded. *Confidentiality* This communication (including any attachment/s) is intended only for the use of the addressee(s) and contains information that is PRIVILEGED AND CONFIDENTIAL. Unauthorized reading, dissemination, distribution, or copying of this communication is prohibited. Please inform originator if you have received it in error. *Caution for viruses, malware etc.* This communication, including any attachments, may not be free of viruses, trojans, similar or new contaminants/malware, interceptions or interference, and may not be compatible with your systems. You shall carry out virus/malware scanning on your own before opening any attachment to this e-mail. The sender of this e-mail and Company including its sister concerns shall not be liable for any damage that may incur to you as a result of viruses, incompleteness of this message, a delay in receipt of this message or any other computer problems.

3 3

SL absorbed ACK is counted as dropped by core.drop_requests
by Kaufman 03 Jul '23

03 Jul '23

Just checking to see if this is the designed behavior. The SL module will attempt to match ACKs for stateless replies and handle them (absorb them?). The question I have is that it looks as though this ACK gets counted as dropped by the core.drop_requests from the KEX module. Tested using this config: #!KAMAILIO loadmodule "pv" loadmodule "sl" loadmodule "xlog" loadmodule "kex" loadmodule "corex" loadmodule "ctl" modparam("sl", "bind_tm", 0) route { xinfo("[$ci] $rm Request. Src:[$si:$sp] RURI:[$ru] To:[$tu] From:[$fu]\n"); sl_send_reply("404", "Not Found"); } event_route[sl:filtered-ack] { xnotice("sl:filtered-ack ACK [$ci] to local reply absorbed\n"); } Then validate by kamcmd stats.fetch core:drop_requests Is this the designed and "correct" behavior? Kaufman

3 4

Kamailio v5.7.1 Released
by Daniel-Constantin Mierla 28 Jun '23

28 Jun '23

Hello, Kamailio SIP Server v5.7.1 stable release is out. This is a maintenance release of the latest stable branch, 5.7, that includes fixes since the release of v5.7.0. There is no change to database schema or configuration language structure that you have to do on previous installations of v5.7.x. Deployments running previous v5.7.x versions are strongly recommended to be upgraded to v5.7.1. For more details about version 5.7.1 (including links and guidelines to download the tarball or from GIT repository), visit: * https://www.kamailio.org/w/2023/06/kamailio-v5-7-1-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 Kamailio World Conference - www.kamailioworld.com

1 0

Forward Registration
by nutxase 28 Jun '23

28 Jun '23

Hi All I have setup kamailio using websockets(wss) i am trying to forward any registration that comes to kamailio to go to asterisk, so in theory kamailio is a registration proxy i have set rewritehostport("xxx.xxx.xxx[:5080](http://node3.sipalto.com:5080)"); the registration forwards fine but the contact on asterisk side shows as sip:xxx:kamailioip.xxxx.invalid so therefore asterisk sees the sip peer as offline what am i missing :( Sent with [Proton Mail](https://proton.me/) secure email.

1 0

Releasing v5.7.1
by Daniel-Constantin Mierla 28 Jun '23

28 Jun '23

Hello, I am considering to release Kamailio v5.7.1 (out of branch 5.7) this week (likely on Wednesday or Thursday, Jun 28/29, 2023). If anyone is aware of issues not yet on the bug tracker, report them there asap in order to have a better chance to be fixed. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - www.kamailioworld.com

1 1

Matching the From Username in LCR rule table
by harneet singh 27 Jun '23

27 Jun '23

Hi Experts, We wished to used the LCR Module to be able to select the Gateway(s) to send the calls to based on the From(Caller) Username. Based on the LCR Documentation, the usage of other fields like request URI or prefix etc is pretty clear. But for the From Usename I am having certain trouble understanding the same. It refers to some mtree. Excerpt below: "A gateway matches a request if user part of Request-URI matches "prefix", caller URI matches "from_uri" pattern,* caller URI userpart matches mtree with "mt_value"*, and callee URI matches "request_uri" pattern in a tuple that is associated with the gateway." Can someone explain/ share a sample lcr_rule table entries for the From Username that can be matched against the incoming sip message for gw selection? Do we need to manually create an mtree by the name "*lcr*". Asking based on the below section in LCR documentation? Any pointers are highly appreciated. 3.35. mtree (string) Name of mtree to which load_gws() matches caller URI userpart. *Default value is "lcr".* Regards, Harneet Singh -- "Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth" - Sir Arthur Conan Doyle

2 3

uac_replace() and uac_restore debug help
by Duarte Rocha 24 Jun '23

24 Jun '23

Hello, I'm currently experiencing some odd behaviours when using these functions and I need some help debugging to find the root of the issue. I receive a call from a client and do some changes to the To and From header using auto mode with password. Encrypted info goes on the Record-Route header parameters (vsf\vst) normally. 1 - On subsequent requests sent by the originating client, domains on To and From header are different from the ones sent in the first INVITE. In this scenario, somehow the automatic modifying has errors on the end result. Can the different domains affect the end result of the automatic modifying or only the vsf\vst parameters and password are needed to the auto replace\restore? 2 - How can I decrypt the info on vsf and vst parameters in order to verify the info sent and the encryption? Cheers, Duarte Rocha

2 1

uac_restore behaviour question
by Duarte Rocha 22 Jun '23

22 Jun '23

Hello, I have some questions regarding uac_replace methods. When I receive the first INVITE from someone I change To and From using uac_replace_to() and uac_replace_from(). I do this only on first INVITES. In order to restore them I use the "auto" so the changes are restored automatically in replies or requests sent to the call originator.. In the case of subsequent requests from the originator kamailio still changes To and From without me using uac_replace functions. Is this caused by the auto restore? Does it work for both sides and is this is the intended behaviour? Cheers

1 1

How to handle 302 redirects
by Trey Ormsbee 22 Jun '23

22 Jun '23

Hello, Im having a hard time figuring out how to handle a 302 reidrect, the uac_redirect modules shows a simple configuration. However for me, what it is not doing is changing the 302 back to invite. It is sending the 302 as is on. if(!t_check_status("3[0-9][0-9]")) { exit; } get_redirects("3:1"); t_relay(); This code just relays the 302 for me. I should add I am using this with the DISPATCHER module so perhaps that has something to do with my issue. Setup is this, kamailio is sitting between to sip servers, so the flow goes like this, sip_server_a -> kamailio -> sip_server_b. sip_server_b only responds with 302 redirects, sip_server_a does not handle 302’s at all. Kamailio will only get invites from sip_server_a, and the redirects from sip_server_b will only have one contact. How can I get kamailio to reply to sip_server_a’s invite with the updated INVITE? My config is a mesh of the dispatcher example and uac_redirect example with this specific section handling the redirect: # Sample failure route failure_route[RTF_DISPATCH] { xlog("L_NOTICE", "RTF_DISPATCH: "); if (t_is_canceled()) { exit; } # next DST - only for 500 or local timeout if (t_check_status("500") or (t_branch_timeout() and !t_branch_replied())) { if(ds_next_dst()) { t_on_failure("RTF_DISPATCH"); route(RELAY); exit; } } if (t_check_status("302")) { xlog("L_NOTICE", "RTF_DISPATCH: 302 "); if (!get_redirects("1:1")) { xlog("L_NOTICE", "RTF_DISPATCH: failed to get_redirects "); t_reply("480", "Temporarily Unavailable"); exit; } xlog("L_NOTICE", "RTF_DISPATCH: got redirects "); t_relay(“sip_server_a”,”5060”); } } Any ideas what I am doing wrong is this supported? Im expecting once I relay this message that it should be an INVITE not a 302 redirect. I cant find any examples of anyone else really doing this.

3 3

Missing posops module from 5.7 debian repo
by Patrick Karton 20 Jun '23

20 Jun '23

hello , i have installed kamailio 5.7 from debian repo http://deb.kamailio.org/kamailio57 bullseye main but i dont find the posops module in the directory modules. what is the exactly package where i can find it. Thanks.

2 5

KEMI
by iliusha.md＠gmail.com 19 Jun '23

19 Jun '23

Hello, I have the following statement: if KSR.is_method("INVITE") then KSR.log("info", "method not allowed " .. KSR.kx.get_method() .."\n"); KSR.x.exit(); end For some reason, it falls into this condition no matter which method I use, I tried OPTIONS, NOTIFY etc. log file: <core> [core/kemi.c:152]: sr_kemi_core_log(): method not allowed OPTIONS the same with this check: if KSR.is_method_in("I") then KSR.log("info", "method not allowed " .. KSR.kx.get_method() .."\n"); KSR.x.exit(); end this is the lua modparam settings: # ---- lua params ---- modparam("app_lua", "load", "/usr/local/etc/kamailio/main.lua") modparam("app_lua", "reload", 1) modparam("app_lua", "log_mode", 1) cfgengine "lua" version: kamailio 5.7.0 (x86_64/linux) 1c23c2 Any idea what I'm doing wrong?

2 1

Kamailio failover in aws/azure environment
by M Arqum CH 17 Jun '23

17 Jun '23

Hi members, I am setting up kamailio as loadbalcer for asterisk server farm with active-backup conf in Azure cloud using azure loadbalcer, for incoming it works fine external incoming traffic with nated external IP, can any one guide how to do active-backup configuration for internal traffic, as asterisk servers are running on local network. Thanks and regards Arqum

2 1

TLS errors
by nutxase 16 Jun '23

16 Jun '23

Hey All I have been setting up TLS and websocket for kamailio but i keep getting these errors in the log please can someone help me Jun 14 20:51:57 so-sbc-02 /usr/sbin/kamailio[25490]: ERROR: tls [tls_util.h:51]: tls_err_ret(): TLS accept:error:1408A0C1:SSL routines:ssl3_get_client_hello:no shared cipher (sni: [sip.domain.com](http://sip.sipalto.com)) Jun 14 20:51:57 so-sbc-02 /usr/sbin/kamailio[25490]: ERROR: tls [tls_server.c:1333]: tls_h_read_f(): src addr: 1.2.3.4.5:57265 Jun 14 20:51:57 so-sbc-02 /usr/sbin/kamailio[25490]: ERROR: tls [tls_server.c:1336]: tls_h_read_f(): dst addr: 5.4.3.2.1:8089Jun 14 20:51:57 so-sbc-02 /usr/sbin/kamailio[25490]: ERROR: <core> [core/tcp_read.c:1478]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f3c8fc16720 r: 0x7f3c8fc16848 (-1) my config is pretty standard so i am not sure what i am missing using letsencrypt certs #!ifdef WITH_TLS # ----- tls params ----- modparam("tls", "tls_method", "TLSv1.2+") modparam("tls", "certificate", "/etc/kamailio/tls/cert.pem") modparam("tls", "private_key", "/etc/kamailio/tls/ckey.pem") modparam("tls", "ca_list", "/etc/kamailio/tls/fullchain.pem")#!endif Sent with [Proton Mail](https://proton.me/) secure email.

3 5

impossible to modify $tU twice
by David VILLAUME 15 Jun '23

15 Jun '23

Hello, I’m in a scenario where i would apply different modification to $tU to User with KEMI, but I can’t achieve it. I managed to reproduce it with legacy config : Scenario 1 (both values concatenates): route[dbg] { $tU ="aaa"; $tU ="bbb"; } To: sip:aaabbb@5.5.5.5 Scenario 1 (both values concatenates and @ disapears): route[dbg] { $tU ="aaa"; $tU=$null; $tU ="bbb"; } To: sip:aaabbb5.5.5.5 --->without @ I tried different combination with [*] as for avps without success, does anyone have an idea about how to perform it ? Regards, David

3 2

Cannot achieve rtpengine HA
by Arsenijs Kabihno 13 Jun '23

13 Jun '23

Hello, We are trying to achieve rtpengine HA solely with kamailio and rtpengine module. In the following example call goes to rtpengine node 10.5.0.183:22222 and then we stop rtpengine service on this node to simulate failure. Client is triggering re-INVITE, but, apparently, kamailio sticks to initially selected rtpengine, producing the following errors: Jun 12 06:59:48 ap07stvp.xxxxxxx.xxx docker[9373]: 27(33) INFO: {2 2 INVITE jdl9kq6fv51jcv1agk2e} <script>: RTPENGINE branch_id:0 ruri: <null>, method:INVITE, status:200, extra_id: z9hG4bK55018600, rtpengine_answer: replace-origin replace-session-connection SIP-source-address direction=priv1 direction=pub1 SIP-source-address via-branch=extra rtcp-mux-offer generate-mid DTLS=passive SDES-off ICE=force RTP/SAVPF Jun 12 06:59:49 ap07stvp.xxxxxxx.xxx docker[9373]: 27(33) NOTICE: {2 2 INVITE jdl9kq6fv51jcv1agk2e} acc [acc.c:287]: acc_log_request(): ACC: transaction answered: timestamp=1686553189;method=INVITE;from_tag=fcn109nfe9;to_tag=01284cc8-bc58-4104-9629-8e6bb827d97f;call_id=jdl9kq6fv51jcv1agk2e;code=200;reason=OK;src_user=90362;src_domain=10.181.0.1;src_ip=10.5.0.145;dst_ouser=123;dst_user=123;dst_domain=10.181.0.1 Jun 12 06:59:49 ap07stvp.xxxxxxx.xxx docker[9373]: 31(37) INFO: {2 2 INVITE jdl9kq6fv51jcv1agk2e} <script>: RTPENGINE branch_id:0 ruri: <null>, method:INVITE, status:200, extra_id: z9hG4bK55018600, rtpengine_answer: replace-origin replace-session-connection SIP-source-address direction=priv1 direction=pub1 SIP-source-address via-branch=extra rtcp-mux-offer generate-mid DTLS=passive SDES-off ICE=force RTP/SAVPF Jun 12 06:59:49 ap07stvp.xxxxxxx.xxx docker[9373]: 51(57) INFO: {1 2 ACK jdl9kq6fv51jcv1agk2e} <script>: RTPENGINE branch_id:0 ruri: sip:10.5.2.192:5060, method:ACK, status:<null>, extra_id: <null>, rtpengine_offer: replace-origin replace-session-connection SIP-source-address direction=pub1 direction=priv1 SIP-source-address rtcp-mux-demux DTLS=off SDES-off ICE=remove RTP/AVP Jun 12 06:59:49 ap07stvp.xxxxxxx.xxx docker[9373]: 51(57) INFO: {1 2 ACK jdl9kq6fv51jcv1agk2e} <script>: RTPENGINE branch_id:0 ruri: sip:10.5.2.192:5060, method:ACK, status:<null>, extra_id: <null>, rtpengine_offer: replace-origin replace-session-connection SIP-source-address direction=pub1 direction=priv1 SIP-source-address rtcp-mux-demux DTLS=off SDES-off ICE=remove RTP/AVP Jun 12 07:01:26 ap07stvp.xxxxxxx.xxx docker[9373]: 27(33) INFO: {2 3 INVITE jdl9kq6fv51jcv1agk2e} <script>: RTPENGINE branch_id:0 ruri: <null>, method:INVITE, status:200, extra_id: z9hG4bK20888040, rtpengine_answer: replace-origin replace-session-connection SIP-source-address direction=priv1 direction=pub1 SIP-source-address via-branch=extra rtcp-mux-offer generate-mid DTLS=passive SDES-off ICE=force RTP/SAVPF Jun 12 07:01:26 ap07stvp.xxxxxxx.xxx docker[9373]: 27(33) ERROR: {2 3 INVITE jdl9kq6fv51jcv1agk2e} rtpengine [rtpengine.c:3070]: send_rtpp_command(): can't send command "offer" to RTPEngine <udp:10.5.0.183:22222> Jun 12 07:01:26 ap07stvp.xxxxxxx.xxx docker[9373]: 54(60) INFO: {1 3 ACK jdl9kq6fv51jcv1agk2e} <script>: RTPENGINE branch_id:0 ruri: sip:10.5.2.192:5060, method:ACK, status:<null>, extra_id: <null>, rtpengine_offer: replace-origin replace-session-connection SIP-source-address direction=pub1 direction=priv1 SIP-source-address rtcp-mux-demux DTLS=off SDES-off ICE=remove RTP/AVP Jun 12 07:01:26 ap07stvp.xxxxxxx.xxx docker[9373]: 54(60) ERROR: {1 3 ACK jdl9kq6fv51jcv1agk2e} rtpengine [rtpengine.c:2706]: rtpp_function_call(): no available proxies We also found Daniel answer on similar issue here: https://github.com/kamailio/kamailio/issues/2713#issuecomment-823138302 Please advise how it can be solved. Kind regards, Arsenijs

4 5

Carrierroute Test API?
by sr.maillists＠gmail.com 13 Jun '23

13 Jun '23

Hi List Does someone know a function to test a number against the carrierroute module, to see which route it picked? My Idea: We have multiple Kamailio-Proxies and I would like to test a number against all hosts to see where it will be routed, without performing testcalls. Regards Stefan

2 1

Kamailio/MySQL Module compatibility with MySQL 8.0+
by Pedro Ulhoa 13 Jun '23

13 Jun '23

Hello friends. I didn't find about it in the documentation, but I will need to update my database version to MySQL 8.0.32 and I'm using Kamailio version 5.4. I did some quick tests, and I only needed to adjust the user due to the authentication mode, and with that, apparently I had no problems. I would like to know if you are using Kamailio with the latest version of MySQL, if you have had any problems in production, and if it really is safe to upgrade. -- Aviso Legal: Este documento pode conter informações confidenciais e/ou privilegiadas. Se você não for o destinatário ou a pessoa autorizada a receber este documento, não deve usar, copiar ou divulgar as informações nele contidas ou tomar qualquer ação baseada nessas informações. Disclaimer: The information contained in this document may be privileged and confidential and protected from disclosure. If the reader of this document is not the intended recipient, or an employee agent responsible for delivering this document to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited.

3 2

What is the best way to return a lot of data via JSONRPC and jansson?
by Benoit Panizzon 12 Jun '23

12 Jun '23

Hi Team To offer some diagnose functionality I created an API that returns the location list via JSONRPC But this creates huge variables. Jun 12 09:43:32 prod-cpereg02 kamailio[2174548]: ERROR: <core> [core/pvapi.c:1491]: pv_printf_mode(): no more space for spec value - printed:0 token:8599 buffer:8192 Jun 12 09:43:32 prod-cpereg02 kamailio[2174548]: ERROR: <core> [core/pvapi.c:1503]: pv_printf_mode(): buffer overflow -- increase the buffer size... Already hitting the default limit and not sure this is the right way to go as we will end up with thousands of registrations. What is the best way to return larger ammounts of data out of kamailio? Avoid using the JSONRPC and access the database externally? Mit freundlichen Grüssen -Benoît Panizzon- -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

2 1

Dialog DMQ state after restart
by Calvin E. 10 Jun '23

10 Jun '23

Does the dialog module do anything similar to the htable dmq_init_sync behavior? The scenario is restarting the offline member of an HA pair after modifying the script. We're unsure of the state of the replicated dialogs post-restart. Will the standby become aware of the dialogs prior to the restart? In other words, do we need to wait until the pre-restart calls end before we can safely failover? -Calvin E.

5 7

Kamailio - could not allocate private memory from pkg pool
by Muhammad Danish Moosa 09 Jun '23

09 Jun '23

Hi, I have been kamailio services working for few months and suddenly I got this error. ERROR: <core> [core/kemi.c:2923]: sr_kemi_pv_sets(): unable to set pv [$rp] ERROR: <core> [core/pvapi.c:352]: pv_cache_add(): could not allocate private memory from pkg pool ERROR: <core> [core/kemi.c:2914]: sr_kemi_pv_sets(): cannot get pv spec for [$dlg_var(BW0930526150606231188928742(a)10.10.16.100)] ERROR: <core> [core/data_lump.c:544]: dup_lump_list_r(): could not allocate private memory from pkg pool ERROR: <core> [core/data_lump.c:582]: dup_lump_list_r(): out of mem ERROR: tm [t_fwd.c:1759]: t_forward_nonack(): failure to add branches ERROR: <core> [core/msg_translator.c:2501]: build_res_buf_from_sip_req(): could not allocate private memory from pkg pool ERROR: sl [sl_funcs.c:414]: sl_reply_error(): stateless error reply used: I'm terribly sorry, server error occurred (1/SL) ERROR: <core> [core/msg_translator.c:2501]: build_res_buf_from_sip_req(): could not allocate private memory from pkg pool ERROR: tm [t_reply.c:475]: _reply_light(): response building failed WARNING: tm [t_lookup.c:1499]: t_unref(): generation of a delayed stateful reply failed Issue was fixed after the restart of kamailio. -- Muhammad Danish Moosa " The core of mans' spirit comes from new experiences. "___ Christopher McCandless

4 10

Kamailio World
by Fred Posner 05 Jun '23

05 Jun '23

1 0

Invalid Links
by Brandon Armstead 04 Jun '23

04 Jun '23

https://www.kamailio.org/w/kamailio-v5-7-0-release-notes/ article references math module and tls_wolfssl, 2 of the 4 modules mentioned link back to 5.6 (these two) instead of 5.7 resulting in a 404. Respective links should be as follows: math - https://www.kamailio.org/docs/modules/5.7.x/modules/math.html tls_wolfssl - https://www.kamailio.org/docs/modules/5.7.x/modules/tls_wolfssl.html Can we get a correction in the article on WP? Thanks - Brandon

1 0

header from failure_route
by David Villasmil 04 Jun '23

04 Jun '23

Hello guys, so i'm doing on a failure_route: $var(xgws_in_reply) = $T_rpl($hdr(X-GWs)); which when it’s present on the reply is cool… but when there is NO REPLY, then kamailio sets it to “0”… anyway over this? i only want to know whether it is present on the reply Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337

2 2

Missing transformations for {val.*}?
by Kaufman 03 Jun '23

03 Jun '23

Beginning in 5.6 new {val.*} transformations are documented as being exported by the pv module, however if I try using it Kamailio fails to start. Wondering if maybe it's actually imported by another module and the documentation is wrong or something like that? This configuration in 5.6.3 on Alpine Linux installed from packages: #!KAMAILIO loadmodule "pv" loadmodule "xlog" request_route { xlog("Null val: $(avp(nothing){val.ne})\n"); exit; } Fails to start with the following: 0(114) INFO: <core> [main.c:3055]: main(): processes (at least): 29 - shm size: 67108864 - pkg size: 8388608 0(114) ERROR: <core> [core/pvapi.c:1774]: tr_lookup(): unknown transformation: [val] in [{val.ne}] 0(114) ERROR: <core> [core/pvapi.c:1799]: tr_lookup(): error parsing [{val.ne}] 0(114) ERROR: <core> [core/pvapi.c:1106]: pv_parse_spec2(): bad tr in pvar name "avp" 0(114) ERROR: <core> [core/pvapi.c:1131]: pv_parse_spec2(): invalid parsing in [$(avp(nothing){val.ne})] at (4) 0(114) ERROR: xlog [xlog.c:551]: xdbg_fixup_helper(): wrong format[Null val: $(avp(nothing){val.ne})] 0(114) ERROR: <core> [core/route.c:1169]: fix_actions(): fixing failed (code=-1) at cfg:/etc/kamailio/kamailio.cfg:7 Kaufman Sr. VoIP Engineer - BCM One +1.612.735.9309 bkaufman(a)bcmone.com<mailto:bkaufman@bcmone.com> 24 hour client support: +1.855.639.6300 [https://www.bcmone.com/files/bcmone-logo.png]<https://www.bcmone.com/> [https://www.bcmone.com/files/twitter-icon-circle.png] <https://www.facebook.com/bcmonenyc/> [https://www.bcmone.com/files/twitter-icon-circle.png] <https://twitter.com/bcm_one/> [https://www.bcmone.com/files/linkedin-icon-circle.png] <https://www.linkedin.com/company/business-communications-management/> NOTE: This e-mail and any attachments are from BCM One, Inc. and are intended solely for the use and review of the individual(s) to whom it is addressed. If you believe you received this e-mail in error, please notify the sender immediately, delete the e-mail (and any attachments) from your computer and do not copy or disclose it to anyone else.

2 1

custom mid registrar using kamailio.
by Yuriy Nasida 01 Jun '23

01 Jun '23

Hello, https://lists.kamailio.org/pipermail/sr-users/2020-October/110792.html I read this thread very carefully and I think I managed to implement all the steps described by Daniel. Thank you so much for the detailed description. But it looks like I'm stuck on the last step. I can't delete records from htable when an incoming call cannot reach the registered device (e.g., no more internet access, power off at the device). I try to do this from failure route but looks like i kamailio has not access to htable from it. failure_route[INTERNAL_TO_EXTERNAL_FAILURE] { if (t_check_status("408")) { xlog("L_WARN", "$ci|log| hello \n"); xlog("L_WARN", "$ci|log| mid reg token - $sht(mid_reg_token=>$fU::$si::$sp) \n"); } } I do not see xlog message with mid reg token but i see 'hello'. Yes, htable record exists in case i check using: kamcmd htable.dump mid_reg_token Also I need a way to remove registration at the registrar (Freeswitch in my case). This means I need to send api request from kamailio or just run some script that will do this. What is the best way ? module exec ? Please advice, Thanks

2 3

Kamailio and MS Teams side by side present staus und chat function
by Hans-Jürgen Brand 31 May '23

31 May '23

2 1

Is Min-SE check broken?
by harneet singh 31 May '23

31 May '23

Hi All, I am facing an issue in understanding how the min_se should be working in kamailio. As per the SST documentation, it seems like if the min_se is configured as 500, then any value of Session-Expires OR MIN-SE if lower than 500, can be responded to by a 422. However, I strangely see the reverse happening. To investigate further, I looked in to the ki_sst_check_min() code in the master, and these seems like a potential issue. Ref Code: Inside ki_sst_check_min(), there is an if condition like below: if (sst_min_se < MIN(minse, se.interval)) { However, shouldn't it be the other way around? ie if (sst_min_se > MIN(minse, se.interval)) { because we need to send 422 if the received value(in INVITE etc) is smaller than the sst configure min_se value? I also found a different documentation, at https://git.sgu.ru/oldssu/ex-opensips/blob/cb9df8d59dbb254a9d862569fd5d11f6… where the check is as below? if (sst_min_se > MIN(minse, se.interval)) { Can someone confirm if this is broken, or my understanding is incorrect? Regards, Harneet -- "Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth" - Sir Arthur Conan Doyle

2 3

http_client using JWT?
by Benoît Panizzon 31 May '23

31 May '23

Hi The http_client module support the somehow old fashioned way to submit credentials as part of the URL. Our 'held' server developer would love to use either JWT or a Bearer Token in the Auth-Header or a 'cookie-jar' to authenticate the requests. Is this somehow possible? -- Mit freundlichen Grüssen -Benoît Panizzon- @ HomeOffice und normal erreichbar -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

3 2

Knowing about the uac module with primary and secondary proxy setting
by MUSLIH K 31 May '23

31 May '23

Hi, *sip_provider_proxy1[* uac module-register] ---> *kamailio* [dispatcher Module] ----> *Asterisk1* ----> *Asterisk 2* in my configuration kamailio register to the sip provider using *uac module*, sip information are stored in database (uacreg). when a incoming call(INVITE) come to kamailio it will dispatch call to Asterisk using* "dispatcher module".* Here i have couple of questions 1. If my SIP provider has a secondary proxy as a failover server (sip_provider_proxy2), can I configure Kamailio with the uac module to use the secondary proxy if the primary proxy fails? 2. Since my application is inbound-only, registration failure is only identified when the registration expires (3600 seconds = 1 hour). Can I use the dispatcher module to select the SIP proxy and switch the registration to the secondary proxy if the primary proxy is not reachable (using OPTIONS)?

2 2

DISABLE SDP MEDIA STREAMS
by Patrick Karton 29 May '23

29 May '23

Hello kamailio community, i know its an unusual query but i would like to know if there is a cleaner/proper.right way to disable some (or all) media streams in SDP. i have come with a solution by sdpops module with subst_body function like this. route[SDP_DISABLE_UNAUTHORIZED_MEDIA]{ # disable text,media and video media streams subst_body('#^m=(video|text|audio)[ ]+[0-9/]+(.*)$#m=\1 0 \2#ig'); # update originator ip address subst_body('#^o=([^ ]+)[ ]+([^ ]+)[ ]+([^ ]+)[ ]+([^ ]+)[ ]+([^ ]+)[ ]+([^ ]+)$#o=\1 \2 \3 \4 \5 7.7.7.7#ig'); # 1 2 2 4 5 6 # name sid snumber network net-type addr # update connection ip address subst_body('#^c=([^ ]+)[ ]+([^ ]+)[ ]+([^ ]+)$#c=\1 \2 7.7.7.7#ig'); # 1 2 3 # network net-type addr #remove all media attributes sdp_remove_line_by_prefix("a=fmtp"); sdp_remove_line_by_prefix("a=X-"); sdp_remove_line_by_prefix("a=rtcp"); sdp_remove_line_by_prefix("a=ssrc"); sdp_remove_line_by_prefix("a=sendrecv"); sdp_remove_line_by_prefix("a=sendonly"); sdp_remove_line_by_prefix("a=recvonly"); sdp_remove_line_by_prefix("a=inactive"); sdp_remove_line_by_prefix("b="); } is it the right way to do it. if not can someone provide me an alternative solution. Thanks :)

3 2

Re: [sr-dev] Troubles with outbound kamailio call to other server
by Henning Westerholt 26 May '23

26 May '23

Hello (added sr-users, as its probably more a usage question). The SIP message (the BYE) cannot be parsed apparently. From the log it looks that there is an invalid character in the first line. Do a network trace to analyse the packets that its actually send and try to get some more clues from that. Cheers, Henning -- Henning Westerholt – https://skalatan.de/blog/ Kamailio services – https://gilawa.com > -----Original Message----- > From: aaron.soto(a)dialapplet.com <aaron.soto(a)dialapplet.com> > Sent: Freitag, 26. Mai 2023 10:44 > To: sr-dev(a)lists.kamailio.org > Subject: [sr-dev] Troubles with outbound kamailio call to other server > > Hi everyone, > I'm having the following errors in kamailio when i try to make an outbound call to > other server, I don't know what does it mean, if some one can help me > > 11(25) ERROR: <core> [core/receive.c:310]: receive_msg(): core parsing of SIP > message failed (XX.XX.XX.XX.5060/1) > 13(27) ERROR: <core> [core/parser/parse_fline.c:271]: parse_first_line(): > parse_first_line: bad message (offset: 65) > 13(27) ERROR: <core> [core/parser/msg_parser.c:681]: parse_msg(): ERROR: > parse_msg: message=<BY > sip:asterisk@10.0.5.158:4080;alias=10.0.5.158~44730~1 SIP/2.0 > Via: SIP/2.0/UDP 84.127.226.15:5060;branch=z9hG4bK3bc90b47;rport > Route: <sip:34.252.151.179:4060;r2=on;lr;ftag=5c7f862f-9692-4028-8af0- > ebc224ba0e2a;vsf=AAAAAAAAAAAAAAAAAAAJCQABGgUAAAMJLjE4ODo1MDYw; > nat=yes>,<sip:10.0.5.40:4070;r2=on;lr;ftag=5c7f862f-9692-4028-8af0- > ebc224ba0e2a;vsf=AAAAAAAAAAAAAAAAAAAJCQABGgUAAAMJLjE4ODo1MDYw; > nat=yes> > Max-Forwards: 70 > From: <sip:692598435@kamailio.voip.svc.cluster.local>;tag=as6f32aa26 > To: <sip:963441038@192.168.123.66:4060>;tag=5c7f862f-9692-4028-8af0- > ebc224ba0e2a > Call-ID: b9a49c52-7829-4cdf-a88c-0064cc5bb438 > CSeq: 102 BYE > User-Agent: Asterisk PBX 11.2-cert3 > X-Asterisk-HangupCause: No user responding > X-Asterisk-HangupCauseCode: 18 > Content-Length: 0 > > > > _______________________________________________ > Kamailio (SER) - Development Mailing List To unsubscribe send an email to sr-dev- > leave(a)lists.kamailio.org

1 0

Consistent huntable responses based on failure_route question
by John Hardiman 25 May '23

25 May '23

Hi Kamailio list, I hope you are all well? I am looking for some assistance on a specific error I am trying to work around. Kamailio 5.5.3 - Ubuntu 20.04 Kemi Python script (but I think this is more default failure_route behaviour) Dispatcher module which hunts to a group of FreeSWITCH that I have configured to send 503 responses on. My scenario is fairly simple, I am trying to respond back to a carrier for huntable responses (503 specifically) by calling a failure route below: def ksr_failure_manage(self, msg): if KSR.tm.t_any_timeout()>0 : self.ksr_send_reply_clear_rtpengine(msg, 503, "Timeout to destination") KSR.err("Timeout to Invite for %s from IP %s" % (KSR.pv.get("$ci"),KSR.pv.get("$si"))) return 1 else: self.ksr_send_reply_clear_rtpengine(msg, 503, "Unknown error failover to next node") KSR.err("Failed but not timeout for %s from IP %s" % (KSR.pv.get("$ci"),KSR.pv.get("$si"))) return 1 This works and a 503 with the correct message is sent if the invite doesn't get a response after 2 seconds. (My specific test case here) # Timers for call setup 2 minutes for any 1xx provisional response received # If no invite response received in 2 seconds end the call as per failure route. KSR.tm.t_set_fr(120000, 2000) self.ksr_route_relay(msg) KSR.tm.t_on_failure("ksr_failure_manage") return -255 The issue is after a few more milliseconds after my initial 503 a 408 is sent. Also after the failover if the carrier tries the same Kamailio again it gets a 500 rather than a 408. 408: [cid:image001.png@01D98F15.CD07DCB0] 500: [cid:image002.png@01D98F15.CD07DCB0] My steps to get around this have been to change the default tm code to 503 below, but this has not changed the default response and the above behaviour unfortunately: # ----- tm params ----- # auto-discard branches from previous serial forking leg modparam("tm", "failure_reply_mode", 3) # setting default reason code and response for general errors to allow failover. modparam("tm", "default_code", 503) modparam("tm", "default_reason", "Unknown reason try next node") My question is: How can I make sure my failure route is the final response here. Or if I cannot make sure of this, how can I change the default mapped response to be a consistent SIP response (503 specifically) Many thanks in advance as I am scratching my head on this one a bit. John.

2 2

Override listen advertise address
by Calvin E. 25 May '23

25 May '23

Using 5.6.x, a scenario designed for a public IP now needs to support life in the cloud behind NAT. I'd like to avoid having two listeners to separate on-net from off-net traffic. In a HA scenario, it would be nice to have only one floating IP. Is it possible to use the same local address and port for external/public and internal/private traffic? Should set_advertised_address() override the listen advertise address? Initial testing did not produce the expected result. I want to make sure I'm following a sane pattern before going down a rabbit hole. The idea is to toggle the advertised address by checking if the sender or recipient is rfc1918(). For the dispatcher module, is it possible to use socket names like below? In testing it appeared that only one of the two names was valid. listen=udp:10.0.0.10:5060 name "onnet" listen=udp:10.0.0.10:5060 advertise 11.11.11.11:5060 name "offnet"

3 4

lost module: best practice handling delay caused by held / lis procedure?
by Benoit Panizzon 25 May '23

25 May '23

Hi gang In 2024, Switzerland will start using NG112 (NG911) procedures to transmit the caller location via Geolocation URL via LIS Server to a PSAP. So time to start testing this on my devel plattform. Kamailio ships with the lost module which looks promising. In short, the Procedure is as follows: Customer calls emergency number. Kamailio performs a http request to our inhouse HELD server with the identification of the calling customer. HELD server looks up the location of the caller and pushes a HELD XML object to the Swiss LIS Server, which then is queried by the emergency PSAP receiving the call. LIS server return and URL. HELD server returns the URL to Kamailio. Kamailio adds Geolocation Header with that URL and relays the call. This takes some time and as the call is not yet being relayed while waiting for the held request to complete, there is no 100 trying being sent and the emergency call is bound to time out. So, shall I call t_reply("100","Performing HELD lkup") before calling the lost module? Or is there a better way? Mit freundlichen Grüssen -Benoît Panizzon- -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

3 7

cancel at first call after startup kamailio not relay
by Giuseppe Pandolfi 23 May '23

23 May '23

Hi, I have a problem with kamailio v 5.6.1 on mips architecture: version: kamailio 5.6.1 (mips/linux) flags: USE_TCP, USE_TLS, 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-NOSMP, USE_PTHREAD_MUTEX, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLOCKLIST, HAVE_RESOLV_RES 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 on 14:22:18 Apr 27 2023 Using default script for make a call from sip ua to PSTN system (#!define WITH_PSTN), the cancel sent for the first call after start kamailio doesn't relay to PSTN system and I have the trace error beelow: 2(3203) BUG: {1 27018 CANCEL 0tBgb95Z.0eE5VVrAkoP06nvunIknKNz} tm [t_cancel.c:318]: cancel_branch(): local_cancel buffer=(nil) != BUSY_BUFFER (trying to continue) 12(3203) ERROR: {1 27018 CANCEL 0tBgb95Z.0eE5VVrAkoP06nvunIknKNz} tm [t_fwd.c:1434]: e2e_cancel(): cancel error the next calls works fine. Does anyone have any suggestions? Beelow trace at debug level: 37(3695) INFO: <core> [core/cfg/cfg_ctx.c:602]: cfg_set_now(): core.debug has been changed to 3 37(3695) DEBUG: ctl [io_listener.c:518]: handle_stream_read(): bytes processed: 23 12(3670) DEBUG: <core> [core/parser/parse_fline.c:250]: parse_first_line(): first line type 1 (request) flags 1 12(3670) DEBUG: <core> [core/parser/msg_parser.c:677]: parse_msg(): SIP Request: 12(3670) DEBUG: <core> [core/parser/msg_parser.c:679]: parse_msg(): method: <CANCEL> 12(3670) DEBUG: <core> [core/parser/msg_parser.c:681]: parse_msg(): uri: <sip:100@192.168.2.238:5060> 12(3670) DEBUG: <core> [core/parser/msg_parser.c:683]: parse_msg(): version: <SIP/2.0> 12(3670) DEBUG: <core> [core/parser/parse_hname2.c:302]: parse_sip_header_name(): parsed header name [Via] type 1 12(3670) DEBUG: <core> [core/parser/parse_via.c:1303]: parse_via_param(): Found param type 235, <rport> = <n/a>; state=6 12(3670) DEBUG: <core> [core/parser/parse_via.c:1303]: parse_via_param(): Found param type 232, <branch> = <z9hG4bKPjLBcUXshEKW2s9T0en9czTYAsciW1vV-W>; state=16 12(3670) DEBUG: <core> [core/parser/parse_via.c:2639]: parse_via(): end of header reached, state=5 12(3670) DEBUG: <core> [core/parser/msg_parser.c:555]: parse_headers(): Via found, flags=2 12(3670) DEBUG: <core> [core/parser/msg_parser.c:557]: parse_headers(): this is the first via 12(3670) DEBUG: <core> [core/parser/parse_hname2.c:302]: parse_sip_header_name(): parsed header name [Max-Forwards] type 8 12(3670) DEBUG: <core> [core/parser/parse_hname2.c:302]: parse_sip_header_name(): parsed header name [From] type 4 12(3670) DEBUG: <core> [core/parser/parse_hname2.c:302]: parse_sip_header_name(): parsed header name [To] type 3 12(3670) DEBUG: <core> [core/parser/parse_addr_spec.c:884]: parse_addr_spec(): end of header reached, state=9 12(3670) DEBUG: <core> [core/parser/msg_parser.c:173]: get_hdr_field(): <To> [23]; uri=[sip:100@192.168.2.238] 12(3670) DEBUG: <core> [core/parser/msg_parser.c:176]: get_hdr_field(): to body (23)[sip:100@192.168.2.238 ], to tag (0)[] 12(3670) DEBUG: <core> [core/parser/parse_hname2.c:302]: parse_sip_header_name(): parsed header name [Call-ID] type 6 12(3670) DEBUG: <core> [core/parser/parse_hname2.c:302]: parse_sip_header_name(): parsed header name [CSeq] type 5 12(3670) DEBUG: <core> [core/parser/msg_parser.c:154]: get_hdr_field(): cseq <CSeq>: <17038> <CANCEL> 12(3670) DEBUG: <core> [core/receive.c:394]: receive_msg(): --- received sip message - request - call-id: [CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU] - cseq: [17038 CANCEL] 12(3670) DEBUG: <core> [core/parser/parse_hname2.c:302]: parse_sip_header_name(): parsed header name [User-Agent] type 28 12(3670) DEBUG: <core> [core/parser/parse_hname2.c:302]: parse_sip_header_name(): parsed header name [Content-Length] type 12 12(3670) DEBUG: <core> [core/parser/msg_parser.c:187]: get_hdr_field(): content_length=0 12(3670) DEBUG: <core> [core/parser/msg_parser.c:91]: get_hdr_field(): found end of header 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} <core> [core/receive.c:261]: ksr_evrt_pre_routing(): event route core:pre-routing not defined 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} <core> [core/receive.c:471]: receive_msg(): preparing to run routing scripts... 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} maxfwd [mf_funcs.c:74]: is_maxfwd_present(): value = 70 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} sanity [sanity.c:247]: check_ruri_sip_version(): check_ruri_sip_version entered 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} sanity [sanity.c:270]: check_ruri_sip_version(): check_ruri_sip_version passed 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} sanity [sanity.c:277]: check_ruri_scheme(): check_ruri_scheme entered 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} sanity [sanity.c:297]: check_ruri_scheme(): check_ruri_scheme passed 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} sanity [sanity.c:318]: check_required_headers(): check_required_headers entered 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} sanity [sanity.c:340]: check_required_headers(): check_required_headers passed 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} sanity [sanity.c:348]: check_via1_header(): check via1 header 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} sanity [sanity.c:506]: check_cseq_method(): check_cseq_method entered 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} sanity [sanity.c:539]: check_cseq_method(): check_cseq_method passed 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} sanity [sanity.c:548]: check_cseq_value(): check_cseq_value entered 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} sanity [sanity.c:576]: check_cseq_value(): check_cseq_value passed 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} sanity [sanity.c:585]: check_cl(): check_cl entered 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} sanity [sanity.c:610]: check_cl(): check_cl passed 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} sanity [sanity.c:622]: check_expires_value(): check_expires_value entered 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} sanity [sanity.c:659]: check_expires_value(): no expires header found 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} sanity [sanity.c:758]: check_parse_uris(): check_parse_uris entered 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} sanity [sanity.c:762]: check_parse_uris(): parsing ruri 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} sanity [sanity.c:776]: check_parse_uris(): looking up From header 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} <core> [core/parser/parse_addr_spec.c:185]: parse_to_param(): add param: tag=Jjj1QBeRxydZ5rq.-xKCfcJZhlPANj9N 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} <core> [core/parser/parse_addr_spec.c:884]: parse_addr_spec(): end of header reached, state=29 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} sanity [sanity.c:791]: check_parse_uris(): looking up To header 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} sanity [sanity.c:837]: check_parse_uris(): check_parse_uris passed 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} sanity [sanity_mod.c:254]: w_sanity_check(): sanity checks result: 1 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} tm [t_lookup.c:727]: t_lookupOriginalT(): searching on hash entry 10182 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} tm [t_lookup.c:440]: matching_3261(): RFC3261 transaction matched, tid=PjLBcUXshEKW2s9T0en9czTYAsciW1vV-W 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} tm [t_lookup.c:823]: t_lookupOriginalT(): canceled transaction found (0x729bff78)! 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} tm [t_lookup.c:826]: t_lookupOriginalT(): found - lookup completed 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} tm [tm.c:1232]: ki_t_lookup_cancel_flags(): lookup_original: t_lookupOriginalT returned: 0x729bff78 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} tm [t_lookup.c:1348]: t_newtran(): msg (0x771181ec) id=1/3670 global id=0/0 T start=0xffffffff 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} tm [t_lookup.c:498]: t_lookup_request(): start searching: hash=10182, isACK=0 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} tm [t_lookup.c:456]: matching_3261(): RFC3261 transaction matching failed - via branch [z9hG4bKPjLBcUXshEKW2s9T0en9czTYAsciW1vV-W] 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} tm [t_lookup.c:675]: t_lookup_request(): no transaction found 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} <core> [core/crypto/md5utils.c:67]: MD5StringArray(): MD5 calculated: dd71ad9d7511b02a5fc83c3c70ce307f 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} tm [t_lookup.c:727]: t_lookupOriginalT(): searching on hash entry 10182 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} tm [t_lookup.c:432]: matching_3261(): matched skip method - s:0x2 t:0x2 m:0x2 - continue searching 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} tm [t_lookup.c:440]: matching_3261(): RFC3261 transaction matched, tid=PjLBcUXshEKW2s9T0en9czTYAsciW1vV-W 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} tm [t_lookup.c:823]: t_lookupOriginalT(): canceled transaction found (0x729bff78)! 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} tm [t_lookup.c:826]: t_lookupOriginalT(): found - lookup completed 12(3670) BUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} tm [t_cancel.c:318]: cancel_branch(): local_cancel buffer=(nil) != BUSY_BUFFER (trying to continue) 12(3670) ERROR: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} tm [t_fwd.c:1434]: e2e_cancel(): cancel error 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} tm [t_reply.c:1763]: cleanup_uac_timers(): RETR/FR timers reset 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} tm [t_reply.c:638]: _reply_light(): reply sent out - buf=0x77101e68: SIP/2.0 500 cancel e... shmem=0x729c5b60: SIP/2.0 500 cancel e 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} tm [t_funcs.c:120]: put_on_wait(): put T [0x729c36d8] on wait 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} tm [t_reply.c:648]: _reply_light(): finished 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} tm [t_funcs.c:373]: t_relay_to(): new transaction forwarded 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} <core> [core/receive.c:529]: receive_msg(): request-route executed in: 9868 usec 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} <core> [core/usr_avp.c:637]: destroy_avp_list(): destroying list (nil) 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} <core> [core/usr_avp.c:637]: destroy_avp_list(): destroying list (nil) 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} <core> [core/usr_avp.c:637]: destroy_avp_list(): destroying list (nil) 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} <core> [core/usr_avp.c:637]: destroy_avp_list(): destroying list (nil) 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} <core> [core/usr_avp.c:637]: destroy_avp_list(): destroying list (nil) 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} <core> [core/usr_avp.c:637]: destroy_avp_list(): destroying list (nil) 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} <core> [core/xavp.c:541]: xavp_destroy_list(): destroying xavp list (nil) 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} <core> [core/xavp.c:541]: xavp_destroy_list(): destroying xavp list (nil) 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} <core> [core/xavp.c:541]: xavp_destroy_list(): destroying xavp list (nil) 12(3670) DEBUG: {1 17038 CANCEL CYxrNJtcCFZKS.PJN29LlEBd0aejPQUU} <core> [core/receive.c:628]: receive_msg(): cleaning up 34(3692) DEBUG: tm [timer.c:642]: wait_handler(): finished transaction: 0x729c36d8 (p:0x72866768/n:0x729bff78) 34(3692) DEBUG: tm [h_table.c:132]: free_cell_helper(): freeing transaction 0x729c36d8 from timer.c:650

1 0

mk_proxy(): could not resolve hostname
by ajosebar＠gmail.com 23 May '23

23 May '23

I have Kamailio 5.6 on Debian 11. I need to use the function forward within a routing block in my configuration file: forward("udp:192.168.28.51:5060"); But when I start the kamailio service I got: CRITICAL: [core/proxy.c:264]: mk_proxy(): could not resolve hostname: "udp:192.168.28.51:5060" The same occurs when I use the dns nane : forward("udp:raspberry3.emtelco.co:5060"); Any ideas ? Regards

2 1

DNS resolution with ipops
by harneet singh 22 May '23

22 May '23

Hi Experts, I am planning to use *dns_query*() API from the ipops module, which I understand from some documentation that it internally uses *getaddrinfo*(). I wanted to check if someone can comment on the DNS Cache mechanism in this case. * Does Kamailio retain any *dns cache* while using this API, or would it be actually doing the resolution for each call. * In light of the above, does Kamailio honour the *TTL value i*n response to the DNS Query? Regards, Harneet Singh -- "Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth" - Sir Arthur Conan Doyle

2 1

MySQL duplicate entry error on location after 5.5 => 5.6 upgrade
by Benoit Panizzon 22 May '23

22 May '23

Hi list Since updating 5.5 to 5.6 i often see this message in the logs: ERROR: db_mysql [km_dbase.c:122]: db_mysql_submit_query(): driver error on query: Duplicate entry 'uloc-645ca178-f29e-1' for key 'location.ruid_idx' (1062) ERROR: <core> [db_query.c:244]: db_do_insert_cmd(): error while submitting query ERROR: usrloc [ucontact.c:687]: db_insert_ucontact(): inserting contact in db failed ****** (uloc-645ca178-f29e-1) ERROR: usrloc [urecord.c:420]: wb_timer(): inserting contact into database failed (aor: *******) usrloc is dmq synced between two nodes. Were there some changes which could have caused this issue? Mit freundlichen Grüssen -Benoît Panizzon- -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

1 0

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

21 May '23

Kamailio v5.7.0 is out – it comes with 4 new modules and a large set of improvements touching again more than 60 existing modules. You can read a bit more detailed release notes at: * https://www.kamailio.org/w/kamailio-v5-7-0-release-notes/ Many thanks to all developers and community members that made possible this release. v5.7.0 brings more flexibility and optimizations across many components, new variables and transformations, expression-based preprocessor values and conditions, alternative TLS module using WolfSSL project, improvements to STIR/SHAKEN, IMS/VoLTE, more functions exported to KEMI interface, including a new KEMI Python3 interpreter. ... just to list only a few here. Enjoy Kamailio v5.7.0! Thank you for flying Kamailio! Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - June 5-7, 2023 - www.kamailioworld.com

2 1

db_redis and ursloc - problem after restarting kamailio
by Koldo Aingeru 18 May '23

18 May '23

Hi, I've encountered a problem using db_redis for location, we recently migrated to redis from mysql and just found out this yesterday. We are using the usrloc module with db_mode = 2, so the location info is written to redis every 60 seconds. When restarting, Kamailio reads all the contacts and loads them into memory, but for some contacts it loads the “methods” key with an incorrect value. If in the REGISTER there are no methods kamailio saves it with methods= -1: { "jsonrpc": "2.0", "result": { "AoR": “zzzzzzz", "Contacts": [{ "Contact": { "Address": "sip:1540305477794@W.X.Y.Z:5060", "Expires": 2752, "Q": -1, "Call-ID": "7d3965a85bfd0e88-32357(a)W.X.Y.Z", "CSeq": 11, "User-Agent": “xxxxxxx", "Received": "sip:W.X.Y.Z:5060", "Path": "<sip:A.B.C.D;lr;received=sip:W.X.Y.Z:5060>", "State": "CS_SYNC", "Flags": 0, "CFlags": 64, "Socket": “udp:A.B.C.D:5060", "Methods": -1, "Ruid": "uloc-644a176b-6472-4641", "Instance": "[not set]", "Reg-Id": 0, "Server-Id": 0, "Tcpconn-Id": -1, "Keepalive": 1, "Last-Keepalive": 1684246829, "Last-Modified": 1684246829 } }] }, "id": 19286 } But when restarting kamailio, the same contacts has a methods= 0 { "jsonrpc": "2.0", "result": { "AoR": “zzzzzzz", "Contacts": [{ "Contact": { "Address": "sip:1540305477794@W.X.Y.Z:5060", "Expires": 2697, "Q": -1, "Call-ID": "7d3965a85bfd0e88-32357(a)W.X.Y.Z", "CSeq": 11, "User-Agent": “xxxxxxx", "Received": "sip:W.X.Y.Z:5060", "Path": "<sip:A.B.C.D;lr;received=sip:W.X.Y.Z:5060>", "State": "CS_SYNC", "Flags": 0, "CFlags": 64, "Socket": “udp:A.B.C.D:5060", "Methods”: 0, "Ruid": "uloc-644a176b-6472-4641", "Instance": "[not set]", "Reg-Id": 0, "Server-Id": 0, "Tcpconn-Id": -1, "Keepalive": 1, "Last-Keepalive": 1684246829, "Last-Modified": 1684246829 } }] }, "id": 19286 } In the schema file for redis the key is correctly set as int and in redis I can see it saved as -1. So when a call comes in, the lookup() function returns a -2 as it doesn’t support the INVITE method and the call fails. This is happening in kamailio 5.2.8 and kamailio 5.2.1 (old versions, I know, we are working on updating it); with mysql as a backend it works perfectly after a restart. We do have the param method_filtering=1 , changing to 0 makes it works. We seem to have this since forever and for what I can see, is not unusual as is in the default kamailio.cfg provided (even the default value for it is 0). Has anyone else encountered this? Thanks! ======================================== Koldo Aingeru Marcos Fdez. Ingeniería de Sistemas Sarenet S.A.U. 944209470 Parque Tecnológico, Edificio 103 48170 Zamudio, Bizkaia www.sarenet.es ========================================

2 2

Contact changes, caller dialog attributes and NAT traversal
by Alex Balashov 17 May '23

17 May '23

Hi, When I modify INVITEs with set_contact_alias() / add_contact_alias(), this is not preserved in dialog data, and therefore not honoured in BYEs locally generated due to dialog timeout. For example, if the initial INVITE contained: Contact: sip:line1@192.168.1.100 and, after transit, became: Contact: <sip:line1@192.168.1.100>;alias=1.1.1.1~25844~1 There is no ;alias value stored in the caller dialog data, just the original URI + parameters. A related problem: I tried to work around this by storing an alias in dialog user variables, e.g. $dlg_var(alternate_ct) = $_s($si~$sp~$prid) and in fact, I am able to recover this value later: event_route[tm:local-request] { if($dlg_var(alternate_ct) ne $null) { $ru = $ru + ";alias=" + $dlg_var(alternate_ct); handle_ruri_alias(); } } And in fact, if I print the value of $du after calling handle_ruri_alias(), I can see that it is modified. However, this seems to have no effect on where the request actually goes at the network and transport level. I assume this is because the event_route does not actually allow one to overwrite elements of the spoofed request, and that its essential attributes have been pre-populated elsewhere. Nevertheless, the effect is that these BYEs do not reach NAT'd endpoints. Any suggestions are appreciated! Thanks in advance, -- Alex -- Alex Balashov Principal Consultant Evariste Systems LLC Web: https://evaristesys.com Tel: +1-706-510-6800

2 4

Re: Releasing Kamailio v5.7.0
by Daniel-Constantin Mierla 17 May '23

17 May '23

The header style was wrong for ctl, fixed, thanks. Daniel On 15.05.23 18:55, Дилян Палаузов wrote: > Off-list > > Hello, > > at > https://github.com/kamailio/kamailio-wiki/blob/main/docs/features/new-in-5.… there > is a horizonal line after ctl, which shall not be there. > > Greetings > Дилян > > > На 15 май 2023 г. 7:20:55 UTC, Daniel-Constantin Mierla > <miconda(a)gmail.com> написа: > > Hello, with a few public holidays coming soon around here, I am > considering to release 5.7.0 this week on Wednesday, May 17, 2023. > Rather short notice, but there were no major bug reports that need > to be tracked. The list of new features is being built in the > wiki: - > https://github.com/kamailio/kamailio-wiki/blob/main/docs/features/new-in-5.… > The other tutorials related to this major release should be ready > by then as well. Should anyone think more time is needed, then it > can be postponed, not a problem at all. Cheers, Daniel > -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - June 5-7, 2023 - www.kamailioworld.com

1 0

Releasing Kamailio v5.7.0
by Daniel-Constantin Mierla 17 May '23

17 May '23

Hello, with a few public holidays coming soon around here, I am considering to release 5.7.0 this week on Wednesday, May 17, 2023. Rather short notice, but there were no major bug reports that need to be tracked. The list of new features is being built in the wiki: - https://github.com/kamailio/kamailio-wiki/blob/main/docs/features/new-in-5.… The other tutorials related to this major release should be ready by then as well. Should anyone think more time is needed, then it can be postponed, not a problem at all. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - June 5-7, 2023 - www.kamailioworld.com

2 3

Diameter_authorization_rejected (FHOSS)
by Wilmes, Matthias 16 May '23

16 May '23

Hello sr-users, i use the guide for "how to integrate an IMS using Kamailio with open5gs EPC" from Supreeth Herle. When my CotsUE(ONEPLUS8) try to Register. I get an 403 Forbidden HSS Authorization Rejected (see udp-stream.txt). The output of the fhoss looks like this. de.fhg.fokus.hss.cx.CxFinalResultException: Diameter_Authorization_Rejected at de.fhg.fokus.hss.cx.op.UAR.processRequest(UAR.java:134) at de.fhg.fokus.hss.main.Task.execute(Task.java:169) at de.fhg.fokus.hss.main.Worker.run(Worker.java:66) Insufficient access rights for the mysql hss_db? The user hss@localhost and hss@% have grant access. Maybe someone has had the error and has a hint and can help. Can't find the error. Many thanks in advance for an answer. -M.Wilmes

3 2

How to prevent run-away dialogues?
by Benoît Panizzon 15 May '23

15 May '23

Hi team Is there any way to get correct CDRS when using the dialog module and restarting kamailio? I have configured the dialog timeout to be 12 hours. But today while doing IC billing, we stumbled over a call that lasted for a week. Probably due to a stale entry in the database dialogue tables left over after a kamailio restart. Looking at the logs there definitely was something wrong: dialog [dlg_req_within.c:211]: bye_reply_cb(): inconsistent dlg timer data on dlg 0x7f153f503778 [956:2612] with clid '35BEFD13@7f33ff47' and tags '7f33ff47+1+75300082+dde85140' '3891401256-2097511021' acc [acc_cdr.c:229]: db_write_cdr(): fallback to dlg_only search because of message doesn't exist. -- Mit freundlichen Grüssen -Benoît Panizzon- @ HomeOffice und normal erreichbar -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

2 1

[auth_radius.c:123]: mod_init(): failed to open configuration file
by Denys Pozniak 12 May '23

12 May '23

Hello! After a major upgrade of Kamailio (5.1 -> 5.6), an error appears that it is not possible to open configuration file (I think this is about /etc/radiusclient/radiusclient.conf), although it exists with the necessary access rights: *0(27075) DEBUG: <core> [core/sr_module.c:969]: init_mod(): auth_radius0(27075) ERROR: auth_radius [auth_radius.c:123]: mod_init(): failed to open configuration file0(27075) ERROR: <core> [core/sr_module.c:975]: init_mod(): Error while initializing module auth_radius (/usr/lib64/kamailio/modules/auth_radius.so)ERROR: error while initializing modules* For the test, I made Kamailio downgrade back to 5.1 and the problem went away. Shortened the Kamailio config to the minimum for reproducing the problem: *#!KAMAILIOmemdbg=5memlog=5children=1log_stderror=nolisten=udp:127.0.0.1:5060 <http://127.0.0.1:5060>loadmodule "kex.so"loadmodule "corex.so"loadmodule "tm.so"loadmodule "sl.so"loadmodule "rr.so"loadmodule "pv.so"loadmodule "maxfwd.so"loadmodule "auth.so"loadmodule "auth_radius.so"modparam("auth_radius", "radius_config", "/etc/radiusclient/radiusclient.conf")request_route { return;}* Could the commit below somehow affect the acceptance of the radius_config module parameter? https://github.com/kamailio/kamailio/commit/f33ba318b20cbd2b34d278a7e2c4e64… -- BR, Denys Pozniak

4 7

kamcmd ul.db_contacts how to specify table name?
by Benoît Panizzon 12 May '23

12 May '23

Good morning. I'm trying to get the number of registered contacts with kamcmd ul.db_contacts. The table has the default name 'location'. But no matter what I try: kamcmd ul.db_contacts location kamcmd ul.db_contacts s:location kamcmd ul.db_contacts database.location kamcmd ul.db_contacts s:database.location Kamcmd complains the table is not found. What would be the correct syntax to provide the table name? Attempted with Kamailio 5.5 and 5.6 -- Mit freundlichen Grüssen -Benoît Panizzon- @ HomeOffice und normal erreichbar -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

1 1

ICMP Port Unreachable using loopback interface with ethernet IP
by Calvin E. 11 May '23

11 May '23

The scenario is Kamailio on Debian 11 talking to an external application server that returns a 302 with a Contact that contains Kamailio's own IP and a different port. Kamailio is listening on the correct port via at the given IP address. However, when Kamailio creates the packet to talk to itself, it it send over the loopback adapter "lo" and gets an ICMP port reply: listen=udp:KAMAILIO_INTERNAL_FLOATING_IP:8888 10.z.a.b.5000 > 10.z.x.y.5060: SIP, length: 849 SIP/2.0 302 Moved Temporarily Contact: <sip:44123456...@10.z.x.y:8888> 15:39:00.548722 lo In IP (tos 0x10, ttl 64, id 5431, offset 0, flags [none], proto UDP (17), length 949) 10.z.x.y.5060 > 10.z.x.y.8888: SIP, length: 921 15:39:00.548732 lo In IP (tos 0xd0, ttl 64, id 19038, offset 0, flags [none], proto ICMP (1), length 576) 10.z.x.y > 10.z.x.y: ICMP 10.44.7.136 udp port 8888 unreachable, length 556 Do I need to configure something in the OS or Kamailio to allow the ethernet IP to work via the loopback adapter? I haven't set up any special networking to cause this, it appears to be a Linux kernel behavior.

3 3

where add contact header to ack for fail messages
by mohsen khashei 11 May '23

11 May '23

Hi I want to know where kamailio sends ack messages to faiurel messages (status >=400) so that I I add Contact header to the ack. I tried WITHINDLG with no luck. thanks

5 6

GeoIP2 and KEMI
by Michal Hajek 11 May '23

11 May '23

Hello, why this commit is not in branch 5.6? https://github.com/kamailio/kamailio/commit/21817906853140322c701f8cbb82010… Without this, is KEMI and GeoIP2 incompatible. Thanks Michal

2 1

kamailio/kamailio-ci docker image
by Sergey Safarov 11 May '23

11 May '23

Hi Now "kamailio/kamailio-ci" docker image is pushed to GitHub packages <https://github.com/kamailio/kamailio-ci/pkgs/container/kamailio-ci> only. I have a question should we completely switch to using the GitHub docker repo and remove the "kamailio/kamailio-ci" docker image from Docker Hub <https://hub.docker.com/repository/docker/kamailio/kamailio-ci>? Or required to push the "kamailio/kamailio-ci" docker image to GitHub packages and Docker Hub repos? Sergey

2 1

Re: where add contact header to ack for fail messages
by Henning Westerholt 11 May '23

11 May '23

Understood. Thanks for sharing your final solution, added the list as well that others can benefit from it. Cheers, Henning From: mohsen khashei <mkhashei(a)gmail.com> Sent: Donnerstag, 11. Mai 2023 12:37 To: Henning Westerholt <hw(a)gilawa.com> Subject: Re: [SR-Users] Re: where add contact header to ack for fail messages I need it for an application server after kamailio. Finally I add contact to the message by ac_extra_hdrs of tm module with a p header. On Thu, May 11, 2023, 15:01 Henning Westerholt <hw(a)gilawa.com<mailto:hw@gilawa.com>> wrote: Hello, why you actually need to add the Contact header to the ACK? According to the RFC 3261 is should be an optional header to that message. Cheers, Henning -----Original Message----- From: James Browne <james(a)frideo.com<mailto:james@frideo.com>> Sent: Mittwoch, 10. Mai 2023 14:08 To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org>> Subject: [SR-Users] Re: where add contact header to ack for fail messages I made simple tests and it seems that this is a kamailio-TM-internal message being sent, not being processed by the cfg file. If this is simple enough and deterministic, you may consider using the corex module to edit the message as it's being sent "on the wire". I can't think of any other solution. https://kamailio.org/docs/modules/5.6.x/modules/corex.html#corex.evr.networ… You may be able to write some code that manipulates the message to manually add the Contact header. Maybe even the append_hf function may work here, but it seems unlikely. James On Mon, 8 May 2023 at 12:28, mohsen khashei <mkhashei(a)gmail.com<mailto:mkhashei@gmail.com>> wrote: > > thanks for the reply I tried it and it didn't work. also I tried onsend_route with no luck. > > On Sun, May 7, 2023 at 7:00 PM Yuriy G <ovoshlook(a)gmail.com<mailto:ovoshlook@gmail.com>> wrote: >> >> Try here >> https://www.kamailio.org/docs/modules/5.6.x/modules/tm.html#tm.e.loca >> l-request >> >> However I would doubt first do I do something right by adding contact to ACK message wichbasicaly confirmation of the final transaction and contact here is meaningless. >> >> On Sun, 7 May 2023, 16:48 mohsen khashei, <mkhashei(a)gmail.com<mailto:mkhashei@gmail.com>> wrote: >>> >>> Hi I want to know where kamailio sends ack messages to faiurel messages (status >=400) so that I I add Contact header to the ack. >>> I tried WITHINDLG with no luck. >>> thanks >>> __________________________________________________________ >>> Kamailio - Users Mailing List - Non Commercial Discussions To >>> unsubscribe send an email to sr-users-leave(a)lists.kamailio.org<mailto:sr-users-leave@lists.kamailio.org> >>> Important: keep the mailing list in the recipients, do not reply only to the sender! >>> Edit mailing list options or unsubscribe: >> >> __________________________________________________________ >> Kamailio - Users Mailing List - Non Commercial Discussions To >> unsubscribe send an email to sr-users-leave(a)lists.kamailio.org<mailto:sr-users-leave@lists.kamailio.org> >> Important: keep the mailing list in the recipients, do not reply only to the sender! >> Edit mailing list options or unsubscribe: > > __________________________________________________________ > Kamailio - Users Mailing List - Non Commercial Discussions To > unsubscribe send an email to sr-users-leave(a)lists.kamailio.org<mailto:sr-users-leave@lists.kamailio.org> > Important: keep the mailing list in the recipients, do not reply only to the sender! > Edit mailing list options or unsubscribe: __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-leave(a)lists.kamailio.org<mailto:sr-users-leave@lists.kamailio.org> Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:

1 0

using kamailio to send invite to webrtc clients (with freeswitch)
by shwetank singh 09 May '23

09 May '23

Hello experts I have a setup where webrtc client registrations (from behind a NAT / VPN) are on kamailio and the INVITE to begin a call is sent by freeswitch to kamailio which is then expected to relay it to the subscribed webrtc client. i understand, from documentation and general thinking, that kamailio cannot open a new connection to such a client and should reuse an open connection (a websocket in my case). i have setup kamailio as generic as it may sound and expect t_relay() to do the magic of forwarding the invite, however, from logs i don't see anything indicating kamailio is using any existing connection and hence my outgoing invite requests are stuck showing pointed towards a vpn gateway which was the registered "location" of client (which is the public ip of VPN gateway) please advise what relevant information can i produce here to make the query more readable and clear. headed here after trying just about all the resources available on the topic. e.g. if my location record looks like AoR: 1004(a)mydomain.com Contacts: - Contact: Address: sip:1004@11.22.33.44:49179 CFlags: 64 CSeq: 3087 Call-ID: 189jss21e24ntve1ggsuli Expires: 593 Flags: 0 Instance: <urn:uuid:8a936bbc-514f-4755-bed0-edc644dd4453> KA-Roundtrip: 0 Keepalive: 1 Last-Keepalive: 1683652755 Last-Modified: 1683652755 Methods: 7071 Path: <sip:10.10.6.196:3040;received=sip:mydomain.com ;lr;nat=yes> Q: -1 Received: sip:11.22.33.44:49179;transport=ws Reg-Id: 1 Ruid: uloc-645601c4-131220-3764 Server-Id: 0 Socket: tls:1.2.3.4:4443 State: CS_SYNC Tcpconn-Id: 3916 User-Agent: JsSIP 3.9.0 i try to lookup the location and find the address, and then route to that address by setting $ru in sngrep it does show that kamailio is trying to send INVITE to 11.22.33.44:port (which is the VPN gateway) but it isn't exactly clear from logs if this is being done over an existing connection. how does kamailio identify if a connection exists for a user (for each contact in AOR, if multiple contacts exist for a user -- i.e. different browser sessions?) if(reg_fetch_contacts("location", "$ru", "caller")) { $var(i) = 0; while($var(i) < $(ulc(caller=>count))) { $ru = $(ulc(caller=>addr)[$var(i)]); $var(i) = $var(i) + 1; setflag(FLT_DLGINFO); dlg_manage(); t_relay(); } } -- Shwetank

3 2

Performing async_http calls on stateless Loadbalancers
by Julius Flohr 09 May '23

09 May '23

Hi List, we are running several stateless SIP Loadbalancers using Kamaillio 5.1 and 5.6. Now we would like to perform an async_http request if an INVITE matches certain criteria. The request itself is performed very similar to how it's described here [1] This uses the transaction module in order to assure that the response can be mapped to the original request. However, this also means that the processing of the entire request becomes stateful which we would like to avoid. We tried to use t_release() in the callback route (in [1] this route is called "RELAY_API_RESPONSE"). However, documentation says that this is only allowed in the REQUEST_ROUTE. Is there an easy way to circumnavigate this issue? Cheers [1]: https://wazo-platform.org/blog/kamailio-routing-with-rtjson-and-http-async-… -- Julius Flohr - Voice Engineer - flohr(a)sipgate.de Telefon: +49 (0)211-63 55 55-0 Mobil: +49 (0)1579-000-0205 Telefax: +49 (0)211-63 55 55-22 sipgate GmbH - Gladbacher Str. 74 - 40219 Düsseldorf HRB Düsseldorf 39841 - Geschäftsführer: Thilo Salmon, Tim Mois Steuernummer: 106/5724/7147, Umsatzsteuer-ID: DE219349391 www.sipgate.de - www.sipgate.co.uk

3 3

Upgrade to 5.6.4 => [core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer
by Benoît Panizzon 08 May '23

08 May '23

Hi team I upgraded our lab to 5.6.4 from the official repository for ubuntu Jammy. Now I get crashes related to TLS: May 5 14:58:40 dev-cpereg01 kamailio[36147]: CRITICAL: <core> [core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer (0x7f4fedbed4e8), called from tls: tls_init.c: ser_free(323), first free tls: tls_init.c: ser_f ree(323) - ignoring May 5 14:58:40 dev-cpereg01 kamailio[36147]: CRITICAL: <core> [core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer (0x7f4fedd72b88), called from tls: tls_init.c: ser_free(323), first free tls: tls_init.c: ser_f ree(323) - ignoring May 5 14:58:40 dev-cpereg01 kamailio[36177]: CRITICAL: <core> [core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer (0x7f4fedd9e4a0), called from tls: tls_init.c: ser_free(323), first free tls: tls_init.c: ser_f ree(323) - ignoring May 5 14:58:40 dev-cpereg01 kamailio[36157]: CRITICAL: <core> [core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer (0x7f4fedd9e428), called from tls: tls_init.c: ser_free(323), first free tls: tls_init.c: ser_f ree(323) - ignoring And a bit later on: May 5 14:58:46 dev-cpereg01 kamailio[36179]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 34 May 5 14:58:46 dev-cpereg01 kamailio[36143]: ALERT: <core> [main.c:774]: handle_sigs(): child process 36161 exited by a signal 11 May 5 14:58:46 dev-cpereg01 kamailio[36143]: ALERT: <core> [main.c:777]: handle_sigs(): core was generated May 5 14:58:46 dev-cpereg01 kamailio[36143]: INFO: <core> [main.c:799]: handle_sigs(): terminating due to SIGCHLD Has there been a fundamental change in TLS? Or did I miss something important to do on a 5.5 => 5.6 upgrade? -- Mit freundlichen Grüssen -Benoît Panizzon- @ HomeOffice und normal erreichbar -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

4 5

TLS1.2 ciphers
by Sergiu Pojoga 05 May '23

05 May '23

Hi gang, Trying to figure out why Kamailio won't negotiate specific TLS1.2 ciphers, such as for example TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 i.e. *ECDHE-RSA-AES256-GCM-SHA384* OpenSSL lists the cipher as supported, however Kamailio won't negotiate it: # nmap --script ssl-enum-ciphers -p 5061 mysbc.domain.com PORT STATE SERVICE 5061/tcp open sip-tls | ssl-enum-ciphers: | TLSv1.2: | ciphers: | TLS_RSA_WITH_AES_256_GCM_SHA384 (rsa 2048) - A | TLS_RSA_WITH_AES_256_CBC_SHA256 (rsa 2048) - A | TLS_RSA_WITH_AES_256_CBC_SHA (rsa 2048) - A | TLS_RSA_WITH_CAMELLIA_256_CBC_SHA (rsa 2048) - A | TLS_RSA_WITH_AES_128_GCM_SHA256 (rsa 2048) - A | TLS_RSA_WITH_AES_128_CBC_SHA256 (rsa 2048) - A | TLS_RSA_WITH_AES_128_CBC_SHA (rsa 2048) - A | TLS_RSA_WITH_SEED_CBC_SHA (rsa 2048) - A | TLS_RSA_WITH_CAMELLIA_128_CBC_SHA (rsa 2048) - A | TLS_RSA_WITH_RC4_128_SHA (rsa 2048) - C | TLS_RSA_WITH_RC4_128_MD5 (rsa 2048) - C | TLS_RSA_WITH_3DES_EDE_CBC_SHA (rsa 2048) - C | compressors: | NULL | cipher preference: server | warnings: | 64-bit block cipher 3DES vulnerable to SWEET32 attack | Broken cipher RC4 is deprecated by RFC 7465 | Ciphersuite uses MD5 for message integrity |_ least strength: C OS: - outdated Debian 8 Jessie - OpenSSL 1.0.1t 3 May 2016 - openssl ciphers -v | grep '*ECDHE-RSA-AES256-GCM-SHA384*' - ECDHE-RSA-AES256-GCM-SHA384 TLSv1.2 Kx=ECDH Au=RSA Enc=AESGCM(256) Mac=AEAD # kamailio -V version: kamailio 5.5.6 (x86_64/linux) ad1244 flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLOCKLIST, HAVE_RESOLV_RES 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. compiled on 21:08:20 Apr 13 2023 with gcc 4.9.2 modparam("tls", "cipher_list", "ALL") method = TLSv1.2+ Elliptic Curve Diffie-Hellman (EDCH) <https://kamailio.org/docs/modules/devel/modules/tls.html#tls.compile>-Ciphers are only supported in OpenSSL 1.0.0e and later. Any suggestions? Thanks.

5 5

Using a second Perl library
by David Cunningham 04 May '23

04 May '23

Hello, We are using a product which already uses the "app_perl" module and sets the "filename" parameter to its own Perl library. However, we want to add more Perl code without having to modify that product's library. Does anyone know of a way to do this? To have Kamailio use Perl code from two different places? I guess in the worst case scenario we could use "app_python3", and have some Python code call subprocess.run() on the Perl code. Thanks very much, -- David Cunningham, Voisonics Limited http://voisonics.com/ USA: +1 213 221 1092 New Zealand: +64 (0)28 2558 3782

1 0

Development is open for future release of v5.8.x series
by Daniel-Constantin Mierla 04 May '23

04 May '23

Hello, the branch 5.7 was created, therefore the master branch is open for adding new features, to be part of future release series v5.8.x (or whatever version is decided for next series). Any bug fix committed to master that applies to 5.7.x or older stable branches should be backported as usual with "git cherry-pick -x ..." to appropriate branches like 5.7 or 5.6. Expect that v5.7.0 will be released in a few weeks from now. Based on the workflow used during the past years, the next future release v5.8.0 should be out after another 8-10 months of development, plus 1-2 months of testing, so sometime during the first part of 2024. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - June 5-7, 2023 - www.kamailioworld.com

1 0

Branch 5.7 has been created
by Daniel-Constantin Mierla 04 May '23

04 May '23

Hello, the branch 5.7 has been created, to be used for releasing v5.7.x series. To check out this branch, the following commands can be used: git clone https://github.com/kamailio/kamailio kamailio-5.7 cd kamailio-5.7 git checkout -b 5.7 origin/5.7 Pushing commits in this branch: git push origin 5.7:5.7 Note that 5.7 is an official stable branch, so only bug fixes, missing kemi exports (discuss on sr-dev if not sure) or improvements to documentation or helper tools can be pushed to this branch. As usual, if there is a bug fixed, commit and push first to master branch and then cherry pick to 5.7 branch: git cherry-pick -x COMMITID In few weeks, the first release from branch 5.7 will be out, respectively Kamailio v5.7.0. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - June 5-7, 2023 - www.kamailioworld.com

1 0

send reply from branch route?
by Benoit Panizzon 04 May '23

04 May '23

Hello Is there a possibility to send a reply from within a branch route? Experimental case (yes, I know it's a non working set-up, but I just wonder if that would be possible). Two registrar nodes, location information shared between the two. CPE registers via TLS, therefore the existing connection shall be used towards the CPE and that only exists on one of the registrars. So in the Branch Route I would like to do something like: $var(socket) = $(ulc(aor=>socket)[$T_branch_idx]); if ($var(socket) == 0) { send_reply("503","no local socket"); } This would cause the core routing instance to select the next registrar from the dispatcher list which hopefully holds the active socket. But none of the 'send_reply' variants seem to be allowed within a branch route. Or is there a better solution? Mit freundlichen Grüssen -Benoît Panizzon- -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

3 6

Branching 5.7 on git repo for 5.7.x releases
by Daniel-Constantin Mierla 04 May '23

04 May '23

Hello, I am planning to split 5.7.x series on its own git branch 5.7 on Thursday, May 4, 2023. After that, master branch will be open for new features (to become part of 5.8 or what ever version will be decided to be next). Usually testing should continue for branch 5.7 for another 1-2 weeks, then, if no relevant road blockers pop up, we should release 5.7.0 as first stable version in the 5.7.x series. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - June 5-7, 2023 - www.kamailioworld.com

1 1

uac.reg_add to database
by Jon Bonilla (Manwe) 04 May '23

04 May '23

Hi 5.6.4 I'm trying to add uacreg logic to my setup. When I add a new entry via rpc I see that the reg is stored in mem but not inserted in the database for persistency. My uac params are like this: modparam("uac", "reg_db_url",DBURL) modparam("uac", "reg_timer_interval", 900) modparam("uac", "reg_retry_interval", 10) modparam("uac", "reg_random_delay", 0) modparam("uac", "reg_hash_size", 12) ## 5.6 modparam("uac", "reg_db_table", "kam_uacreg") modparam("uac", "reg_contact_addr", "192.168.255.254:5060") #Won't be used #modparam("uac", "default_socket", "udp:192.168.0.125:5060") #Won't be used modparam("uac", "reg_keep_callid", 1) modparam("uac", "reg_active", 1) modparam("uac", "reg_gc_interval", 30) modparam("uac", "reg_use_domain", 0) I'm used to add via rpc and have db persistency. Like for exmaple using the domain module. Is this a bug in my config or does this module behave different? Should I insert in the db and call to enable via RPC? If so, what would be the best way to enable only the new inserted register instead of reloading all the regs? It's expected to have many changes and do not want to have full reloads all the time. cheers, Jon -- PekePBX, the multitenant PBX solution https://pekepbx.com

1 0

Kamailio - asterisk - ACK
by Péter Dr. Barabás 03 May '23

03 May '23

Hi all, we are developing a softphone mobile application which registers to asterisk through kamailio. Kamailo proxies the request to asterisk and replies from asterisk to the clients. Registration works fine with asterisk authentication. The problem appears in the following flow: 1. Mobile client A calls client B. 2. Asterisk gets INVITE through kamailo, sends back 401, and get INVITE with credentials. 3. Asterisk sends invite to client B towards kamailio. 4. Kamailio forwards INVITE if client is registered or sends a push notification to client B. When client B registers, kamailio continue the suspended transaction and forwards INVITE. 5. Client B gets INVITE, sends a SIP OK. 6. Asterisk gets SIP OK through kamailio and sends an ACK to client B, which is OK. 7. Asterisk sends the SIP OK to client A through kamailio. 8. Kamailio forwards SIP OK to client A but the contact address contains the asterisk IP instead kamailio. 9. Clilent A try to send ACK but it does not arrive to asterisk, and the call will be hungup after 30 secs. So the question is what is missing, what is the correct solution? I try to use the provided configuration given in following link: https://kb.asipto.com/asterisk:realtime:kamailio-4.0.x-asterisk-11.3.0-astdb The difference is that kamailio has no access to asterisk database. Thanks for your help. With kind regards, Peter

3 3

RFC: selective backports to latest stable as a dedicated git branch
by Daniel-Constantin Mierla 03 May '23

03 May '23

Hello, during past on-site/online devel meetings as well as on mailing lists or tracker, there were various discussions around the idea or requests to make new features available quicker to stable branches. Of course, one can do local git cherry-picking, but I thought to bring this in discussion and see if makes sense to get something more coordinated between developers and community. Therefore I am cross-posting to sr-dev and sr-users to see if there is interest for it from both communities. Somehow inspired from Debian, my first idea would be to create a "x.y-backports" branch, where "x.y" is the branch for the stable release series. For example, with 5.6 release series built from branch "5.6", there could be "5.6-backports" branch which is kept in sync in "5.6" but also can get "selected" new features from devel (master branch) backported. The "selected" new features should be mostly a matter of the people willing to put effort in backporting, but I would consider a list recommendations not to end up with devel and backports branches being more or less the same. For example, in the "no-backporting" list: - no backporting of completely new modules - no backporting of significant changes to the config file language and native scripting interpreter In the "ok-to-backport": - updates to enable use with newer versions of external libraries - changes to make some functions/modules to cope better with the core infrastructure or end points Commits to the backports branch can be proposed via pull requests. The backports branch should be done only for latest stable version, picking from the development version. Right now it would be 5.6, but we can wait till 5.7 is released and then have it for it. No packaging and no official releases should be made from backports branch, only a git branch to be maintained as a community effort. Of course, if someone wants to put more resources into it, we can discuss about. Anyhow, the first questions would be if such branch sounds good to have and if there are people that think they can also contribute to maintain it. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - June 5-7, 2023 - www.kamailioworld.com

3 2

Clarification of 'return false' behaviour
by Patrick Wakano 03 May '23

03 May '23

Hi list, Hope you are all well! I'm using Kamailio version 5.6.4 (installed from the repo rpm.kamailio.org/centos/7) and noticed that every route that uses "return false" is exiting the script, instead of returning.... This was not the case on version 5.4.6 as the same script is running fine..... From this page https://www.kamailio.org/wikidocs/tutorials/faq/main/#how-is-the-function-r…, I would think that when a route returns false, it would return -1 and not stop execution, since negative is equal to false, but it is actually stopping (same as return 0)... So, as an example, this test code doesn't work as expected. In case the source is a public IP, the script doesn't print the "SRC public" it just exits and then of course every other logic meant to be done is not executed.... route[is_src_private] { if (is_ip_rfc1918("$si")) { return true; } return false; #return is_ip_rfc1918("$si"); *# this doesn't work too in case the $si is a public IP* } request_route { ... if (route(is_src_private)) { xlog("L_NOTICE", "SRC private\n"); } else { xlog("L_NOTICE", "SRC public\n"); } ... } If is_src_private is changed to return -1 instead of false, then it all works fine. Also, I noticed that the following code will print "TEST: 0" in case the $si is public and then stop execution. So looks like false is really being converted to 0, but I guess that's unexpected... anyway apologies if I'm missing something obvious.... route[is_src_private] { $var(t) = false; if (is_ip_rfc1918("$si")) { $var(t) = true; } xlog("L_ERR", "TEST: $var(t)\n"); return $var(t); } I could not find a recent ticket or email related to this situation and I've already spent hours trying to understand what is the logic/problem here, so would anyone have been across a similar case that could provide some insight and clarify what is the expected behaviour of the *false* usage (and boolean in general if possible)? Thank you, Kind regards, Patrick Wakano

3 6

rtpengine module: sdp offer in message reply, ip protocol version not passed to rtpengine?
by Benoit Panizzon 02 May '23

02 May '23

Hi Team I think, I might have found something that was overseen in the rtpengine module. A (ipv6) <=> rtpengine <=> B (ipv4) Invite+SDP from B to A It looks like this works as expected. A SDP c= line is created containing an ipv6 address. Invite, no SDP from A to B Reply with SDP offer from B to A The information about A being reachable via ipv6 and therefore an ipv6 c= line being required, could be taken from the via header of the reply. But am I right to fear, that the rtpengine module does not do this at the moment? Mit freundlichen Grüssen -Benoît Panizzon- -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

2 2

Number if typical database connections
by Steve Wilkins 02 May '23

02 May '23

Hello, I moved the Kamailio database to RDS from a local instance and noticed that there were a large number of connections from the Kamailio user. What is the normal number of connection that can be expected? Thank you,

2 1

Rebooting kamailio.org server
by Daniel-Constantin Mierla 02 May '23

02 May '23

Hello, in about 1 hour the kamailio.org server will be rebooted for some system upgrades, it should be quickly back running, but if anyone accesses the web/wiki or mailing lists archives exactly during that time, they might not respond -- just wait for a minute and try again. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - June 5-7, 2023 - www.kamailioworld.com

1 0

Re: [SR-Users] TOPOS (5.1.[23]) breaks PRACK
by Daniel Tryba 02 May '23

02 May '23

On Mon, May 07, 2018 at 04:44:14PM +0200, Daniel Tryba wrote: > Sure. Attached. Problem appears to be that the topos query can't find > callid-totag (from the response). > > I'll try the same scenario with the mysql backend to see if it behaves > different. Config works fine with mysql as topos backend. So the bug is restricted to topos-redis.

5 19

Loading the LCR Module Tables at startup/reload
by harneet singh 30 Apr '23

30 Apr '23

Hi All, Can someone point to a sample as to how we can *load the LCR Module tables* namely the following at startup from a csv file or any other mechanism. * lcr_gw_table * lcr_rule_table * lcr_rule_target_table The idea is to not need to manually feed in the entries into the table but instead add these in the beginning through either a *wrapper script *OR *through the kamailio cfg file* if possible. Any pointers are much appreciated. Thanks & Regards, Harneet Singh -- "Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth" - Sir Arthur Conan Doyle

2 3

Route Header based routing for initial INVITE
by harneet singh 28 Apr '23

28 Apr '23

Hi Experts, I believe the loose_route() in kamailio can be used for initial Out of the dialog INVITE processing as well. Is that the correct understanding? If so, the request will be forwarded ahead to the destination corresponding to the Route Header remaining (if any) after Kamailio has stripped off it's own Address(es) from the Route Header(s). Is that correct? Regards, Harneet Singh -- "Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth" - Sir Arthur Conan Doyle

3 3

Strange RTCP issue
by Kiss Zoltán 27 Apr '23

27 Apr '23

Hello, We have a transparent proxy in front of Asterisk boxes. The media is handled by rtpengine, and the "manage" work is done by Kamailio in the route[NATMANAGE] section like this: if(nat_uac_test("8")) { # Packet from backend server if(ds_is_from_list()){ if (rtpengine_manage("replace-origin replace-session-connection direction=internal direction=pub")) { xdbg("NATMANAGE --- Success rtpengine_manage() RTP from INTERNAL to EXTERNAL $ru"); } } else { if (rtpengine_manage("replace-origin replace-session-connection direction=pub direction=internal")) { xdbg("NATMANAGE --- Success rtpengine_manage() RTP from EXTERNAL to INTERNAL $ru"); } } } else { # Packet from backend server if(ds_is_from_list()){ if (rtpengine_manage("replace-origin replace-session-connection trust-address direction=internal direction=pub")) { xdbg("NATMANAGE --- Success rtpengine_manage() RTP from INTERNAL to EXTERNAL $ru"); } } else { if (rtpengine_manage("replace-origin replace-session-connection trust-address direction=pub direction=internal")) { xdbg("NATMANAGE --- Success rtpengine_manage() RTP from EXTERNAL to INTERNAL $ru"); } } } Everything is working fine, but with some clients (like Grandstream phone) the RTCP session wants to go tot he private address of the phone. Here is the log of one of these strange calls: Apr 27 16:54:38 rtp1 rtpengine[2273]: INFO: [312ed76c31f21b71452e91e5184ad25b@172.16.2.210:5060]: [core] --------- Port 178.238.213.14:11088 <> 81.183.216.3:5068 , SSRC 77c19488, 625 p, 107500 b, 0 e, 29 ts Apr 27 16:54:38 rtp1 rtpengine[2273]: INFO: [312ed76c31f21b71452e91e5184ad25b@172.16.2.210:5060]: [core] --------- Port 178.238.213.14:11089 <> 10.0.5.192:5069 (RTCP), SSRC 0, 0 p, 0 b, 0 e, 43 ts As you can see the RTP itself is okay, but the RTCP will somehow go to the private address. If we tracing the sdp messages in sngrep, then we can see that Kamailio transforming IP addresses for the backend servers to the public (and the private address of the rtpengine) addresses. We are missing something? Thank you! With kind regards, Zoltan

2 1

Sensible values for pike mudule?
by Benoit Panizzon 27 Apr '23

27 Apr '23

Hi Before I go too deep into try and error, I guess others have been there too. What are sensible value you use for the pike module to detect / mitigate abusive behavior, especially dictionary attacks? Are there better solutions that the pike module? Mit freundlichen Grüssen -Benoît Panizzon- -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

2 1

Fwd: Sensible values for pike mudule?
by Stefan 27 Apr '23

27 Apr '23

Hi Benoît We use pike in combination with fail2ban. Log a message -> create a fail2ban rule to block the ip for xxx time. example: if ($ua =~ "(friendly-scanner|sipvicious)") { sl_send_reply("488", "Go away."); xlog("L_INFO","$ci Blocking traffic from $si\n"); exit; } Cool thing is, you can write a log entry from every part in your kamailio-config, and then fail2ban does the rest. Regards Stefan Am 27.04.23 um 16:07 schrieb Benoit Panizzon: > Hi > > Before I go too deep into try and error, I guess others have been there > too. > > What are sensible value you use for the pike module to detect / > mitigate abusive behavior, especially dictionary attacks? > > Are there better solutions that the pike module? > > Mit freundlichen Grüssen > > -Benoît Panizzon-

1 0

hooking mechanism for routing blocks
by Valentin Christoph 27 Apr '23

27 Apr '23

Dear all, I am looking for some hooking mechanism for user defined routing blocks. Is something like this already available? 1) a common part of the routing configuration shall not (or only slightly) be changed, after some hooks have been implemented Something like a function "engage_hooks()" of some "hook_module"? : Routing config that should not be changed by application developers engage_hooks(HOOK_TYPE); Routing config that should not be changed by application developers : 2) one application developer may "hook" new parts of the routing configuration into this, by modparam("hook_module", "hook", "name=MY_RB;type=HOOK_TYPE;prio=50); : : Route [MY_RB] { Do something at hook HOOK_TYPE; } : : 3) another application developer might want to "hook" into the same HOOK_TYPE with a higher priority modparam("hook_module", "hook", "name=ANOTHER_RB;type=HOOK_TYPE;prio=20); : : Route [ANOTHER_RB] { Do another thing with higher priority at hook HOOK_TYPE } : : Kr, Christoph

2 2

Kamailio use case
by jdprsaga＠gmail.com 26 Apr '23

26 Apr '23

Hello All, new subscriber here. I've been reading kamailio documentation to check if kamailio has a use case on the architecture for the solution for my company's software, here an small architecture diagram of our solution. sipclient <----> [ Middleware ] <-----> SBC Our middle ware is both a sip proxy and media proxy. we have a large number of sip clients but a small calling number, our current bottleneck is that the middleware can't handle a high number of registration, i would like to deploy Kamailio as a load balancer for registrations, making sure it is statefull so registrations and calls are hashed into the same middleware server. sipclients < ----> [ kamailio ] <------> [ middleware1, middleware2,...,middleware N] <-----> SBC Any thoughts or pointers?

4 3

rtpengine module: Actions caused by rtpengine_manage() on reply-codes?
by Benoît Panizzon 26 Apr '23

26 Apr '23

Hi all I wonder, if there is a documentation on what action is performed by rtpengine_manage() on which kind reply. Am I right, that rtpengine_manage(), on any 4XX reply causes a delete? So if there is a re-invite (for example to switch to T.38) and the other party replies with 488 which in turn is passed through rtpengine_manage() the existing RTP stream is deleted from rtpengine instead of being left running with the previously agreed codec? Has anyone already figured out a list of what reply codes should be exempt from calling rtpengine_manage()? -- Mit freundlichen Grüssen -Benoît Panizzon- @ HomeOffice und normal erreichbar -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

8 12

Configuring dynamic Destination identification for Kamailio Routing
by harneet singh 25 Apr '23

25 Apr '23

Hi Experts, We have been using Kamailio as a sip proxy for a fair bit of time now(version 5.3.2 though) and do understand the native routing mechanism that can be instrumented through the kamailio cfg scripts. We initially had only two sides, where the traffic could come from into Kamailio and it just passed through to the other side(ie Traffic from A was routed to B and that from B was routed to A). Off late, a few more sip elements have been introduced in the deployment and now there is a need for a more formal/robust mechanism to select the intended destination to forward an initial SIP INVITE to. I believe that we could still keep all the logic in the native kamailio script and do the routing(for example, an incoming call where the *From URI* contains *sip.elementA.com <http://sip.elementA.com>* should be routed to destination *sip.elementB.com <http://sip.elementB.com>*, where as if the* To URI *contains *sip.elementC.com <http://sip.elementC.com>*, the request should be routed to *sip.elementC.com <http://sip.elementC.com>)**. *Since we have many sip elements like A,B.C,D,E etc where the requests might have to be routed to, based on certain different criteria, this logic would become cumbersome. *What would be the best way to accommodate this?* *Would it be possible to rewire this routing logic at runtime(*like in some csv file that can be reloaded*) without a Kamailio restart? * Regards, Harneet Singh -- "Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth" - Sir Arthur Conan Doyle

3 5

sips to sip with TLS proxy
by Kiss Zoltán 25 Apr '23

25 Apr '23

Hi all, We have a working Kamailio setup, lets call it a transparent proxy for Asterisk boxes. Its based on domain and dispatcher modules and everything is working as expected with the test clients (more or less microsip, softphone for ios, etc). We are tried to register with a Grandstream deskphone today, and we see that the phone sending sips:xxx in the Reg Contact field for example. Because the sips schema, the register is working, but we cannot initiate calls from this phone. If we are turning SIP scheme to sip from sips in the phone, then everything is working as expected. I think we can transform those requests from sips to sip with Kamailio, but currently we dont know where can we start. Has anybody a suggestion about this issue? I know that we can transform ruri, contact, etc with textops, nathelper and a lot of other modules, but what is the best for this sips->sip translation? Thanks for your help. With kind regards, Zoltan

4 10

TCP/TLS connection (id: 0) for WebSocket could not be found
by Joey Golan 22 Apr '23

22 Apr '23

Hello, I have 2 clients. 1 using websocket and 1 mobile using TLS. Both can call each other perfectly. After 24-48 hours calls from mobile to websocket failed with an error message: TCP/TLS connection (id: 0) for WebSocket could not be found. At the same time I can make calls from the websocket client to the mobile. I know that the search of the connection is done by target address so I printed the addresses + ports and they are matched to the ones that appear on the ul.dump and ws.dump. *kamcmd ul.dump output:* Info: { AoR: usrmt63ly_1040 HashID: 1830036546 Contacts: { Contact: { Address: sip:usrmt63ly_1040@example.com;transport=ws Expires: 283 Q: -1 Call-ID: tvne1pskgkm2a01pnqm677 CSeq: 1060 User-Agent: JsSIP 3.9.0 Received: sip:*10.218.51.86:24061 <http://10.218.51.86:24061>*;transport=ws Path: <sip:10.218.154.228:50443;transport=ws;received=sip:*10.218.51.86:24061 <http://10.218.51.86:24061>*;transport=ws;lr> State: CS_NEW Flags: 0 CFlags: 64 Socket: tls:10.218.154.228:50443 Methods: 7071 Ruid: uloc-61ebba84-64242101-89ba-1 Instance: <urn:uuid:7573726d-7436-116c-915f-313034304077> Reg-Id: 1 Server-Id: 1642838660 Tcpconn-Id: 100420 Keepalive: 1 Last-Keepalive: 1680417282 KA-Roundtrip: 0 Last-Modified: 1680417282 } } } *kamcmd ws.dump* { connections: { 100420: wss:*10.218.51.86:24061 <http://10.218.51.86:24061>* -> wss: 10.218.154.228:50443 (state: OPEN, last used 14s ago, sub-protocol: sip) } info: { wscounter: 1 truncated: no } } *Call from mobile (TLS) to websocket: Failed with error message: TCP/TLS connection (id: 0) for WebSocket could not be found* 30(35263) INFO: {1 2563 INVITE 4248c155-cd92-49b8-b68a-eef5f2cb3e88} <script>: request_route: method [INVITE] from [ sip:usrrcv4o4_1040@example.com] socket [sip:10.218.51.86:50909;transport=tls] to [sip:usrmt63ly_1040@example.com] 30(35263) INFO: {1 2563 INVITE 4248c155-cd92-49b8-b68a-eef5f2cb3e88} <script>: [RELAY]: method [INVITE] from [sip:usrrcv4o4_1040@example.com] socket [sip:10.218.51.86:50909;transport=tls] to [ sip:usrmt63ly_1040@example.com] socket [sip:*10.218.51.86:24061 <http://10.218.51.86:24061>*;transport=ws] 30(35263) WARNING: {1 2563 INVITE 4248c155-cd92-49b8-b68a-eef5f2cb3e88} <core> [core/msg_translator.c:2863]: *via_builder(): TCP/TLS connection (id: 0) for WebSocket could not be found* 30(35263) ERROR: {1 2563 INVITE 4248c155-cd92-49b8-b68a-eef5f2cb3e88} <core> [core/msg_translator.c:2040]: build_req_buf_from_sip_req(): could not create Via header 30(35263) ERROR: {1 2563 INVITE 4248c155-cd92-49b8-b68a-eef5f2cb3e88} tm [t_fwd.c:479]: prepare_new_uac(): could not build request 30(35263) ERROR: {1 2563 INVITE 4248c155-cd92-49b8-b68a-eef5f2cb3e88} tm [t_fwd.c:1759]: t_forward_nonack(): failure to add branches 30(35263) ERROR: {1 2563 INVITE 4248c155-cd92-49b8-b68a-eef5f2cb3e88} sl [sl_funcs.c:418]: sl_reply_error(): stateless error reply used: No error (2/SL) 30(35263) NOTICE: {1 2563 INVITE 4248c155-cd92-49b8-b68a-eef5f2cb3e88} acc [acc.c:287]: acc_log_request(): ACC: call missed: timestamp=1680417920;method=INVITE;from_tag=e168ffa6-e577-48ec-b9c9-a73f5be318e8;to_tag=0c3e625e9f223a7ee2b093e8e31b2526-b7165bcb;call_id=4248c155-cd92-49b8-b68a-eef5f2cb3e88;code=500;reason=Server Internal Error;src_user=usrrcv4o4_1040;src_domain=example.com ;src_ip=10.218.51.86;dst_ouser=usrmt63ly_1040;dst_user=usrmt63ly_1040;dst_domain= example.com *Call from websocket to mobile (TLS):* 38(35271) INFO: {1 7488 INVITE urcnete8r71dpkhmngd8} <script>: request_route: method [INVITE] from [sip:usrmt63ly_1040@example.com] socket [sip:*10.218.51.86:24061 <http://10.218.51.86:24061>*;transport=ws] to [ sip:usrrcv4o4_1040@example.com] 38(35271) INFO: {1 7488 INVITE urcnete8r71dpkhmngd8} <script>: [RELAY]: method [INVITE] from [sip:usrmt63ly_1040@example.com] socket [sip:*10.218.51.86:24061 <http://10.218.51.86:24061>*;transport=ws] to [ sip:usrrcv4o4_1040@example.com] socket [sip:10.218.51.86:20674 ;transport=tls] 39(35272) INFO: {2 7488 INVITE urcnete8r71dpkhmngd8} <script>: onreply_route[MANAGE_REPLY] method [INVITE] code [100] from [ sip:usrmt63ly_1040@example.com] to [sip:usrrcv4o4_1040@example.com] 39(35272) INFO: {2 7488 INVITE urcnete8r71dpkhmngd8} <script>: onreply_route[MANAGE_REPLY] method [INVITE] code [200] from [ sip:usrmt63ly_1040@example.com] to [sip:usrrcv4o4_1040@example.com] 39(35272) NOTICE: {2 7488 INVITE urcnete8r71dpkhmngd8} acc [acc.c:287]: acc_log_request(): ACC: transaction answered: timestamp=1680417926;method=INVITE;from_tag=18q0p37nfo;to_tag=a88272a0-25ca-43c2-8ce9-8615831b7e9a;call_id=urcnete8r71dpkhmngd8;code=200;reason=OK;src_user=usrmt63ly_1040;src_domain= example.com ;src_ip=10.218.51.86;dst_ouser=usrrcv4o4_1040;dst_user=usrrcv4o4_1040;dst_domain=10.218.51.86 38(35271) INFO: {1 7488 ACK urcnete8r71dpkhmngd8} <script>: request_route: method [ACK] from [sip:usrmt63ly_1040@example.com] socket [sip:*10.218.51.86:24061 <http://10.218.51.86:24061>*;transport=ws] to [ sip:usrrcv4o4_1040@example.com] 38(35271) INFO: {1 7488 ACK urcnete8r71dpkhmngd8} <script>: [RELAY]: method [ACK] from [sip:usrmt63ly_1040@example.com] socket [sip:*10.218.51.86:24061 <http://10.218.51.86:24061>*;transport=ws] to [ sip:usrrcv4o4_1040@example.com] socket [sip:10.218.51.86:20674 ;transport=tls] *Version: kamailio 5.6.2 (x86_64/linux)* What could be the reason for that? Your help would be much appreciated. Thanks, Joey.

3 4

How to log expiring dialogue?
by Benoît Panizzon 21 Apr '23

21 Apr '23

Hi alle I think I have an issue with the dialogue and session timer module with Kamailio 5.4 I sync the Session Expire Timer with the dialogue timeout via a common AVP. When I check a dialogue via kamcmd dlg.list start_ts: 1682066352 init_ts: 1682066346 end_ts: 0 timeout: 1682066952 lifetime: 600 Timeout is increased on the first session refreshing re-invite, as expected (in this case after 300 seconds). But it looks like the dialogue just disappears (from kamcmd dlg.list, not from the backing database) when the lifetime ist reached, leaving an orphan database entry. I would like to digg deeper into this. Is there a way to log more details from the dialogue module like when it triggers dialogue expiry? -- Mit freundlichen Grüssen -Benoît Panizzon- @ HomeOffice und normal erreichbar -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

2 2

Roadmap to next major release series v5.7.x
by Daniel-Constantin Mierla 20 Apr '23

20 Apr '23

Hello, it is time to make the roadmap to the next major release series v5.7.x. In my opinion, I would try to freeze the development during the first part of April 2023, tentatively proposing April 14 as freezing date, being like 4 weeks from now. Then testing phase and first release (v5.7.0) sometime during May 2023. Alternative timelines can be proposed, of course. If anyone wants to add new features/modules, they have to be published till freezing date, either pushed in the git repository or proposed as pull request. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - June 5-7, 2023 - www.kamailioworld.com Kamailio Advanced Training - Online - March 27-30, 2023 - www.asipto.com

3 5

Rtpengine: no audio after kernelization.
by Michel Pelletier 17 Apr '23

17 Apr '23

Hello, I am proxying all RTP through RTPEngine. Everything works fine until about 5 seconds into the call, when rtpengine enters kernelization, after which all RTP forwarding ceases. I've checked the required iptables entries, and all looks good. Here is a description of my environment: # cat os-release PRETTY_NAME="Debian GNU/Linux 11 (bullseye)" NAME="Debian GNU/Linux" VERSION_ID="11" VERSION="11 (bullseye)" VERSION_CODENAME=bullseye ID=debian HOME_URL="https://www.debian.org/" SUPPORT_URL="https://www.debian.org/support" BUG_REPORT_URL="https://bugs.debian.org/" # kamailio -v version: kamailio 5.6.2 (x86_64/linux) 54a9c1 flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLOCKLIST, HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED ADAPTIVE_WAIT_LOOPS 1024, MAX_RECV_BUFFER_SIZE 262144, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: 54a9c1 compiled on 16:02:49 Dec 1 2022 with gcc 10.2.1 # rtpengine -v Version: 11.1.1.3-1~bpo11+1 Michel Pelletier

4 13

Docker repository removed
by Manel Villar 17 Apr '23

17 Apr '23

Hi, I was using the kamailio/kamailio docker repository in one of my projects, and now the image is not available as the repo has been removed. Is the "kamailio-ci" repo a replacement for it? Thanks! -- Manel Villar Steegerstr. 59 13359 Berlin Germany Tel: (+49) (0)162 6574604 skype: manel.villar manelvf(a)gmail.com *"Ars longa, vita brevis"*

4 5

Development for v5.7.x is frozen
by Daniel-Constantin Mierla 17 Apr '23

17 Apr '23

Hello, the formal notification that the development for the next major version 5.7.0 is now frozen. The focus has to be on testing the master branch. Also, the master branch should not get commits with new features till the branch 5.7 is created, expected to happen in 2-4 weeks, a matter of how testing goes on. Meanwhile, the commits with new features in the C code can be pushed to personal branches, new pull requests can still be done, but they will be merged after branching 5.7. Can still be done commits with documentation improvements, enhancements to related tools (e.g., kamctl, kamcmd), merging exiting pull requests at this moment, exporting missing KEMI functions and completing the functionality of the new modules added for 5.7. Once the branch 5.7 is created, new features can be pushed again to master branch as usual. From that moment, the v5.7.0 should be out very soon, time used for further testing but also preparing the release of packages. If someone is not sure if a commit brings a new feature, just make a pull request and it can be discussed there on github portal or via sr-dev mailing list. A summary of what is new in upcoming 5.7 is going to be built at: * https://www.kamailio.org/wikidocs/features/new-in-5.7.x/ Upgrade guidelines will be collected at: * https://www.kamailio.org/wikidocs/install/upgrade/5.6.x-to-5.7.0/ Everyone is more than welcome to contribute to the above wiki pages, especially to the upgrade guidelines, to help everyone else during the migration process from v5.6.x to 5.7.x. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

2 2

Assigning a new RTPEngine for a call for the sake of failover
by mehdithreem+kamailio＠gmail.com 15 Apr '23

15 Apr '23

Hello, I am trying to implement RTPEngine failover, where if a selected RTPEngine node fails in the middle of the call (and not responding NG requests), I want to select an alternative node. However, when I call rtpengine_manage(), it does not seem to select an alternative node in case of a failure. To address this, I have attempted to check if $avp(RTP_INSTANCE) is null after calling rtpengine_manage(), and then use rtpengine_delete() to forget the selected RTPEngine node for the specific call, with the expectation that Kamailio would assign a new RTPEngine node for subsequent SIP message retries. However, it appears that rtpengine_delete() does not have the desired effect in this regard. Here is an excerpt of my code for reference: ``` route[RTP] { #!ifdef WITH_RTPENGINE if (has_body("application/sdp")) { if ($avp(x_source) == "INTERNAL") { rtpengine_manage("replace-session-connection replace-origin direction=internal direction=external"); } else if ($avp(x_source) == "EXTERNAL") { rtpengine_manage("replace-session-connection replace-origin direction=external direction=internal"); } if ($avp(RTP_INSTANCE) == $null) { rtpengine_delete(); drop(); } } #!endif } ``` Can you please advise on how I can achieve the desired failover behavior? Is there another function similar to `rtpengine_reset_call` that can make Kamailio forget the RTPEngine node for a specific call? Thank you!

2 1

CLI & destination based LCR
by John Cahill 14 Apr '23

14 Apr '23

Hi, I'd like to build an LCR solution that routes on both CLI & destination e.g. CLI matches ^\+49*, destinations matches ^\+44* => route to gateway 5 for a large rule set (~ tens of thousands). Any recommendations for which modules to use? Can kamailio perform this particular task well or should I look at another solution? I'd be very grateful to hear about any experience of doing this. Many Thanks. Regards, John

5 5

Kamailio + PostgreSQL
by georgy.grigoryev＠snapcom.fr 14 Apr '23

14 Apr '23

Hello everyone, I'm trying to connect Kamailio 5.5.5 to my PostgreSQL 14. They are on two different servers. I have created the Kamailio DB on the Postgre with the help of the command "kamdbctl create" I'm able to connect to the database with no problem. The problem is in the kamailio.cfg file, i have added this so far: #!define WITH_PGSQL #!ifdef WITH_PGSQL #!define DBURL "postgres://USER:PASSWORD@IP:POPT/kamailio" #!endif #!ifdef WITH_PGSQL loadmodule "db_postgres.so" #!endif modparam("db_postgres", "retries", 3) modparam("db_postgres", "timeout", 10) modparam("db_postgres", "tcp_keepalive", 600) modparam("db_postgres", "lockset", 6) modparam("db_postgres", "bytea_output_escape", 0) But my kamailio doenst like this configuration, can someone help me find the problem? Thank you in advance! Best Regards!

3 2

manipulate Authentication header
by David Villasmil 13 Apr '23

13 Apr '23

Hello guys, I can't find a simple way of changing the username and recalculate the has in a REGISTER... do i have to use textops? Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337

2 1

How to correctly use the SST module?
by Benoît Panizzon 11 Apr '23

11 Apr '23

Hi I still have odd behaviour with the SST module: modparam("sst", "min_se", 300) if (sstCheckMin("1")) { xlog("L_ERR", "$cfg(route) Session Timer too small\n"); exit; } setflag(FLT_DLG); # set the dialog flag setflag(FLT_SST); # Set the sst flag if(is_present_hf("Session-Expires")) { $avp(dlgtimeout) = $(hdr(Session-Expires){s.int}); } On an INVITE containing those header: Session-Expires: 3600;refresher=uac Min-SE: 600 Supported: 100rel,timer Expires: 330 Now Kamailio replies: SIP/2.0 422 Session Timer Too Small Min-SE: 300 What am I doing wrong? -- Mit freundlichen Grüssen -Benoît Panizzon- @ HomeOffice und normal erreichbar -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

1 0

dlg_onroute(): unable to find dialog for INVITE with route param
by Benoît Panizzon 10 Apr '23

10 Apr '23

Happy Eastern Kamailio 5.4 used. On dialogues calls, I noticed this happening on the second re-invite to refresh the session from the B side. dlg_onroute(): unable to find dialog for INVITE with route param 'df9.da75' [2557:22445] and call-id '14148a68-f1b2-485d-b5a2-f9dd7773d2c0' The did df9.da75 is identical to the one in the route-header on the first re-invite from the B side, before this one. No CDR was (yet) generated, and the dialogues is still present and on-going according to the database: CallID [14148a68-f1b2-485d-b5a2-f9dd7773d2c0] H-Entry: 2557 H-ID: 22445 But most probably not in memory as kamcmd dlg.stat_active shows zero (this is on a development node, so no other calls running). There are no sip messages that end the call in between those two re-invites. I see no session timeouts or similar in the logs. Any hint what could cause Kamailio not to find the corresponding dialogue on this re-invite? -- Mit freundlichen Grüssen -Benoît Panizzon- @ HomeOffice und normal erreichbar -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

1 2

Fwd: Kamailio + PostgreSQL
by Stefan 07 Apr '23

07 Apr '23

Hi Give it a try without modparams to see if it works, I have the same config but without modparams and it runs without problems. Else have a look into the kamailio logfile for errors. Or check config with "kamailio -c"? Regards Stefan Am 06.04.23 um 15:18 schrieb georgy.grigoryev(a)snapcom.fr: > Hello everyone, > > I'm trying to connect Kamailio 5.5.5 to my PostgreSQL 14. > They are on two different servers. > I have created the Kamailio DB on the Postgre with the help of the > command "kamdbctl create" > I'm able to connect to the database with no problem. > The problem is in the kamailio.cfg file, i have added this so far: > > #!define WITH_PGSQL > > #!ifdef WITH_PGSQL > #!define DBURL "postgres://USER:PASSWORD@IP:POPT/kamailio" > #!endif > > #!ifdef WITH_PGSQL > loadmodule "db_postgres.so" > #!endif > > modparam("db_postgres", "retries", 3) > modparam("db_postgres", "timeout", 10) > modparam("db_postgres", "tcp_keepalive", 600) > modparam("db_postgres", "lockset", 6) > modparam("db_postgres", "bytea_output_escape", 0) > > But my kamailio doenst like this configuration, can someone help me > find the problem? > > Thank you in advance! > > Best Regards! > __________________________________________________________ > Kamailio - Users Mailing List - Non Commercial Discussions > To unsubscribe send an email to sr-users-leave(a)lists.kamailio.org > Important: keep the mailing list in the recipients, do not reply only > to the sender! > Edit mailing list options or unsubscribe:

2 2

Malformed To Header
by Serdar GUCLUER 06 Apr '23

06 Apr '23

Hello all, In my situation, it is possible to call forwarding to registered users multiple times on same leg. For each forward i have to update To uri and i am using uac_replace_to to do that. But on second relaying, To uri was malformed. On below, Im attaching configuration to illustrate my problem. (version-5.4.9) First relay - /To: //sip:xyz@192.168.0.51/ Second relay - /To: sip:xyz@192.168.0.51sip:abc@192.168.0.51/ Thanks in advance. Serdar /loadmodule "uac.so"// //modparam("uac","restore_mode","auto")// // // //request_route {// // ...// // $avp(x) = "abc";// // $avp(x) = "xyz";// // $avp(myip) = "192.168.0.51";// // $avp(i) = 0;// // route(SERDAR);// // ...// //}// // //route[SERDAR] {// // if ($(avp(x)[$avp(i)])!=$null) {// // $avp(destination) = $(avp(x)[$avp(i)]);// // $avp(i) = $avp(i) + 1;// // $rU=$_s($avp(destination));// //uac_replace_to("$_s(sip:$avp(destination)@$avp(myip))");// // route(LOCATION);// // } else {// // send_reply("403", "Opps!");// // exit;// // }// //}// // //route[LOCATION] {// // $avp(oexten) = $rU;// // if (!lookup("location") ) {// // t_newtran();// // switch ($var(rc)) {// // case -1:// // case -3:// // send_reply("480", "Temporarily Unavailable");// // exit;// // case -2:// // send_reply("405", "Method Not Allowed");// // exit;// // }// // }// // t_on_failure("SERDAR_FAILURE");// // if(!t_relay()) sl_reply_error();// // exit;// //}// // //failure_route[SERDAR_FAILURE] {// // route(NATMANAGE);// // if (t_is_canceled()) //exit;// // route(SERDAR);// //}/

6 11

Presence module and privacy
by Ihor Olkhovskyi 06 Apr '23

06 Apr '23

Hello! Is there any possibility to control more-or-less privacy related parameters of pua_dialoginfo module (like include_localremote) per subscription? Main idea is I want to show some users full info on the call other user is making, for a different user - just show fact of the call without any details. For now I'm only seeing some manual manipulation over XML based on user who is receiving NOTIFY, but maybe I'm trying to invent a weel here. -- Best regards, Ihor (Igor)

2 2

Re: Repository for modules
by Henning Westerholt 06 Apr '23

06 Apr '23

(please keep the list in the communication) Hello, you can find the modules for example in the Debian package service: https://packages.debian.org/bullseye/amd64/kamailio-tls-modules/filelist Crypto is in TLS module package. Cheers, Henning From: Duarte Rocha <duarterocha91(a)gmail.com> Sent: Donnerstag, 6. April 2023 15:42 To: Henning Westerholt <hw(a)gilawa.com> Subject: Re: [SR-Users] Repository for modules Thanks for the quick answer. How can I see info regarding which modules are in the combined packages? One of the modules i'm looking into is the crypto module for example. Otherwise, where can I get a list of modules not included in Debian packages? Cheers, Duarte Henning Westerholt <hw(a)gilawa.com<mailto:hw@gilawa.com>> escreveu no dia quinta, 6/04/2023 à(s) 13:17: Hello, the majority of modules should be packaged for Debian. What modules are missing for you? Keep in mind that some modules are combined in some packages. Some modules can not properly packaged due to missing dependencies, this needs to be installed from source, right. Cheers, Henning From: Duarte Rocha <duarterocha91(a)gmail.com<mailto:duarterocha91@gmail.com>> Sent: Donnerstag, 6. April 2023 13:55 To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org>> Subject: [SR-Users] Repository for modules Hello, I'm currently testing Kamailio on a Debian 11 machine. In order to install it I used apt with repositories from Kamailio (https://deb.kamailio.org/). Now I'm trying to add modules and I'm wondering the best way to do it. Using apt install i don't have access to all the modules. Is there another repository for this? Is my only solution downloading and compiling the modules? Cheers

1 0

Repository for modules
by Duarte Rocha 06 Apr '23

06 Apr '23

Hello, I'm currently testing Kamailio on a Debian 11 machine. In order to install it I used apt with repositories from Kamailio (https://deb.kamailio.org/). Now I'm trying to add modules and I'm wondering the best way to do it. Using apt install i don't have access to all the modules. Is there another repository for this? Is my only solution downloading and compiling the modules? Cheers

2 2

issue in kamailio of udp
by satyaprakash ch 06 Apr '23

06 Apr '23

Hi, I had upgraded Kamailio from 5.4.7 to 5.5.5, Then I restarted the Kamailio service. After upgradation im getting the below error, /usr/local/sbin/kamailio[21754]: ERROR: <core> [core/udp_server.c:596]: udp_send(): sendto(sock, buf: 0x7f7502289200, len: 61012, 0, dst: ( 10.122.45.189:5080), tolen: 16) - err: No buffer space available (105) /usr/local/sbin/kamailio[21754]: ERROR: tm [../../core/forward.h:231]: msg_send_buffer(): udp_send failed /usr/local/sbin/kamailio[21754]: ERROR: tm [uac.c:678]: send_prepared_request_impl(): Attempt to send to precreated request failed ERROR: tm [../../core/forward.h:231]: msg_send_buffer(): udp_send failed ERROR: tm [uac.c:678]: send_prepared_request_impl(): Attempt to send to precreated request failed Anyone have any idea on this errors.

2 3

SCSCF hangs randomly
by solomon.thoobe＠smilecoms.com 05 Apr '23

05 Apr '23

Hi All, We currently experience issues where scscf hangs randomly throughout the day. It started hanging once in a month, the issue has gotten worse over time and now it can hang more than 5 times in a day. I have no prior kamailio experience or experience debugging c applications. Kamailio version: 4.4.0 Running ps shows scscf processes are running. Service status also shows scscf is running but it does not respond to sip requests. Testing with sipsack hangs and print timeout errors. root@NGVI-PCSCF2:/var/log # service scscf status * Status of Kamailio SIP Server: * scscf is running sipsak -vv -s sip:NGVI-PCSCF2:6060 received ICMP message received ICMP message** timeout after 500 ms** Below is the extract from log files Apr 5 12:04:46 NGVI-PCSCF2 /usr/sbin/kamailio[5102]: {1 1 ACK isbc505ramjjjr3g23cs02r53cms0uxbg2es(a)10.18.5.64} WARNING: tm [t_lookup.c:1476]: t_unref(): WARNING: script writer didn't release transaction Apr 5 12:04:46 NGVI-PCSCF2 /usr/sbin/kamailio[5104]: {1 3 REGISTER _A9LGREyW2miE7LhPJzv7g..} ERROR: ims_registrar_scscf [save.c:1034]: update_contacts(): Unable to remove contact <sip:+2347020246874@154.66.2.182:5060;rinstance=28bf37d2cce6e4a1;transport=udp> Apr 5 12:04:47 NGVI-PCSCF2 /usr/sbin/kamailio[5131]: ERROR: rr [rr_mod.c:300]: w_record_route(): Double attempt to record-route Apr 5 12:04:47 NGVI-PCSCF2 /usr/sbin/kamailio[5144]: ERROR: rr [rr_mod.c:300]: w_record_route(): Double attempt to record-route Apr 5 12:04:47 NGVI-PCSCF2 /usr/sbin/kamailio[5108]: {1 1 ACK r8ug398d118i8iaaunrouggisntkigkn(a)10.18.5.64} WARNING: tm [t_lookup.c:1476]: t_unref(): WARNING: script writer didn't release transaction Apr 5 12:04:48 NGVI-PCSCF2 /usr/sbin/kamailio[5190]: CRITICAL: <core> [pass_fd.c:275]: receive_fd(): EOF on 23 Apr 5 12:04:48 NGVI-PCSCF2 /usr/sbin/kamailio[5062]: ALERT: <core> [main.c:741]: handle_sigs(): child process 5103 exited by a signal 11 Apr 5 12:04:48 NGVI-PCSCF2 /usr/sbin/kamailio[5062]: ALERT: <core> [main.c:744]: handle_sigs(): core was generated Apr 5 12:06:12 NGVI-PCSCF2 kamailio: WARNING: <core> [daemonize.c:348]: daemonize(): pid file contains old pid, replacing pid Apr 5 12:06:13 NGVI-PCSCF2 /usr/sbin/kamailio[15060]: WARNING: interconnectroute [ported_cache.c:113]: initPortedNumberCount(): Requested records[726049]: Total allocated[871258]: Fat 20% :Total MemUsed [26 MB divided between primary[0x7f22b8667d60] and secondary[0x7f22b93b3390]] pr 5 04:38:24 NGVI-PCSCF2 /usr/sbin/kamailio[14018]: message repeated 107 times: [ ERROR: ims_usrloc_scscf [subscribe.c:430]: free_subscriber(): record not found in hash table] Apr 5 12:50:38 NGVI-PCSCF2 /usr/sbin/kamailio[2604]: WARNING: interconnectroute [icncache_eventprocessor.c:76]: icnRefreshProcess(): total size 2147483648 qm_real_used 700707576 qm_used 387064680 1st_frag 0x7fd5f6d6a690 last_frag 0x7fd676d30fd0 Apr 5 13:00:25 NGVI-PCSCF2 /usr/sbin/kamailio[2437]: ERROR: ims_usrloc_scscf [subscribe.c:430]: free_subscriber(): record not found in hash table Apr 5 13:00:26 NGVI-PCSCF2 /usr/sbin/kamailio[2437]: message repeated 125 times: [ ERROR: ims_usrloc_scscf [subscribe.c:430]: free_subscriber(): record not found in hash table] Apr 5 13:01:25 NGVI-PCSCF2 /usr/sbin/kamailio[2437]: CRITICAL: <core> [main.c:650]: sig_alarm_abort(): shutdown timeout triggered, dying... Apr 5 13:02:30 NGVI-PCSCF2 kamailio: WARNING: <core> [daemonize.c:348]: daemonize(): pid file contains old pid, replacing pid Apr 5 13:02:30 NGVI-PCSCF2 /usr/sbin/kamailio[27629]: WARNING: interconnectroute [ported_cache.c:113]: initPortedNumberCount(): Requested records[726049]: Total allocated[871258]: Fat 20% :Total MemUsed [26 MB divided between primary[0x7f3093a3fd60] and secondary[0x7f309478b390]] Thank you in advance. Regards, Solly Thoobe

3 2

urn:emergency:service:sos as RURI
by a.izquierdo＠zaleos.net 05 Apr '23

05 Apr '23

Hello, I'm running a Kamailio instance with some routing logic in it. When a UA sends an INVITE with urn:emergency:service:sos as RURI, Kamailio responds with a 400 Bad Request URI. I have set debug log level and it looks like the problem is in the parse_uri.c when sanity_check("1511", "7") is called: parse_uri(): bad char ':' in state 3 parsed: <urn:emergency:service> (21) / <urn:emergency:service:sos> (25) According to RFC8141 (https://www.rfc-editor.org/rfc/rfc8141), this is a correct URN, but maybe I'm missing something. Is there a way to make Kamailio parse this RURI? Kamailio version used: 5.6.4 Thank you!

3 2

segfault during Identity verification (stirshaken)
by Yuriy Nasida 04 Apr '23

04 Apr '23

Hello, It's kamailio 5.6.4. I can say that there is no segfault in case Identity is OK but bad attempts sometimes are the reason for segfault. Not sure I can duplicate but it happens several times per day. Please look at logs. in messages: Apr 3 09:40:02 kam1 kernel: [6381565.762987] kamailio[9141]: segfault at 746c75616665 ip 00007f20c4cab6df sp 00007ffe7ec51470 error 4 in libcrypto.so.1.1[7f20c4c3b000+19e000] kamailio.log: Apr 3 09:40:02 kam1 kamailio[9141]: NOTICE: <script>: it is INVITE with Identity. Lets check Identity Apr 3 09:40:02 kam1 kamailio[9141]: CRITICAL: <core> [core/mem/q_malloc.c:501]: qm_free(): BUG: bad pointer 0x645f6d6574737973 (out of memory block!) called from tls: tls_init.c: ser_free(323) - ignoring Apr 3 09:40:02 kam1 kamailio[9182]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 53 Apr 3 09:40:02 kam1 kamailio[9100]: ALERT: <core> [main.c:774]: handle_sigs(): child process 9141 exited by a signal 11 Apr 3 09:40:02 kam1 kamailio[9100]: ALERT: <core> [main.c:777]: handle_sigs(): core was not generated Apr 3 09:40:02 kam1 kamailio[9100]: CRITICAL: <core> [core/mem/q_malloc.c:501]: qm_free(): BUG: bad pointer 0x645f6d6574737973 (out of memory block!) called from tls: tls_init.c: ser_free(323) - ignoring loadmodule "stirshaken.so" ####### STIRSHAKEN ###### modparam("stirshaken", "vs_verify_x509_cert_path", 1) modparam("stirshaken", "vs_ca_dir", "/etc/kamailio/stir_CA") #modparam("stirshaken", "vs_crl_dir", "/etc/kamailio/CRL") modparam("stirshaken", "as_default_key", "/etc/kamailio/key/private_key.pem") modparam("stirshaken", "vs_cache_certificates", 1) modparam("stirshaken", "vs_cache_dir", "/tmp/cert_cache") modparam("stirshaken", "vs_cache_expire_s", 100) if (is_method("INVITE") && is_present_hf("Identity")) { xlog("L_NOTICE", "it is INVITE with Identity. Lets check Identity\n"); if (1 == stirshaken_check_identity()) { xlog("L_NOTICE", "Shaken Identity is OK\n"); } else { xlog("L_NOTICE", "Shaken Identity is invalid\n"); } } Please give me some advice.

2 2

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