- sr-users - kamailio.org

Re: uac_req_send + evroute + crash
by Dr. Barabás Péter 15 Nov '23

15 Nov '23

Hello Daniel, I’m using kamailio 5.7.2 currently and this misterious crash occurs again. Now core files are generated also, here is the trace: (gdb) bt #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #1 0x00007fae9a2d0859 in __GI_abort () at abort.c:79 #2 0x00005614ad79afd8 in qm_debug_check_frag (qm=0x7fae78e77000, f=0x7fae79805028, file=0x7fae77c8c134 "uac: uac_send.c", line=860, efile=0x5614ad936f99 "core/mem/q_malloc.c", eline=511) at core/mem/q_malloc.c:129 #3 0x00005614ad79f7c1 in qm_free (qmp=0x7fae78e77000, p=0x7fae79805060, file=0x7fae77c8c134 "uac: uac_send.c", func=0x7fae77c8cf10 <__func__.15157> "uac_send_tm_callback", line=860, mname=0x7fae77c8c014 "uac") at core/mem/q_malloc.c:511 #4 0x00005614ad7ab410 in qm_shm_free (qmp=0x7fae78e77000, p=0x7fae79805060, file=0x7fae77c8c134 "uac: uac_send.c", func=0x7fae77c8cf10 <__func__.15157> "uac_send_tm_callback", line=860, mname=0x7fae77c8c014 "uac") at core/mem/q_malloc.c:1350 #5 0x00007fae77c3686b in uac_send_tm_callback (t=0x7fae797dcf40, type=131072, ps=0x7fff8bd990d0) at uac_send.c:860 #6 0x00007fae783abc27 in run_trans_callbacks_internal (cb_lst=0x7fae797dcfe8, type=131072, trans=0x7fae797dcf40, params=0x7fff8bd990d0) at t_hooks.c:241 #7 0x00007fae783abd1e in run_trans_callbacks (type=131072, trans=0x7fae797dcf40, req=0x0, rpl=0x0, code=0) at t_hooks.c:261 #8 0x00007fae782bd8cb in free_cell_helper (dead_cell=0x7fae797dcf40, silent=0, fname=0x7fae783e9f62 "timer.c", fline=653) at h_table.c:165 #9 0x00007fae7837649c in wait_handler (ti=724701450, wait_tl=0x7fae797dcff8, data=0x7fae797dcf40) at timer.c:653 #10 0x00005614ad50be68 in timer_list_expire (t=724701450, h=0x7fae78ef5d18, slow_l=0x7fae78ef95e0, slow_mark=33641) at core/timer.c:857 #11 0x00005614ad50c3a7 in timer_handler () at core/timer.c:922 #12 0x00005614ad50c8d5 in timer_main () at core/timer.c:961 #13 0x00005614ad45fbf3 in main_loop () at main.c:1833 #14 0x00005614ad46ae93 in main (argc=14, argv=0x7fff8bd99b48) at main.c:3086 I think it occurs only if $uac_req(evroute) is set to 1 and I define the event_route[uac:reply] route. My uac_reply route is easy: if ($uac_req(evcode)==200) { xlog("L_INFO", "Registration for user $fU has been refreshed successfully."); $sht(vtp=>asterisk_restarted) = $null; route(SAVE_REG); } else { xlog("L_INFO", "Registration failed: $uac_req(evcode)"); } the SAVE_REG route is the following: route[SAVE_REG] { xlog("L_INFO", "Saving pbx registration...:$fU"); $var(maxExpiry) = MAX_PBX_REG_EXPIRY; route(GET_CLIENT_ID); sql_pvquery("ca", "select count(*) from pbxusers where user = '$fU'", "$var(pbxusersCnt)"); if ($var(pbxusersCnt)>0) { if ($var(clientId) == 0) { sql_query("ca", "update pbxusers set expiry = TIMESTAMPADD(SECOND, $var(maxExpiry), SYSDATE()), online=1 where user = '$fU'"); } else { sql_query("ca", "update pbxusers set client_id = '$var(clientId)', expiry = TIMESTAMPADD(SECOND, $var(maxExpiry), SYSDATE()), online=1 where user = '$fU'"); } } else { sql_query("ca", "insert into pbxusers (user, expiry, client_id, online) values ('$fU', TIMESTAMPADD(SECOND, $var(maxExpiry), SYSDATE()), '$var(clientId)', 0)"); } } And GET_CLIENT_ID route is: route[GET_CLIENT_ID] { $var(clientId) = 0; if (is_present_hf("X-AT-ClientId")) { $var(clientId) = $hdr(X-AT-ClientId); } } Any idea, is it a bug or I do something wrong in config files? Peter From: Dr. Barabás Péter via sr-users <sr-users(a)lists.kamailio.org> Date: Sunday, 2023. October 8. 18:49 To: miconda(a)gmail.com <miconda(a)gmail.com>, Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org> Cc: Dr. Barabás Péter <dr.peter.barabas(a)gmail.com> Subject: [SR-Users] Re: uac_req_send + evroute + crash Hello Daniel, I do not see any “failed to send request with authentication”. The next CRITICAL log appears after calling uac_req_send(): CRITICAL: <core> [core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer (0x7f114995ada8), called from uac: uac_send.c: uac_send_tm_callback(860), first free uac: uac_send.c: uac_resend_tm_callback(732) - ignoring Now we use kamailio 5.7.2 and no crash has come, but the critical logs above exist. I saw a ticket in github: https://github.com/kamailio/kamailio/issues/3522, may the crash be similar or the same to that? I will make a try next week with downgrading to 5.6.2 and try to reproduce the crash. Peter From: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: Friday, 2023. October 6. 13:55 To: Dr. Barabás Péter <dr.peter.barabas(a)gmail.com>, Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org> Subject: Re: [SR-Users] uac_req_send + evroute + crash Hello, do you also get error log messages that include "failed to send request with authentication"? Which CRITICAL log appears when you call uac_req_send()? You pasted a couple of them in the initial email? Cheers, Daniel On 05.10.23 17:32, Dr. Barabás Péter wrote: Hello, I used kamailio version 5.6.2. I refreshed to 5.7.2 today. As I remember it was in kamailio long time ago therefore I could skip evroute route. But this CRITICAL log appears always when I call uac_req_send(). I call it with settings: $uac_req(auser) = $var(username); $uac_req(apasswd) = $var(password); Where username and password are retrived from web service before call. In event_route I got first 401 after 200. Peter From: Daniel-Constantin Mierla <miconda(a)gmail.com><mailto:miconda@gmail.com> Date: Thursday, 2023. October 5. 17:25 To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org><mailto:sr-users@lists.kamailio.org> Cc: Dr. Barabás Péter <dr.peter.barabas(a)gmail.com><mailto:dr.peter.barabas@gmail.com> Subject: Re: [SR-Users] uac_req_send + evroute + crash Hello, On 05.10.23 16:34, Dr. Barabás Péter via sr-users wrote: Hi All, I use kamailio In front of Asterisk and kamailio needs to refresh registrations periodically towards Asterisk to ensure the availability of users from Asterisk side. I use uac module and call uac_req_send() for sending REGISTER requests. I set $uac_req(evroute)=1 The event_route[uac:reply] is called fine, but in kamailio logs I see the next lines: CRITICAL: <core> [core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer (0x7f114995ada8), called from uac: uac_send.c: uac_send_tm_callback(860), first free uac: uac_send.c: uac_resend_tm_callback(732) - ignoring After some time, kamailio has crashed. CRITICAL: <core> [core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer (0x7f114995ada8), called from uac: uac_send.c: uac_send_tm_callback(860), first free uac: uac_send.c: uac_resend_tm_callback(732) – ignoring CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 34 ALERT: <core> [main.c:774]: handle_sigs(): child process 1407950 exited by a signal 6 what version of Kamailio are you using? Is Asterisk challenging for authentication? Does it happen every time or seldom? Cheers, Daniel -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy and Development Services Kamailio Advanced Training - Online - Nov 14-16, 2023 -- asipto.com -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy and Development Services Kamailio Advanced Training - Online - Nov 14-16, 2023 -- asipto.com

1 0

How to check for presence of a file from a route? (Or any other way to tell kamailio not to accept new calls)
by Benoit Panizzon 13 Nov '23

13 Nov '23

Hi I'm still looking for a better way to tell Kamailio that we want to enter 'maintenance' and STAY in maintenance after a restart. Maintenance is: Reject all messages without totag with 503 to prevent creating new dialogues. I could use a shared pv and the use kamcmd pv.shvSet to toggle it. But when kamailio is restarted, that pv is also reset to it's initial state. Not good, if I want to make sure the node stays in maintenance mode after a restart as for example after pushing a config change via ansible. So what comes to my mind is to check for the presence of a file. something like: route[CHECK_MAINTENANCE] { if (!has_totag() && is_method("INVITE")) { if (file_exist("/etc/kamailio/maintenance.flag")) { xlog("L_ERR", "Maintenance flag present! Rejecting INVITE\n"); t_send_reply("503", "Maintenance mode - no new calls accepted"); exit; } } } 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 ______________________________________________________

4 3

Inconsistent behavior between reg_fetch_contacts (registrar module) and reginfo_handle_notify (pua_reginfo module)?
by Mohammad Hossein Ahmadi 13 Nov '23

13 Nov '23

Hello everyone, I have previously set up Kamailio 5.7.2 IMS configuration (including P-CSCF, S-CSCF and I-CSCF) and successfully made voice calls. Now I'm trying to set up an IP-SM-GW AS using the example here (with some tweaks): https://github.com/kamailio/kamailio/blob/master/src/modules/smsops/example… Currently I'm trying to send the SMS using a SIP software client (MicroSIP). The problem is, while the SMS is received at the AS and stored in the database, it does not send it to the callee. While troubleshooting the problem, I've found that reg_fetch_contacts("location", "$var(uri)", "caller") in route[SEND_SMS] cannot find the contact which was added by reginfo_handle_notify("location") in route[NOTIFY] in the usrloc database. By tracing the problem more, I've found that reginfo_handle_notify (when handling reg event NOTIFY) adds the complete AoR in the "username" field in the location table, e.g. as "bob(a)ims.mnc001.mcc001.3gppnetwork.org". But reg_fetch_contacts (when trying to send the SMS) looks up the table using only the user part in the "username" field, e.g. "bob". So it cannot find the callee contact and the configuration assumes the callee is still not registered; so it tries to send out a SUBSCRIBE every time it tries to send an SMS to the callee, instead of actually sending the SMS. Does anybody have any idea on what could have caused this inconsistent behavior between reginfo_handle_notify and reg_fetch_contacts?

2 6

Dispatcher list reloading itself from file?!?
by Benoît Panizzon 13 Nov '23

13 Nov '23

Hi List I wanted to take one of our cores down gracefully by not destroy running dialogues to be able to implement a config change on Kamailio 5.5 For this I did: kamctl dispatcher.remove ID SIP-URI, for every IC This worked fine, Kamailio is instructed to reply 503 on out of dialogue traffic from unknown endpoints causing the endpoints to re-route traffic to the other core, eventually making it possible to stop and restart Kamailio without harm. dialog count was steadily decreasing, until after about 10 minutes after removing the dispatcher URI's it started to increase again. kamctl dispatcher.list shows me, all dispatcher URI I removed are back! There is no ds_reload() being executed by calls. In the module description, I find no hint, that the dispatcher config is being reloaded from file in some interval or so. What could be the cause of my removed dispatcher suddenly being back? -- 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

pseudo variable in include_file not possible
by Bernd Krueger-Knauber 13 Nov '23

13 Nov '23

Hi, since we use git also for our kamailio stuff, we need to check in also host specific stuff. (same kamailio.cfg but different addresses and ... ) For this I thought an include_file for different hosts would be nice, but I can not check in the different host specific files, because I can not use something like: |include_file "$HN(n).cfg" It is not allowed in kamailio 5.6.x Or better: the pseudo variable is not replaced. Is there a way to work arround, or is it possible to make it possible? Best regards Bernd |

3 2

Working with kamailio websocket and asterisk
by SAMUEL MOYA TINOCO 13 Nov '23

13 Nov '23

Good evening everyone, I'm trying to set a scenario with my extensions registered against kamailio via wss and then once authenticated forward the register to my asterisk. After this, I use dispatcher module to balance invites to my asterisks. I have a few questions, the first part seems to be working as I want but when asterisk receives an invite and responds with INVITE (SDP) it doesn't appear on my kamailio (but every other message appears) You can see it in this sngrep captures Kamailio: [cid:image001.png@01DA0E88.5F82F510] Asterisk [cid:image002.png@01DA0E88.5F82F510] I guess it is because something in my asterisk pjsip configuration is wrong but I can't figure out what. So I'm start to think that maybe It is because I need to configure an rtpproxy app to change SDP and make RTP traffic go through kamailio Maybe there's something else I need to do, or there's a guide to do this. But I can't find anything Any help will be very appreciated Thank you in advance Samuel Moya Tinoco Departamento de Sistemas y Redes Móvil: (+34) 606985997 smoya(a)vivelibre.es<mailto:smoya@vivelibre.es> [cid:image003.png@01DA0E88.5F82F510] Soluciones inteligentes para la autonomía personal

6 7

Info: qm and fm memory managers aligning addresses to 16 bytes
by Daniel-Constantin Mierla 10 Nov '23

10 Nov '23

Hello, following the Kamailio Developers Meeting discussions and provided that GNU/Linux malloc() aligns allocated memory to 16 bytes on x86_64 (64b CPUs), I just updated the native Kamailio qm (quick malloc - the default one) and fm (fast malloc) memory managers to also align to 16 bytes: - https://www.gnu.org/software/libc/manual/html_node/Aligned-Memory-Blocks.ht… By default they do it to 16 also for 32b CPUs, the overhead at startup with default config was rather insignificant (like 5000 bytes for private memory set to 8MB), so I didn't want to bother that much (that's also because some 32b CPUs could require larger alignment that the size of the pointer address), but for flexibility I added the an option to set the alignment size at compile time with KSR_MEMORY_ALIGN define (e.g., -DKSR_MEMORY_ALIGN=8UL). The main benefit at this moment is that Kamailio should be able to use the OS distribution (e.g., Debian) packaged libwolfssl instead of bundling and building the library inside it to compile with custom flags, like it is done now. Also, it is safe for the future to use other libraries that leverage internally the OS memory alignment size for specific optimizations. I also increased the optimize factor to 15, which should speed up a bit dealing with larger chunks of memory (now up to 32KB, previously was up to 16KB). Considering that it is more and more common to deal with larger SIP messages (e.g., a webrtc invite can easily be like 20KB) as well as tls/encryption needs addition space that the unencrypted udp/tcp. Hopefully these updates don't have side effects, it was nothing consistent changed, a few defines and fields to match the new alignment constraints. But testing is important, try to play with the master and your configs whenever you have any chance. Unfortunately the tlsf memory manager seems to be specifically designed for aligning to 8 bytes, a rather old related issue in that project is not concluded: - https://github.com/mattconte/tlsf/issues/16 That means the tls_wolfssl module linked with the officially packaged libwolfssl has to be used with qm or fm malloc from now on. Or it has to be built like so far to use tlsf memory manager. The tls/tlsa module can still be used with tlsf memory manager. Cheers, Daniel -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy and Development Services

1 0

Development environment for the pre-commit hooks and clang-format
by Daniel-Constantin Mierla 10 Nov '23

10 Nov '23

Hello, during the Kamailio Developers Meeting 2023 in Dusseldorf early this week, Victor Seva shared how one can setup own development environment for facilitating the automatic checks for clang-format and few other useful bits (e.g., training white spaces) using pre-commit tool. So I thought it would be useful to shared further to both developers and users communities (as the later can make patches and pull requests as well). If I forgot something, Victor should amend me, but the main steps are: - install pre-commit package (either via apt or via pip3) - install clang-format (debian/ubuntu should have it as a package) - go to the folder with git clone of Kamailio source and run: pre-commit install The above command can take some time, but it is needed only once. After that, on evey commit, the checks should be performed a summary should be presented on screen, like: $ git commit src/ check yaml...........................................(no files to check)Skipped check xml............................................(no files to check)Skipped fix end of files.........................................................Passed trim trailing whitespace.................................................Passed check for merge conflicts................................................Passed mixed line ending........................................................Passed clang-format.............................................................Passed If the check of clang-format results in "Failed", like: clang-format.............................................................Failed the pre-commit hooks will correct it, so you can just run again the commit command and the 2nd time should be good to go. If for whatsoever reasons pre-commit is installed but you need to ignore/skip the pre-commit hooks, just provide -n or --no-verify to the commit command, like: $ git commit -n src/ By using pre-commit hooks, one could easily avoid making pull requests that are failing to meet the code formatting checks on github portal as well as ensure that as developer one does no forget to run clang-format before commit. Cheers, Daniel -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy and Development Services

1 0

Issue with Dialog Handling in Kamailio Post 2-Minute Duration
by aaron.soto＠dialapplet.com 10 Nov '23

10 Nov '23

I'm encountering an issue with dialog handling in Kamailio. Initially, everything functions correctly, and if a connection terminates within two minutes, the BYE method works as expected. However, if the call exceeds two minutes, the BYE method doesn't seem to be recognized, and there are no related entries in the logs. As someone new to working with Kamailio, I'm finding this quite perplexing. Could anyone offer guidance or troubleshooting steps to resolve this issue? Thank you for your assistance.

3 6

Sharing load between rtpengine servers
by David Cunningham 09 Nov '23

09 Nov '23

Hello, We have a Kamailio configuration with the following, however all the load is going to the server at 22.22.22.22 (hiding the real IP obviously) instead of being shared evenly between 22.22.22.22 and 33.33.33.33. Can anyone please tell me why? The rtpengine server at 11.11.11.11 is intended to only receive calls if the other two are offline. Thank you very much. #!define RTPENGINE_ADDR "udp:11.11.11.11:7724=1 udp:22.22.22.22:7724=99999999 udp:33.33.33.33:7724=99999999" modparam( "rtpengine", "rtpengine_sock", RTPENGINE_ADDR ) -- David Cunningham, Voisonics Limited http://voisonics.com/ USA: +1 213 221 1092 New Zealand: +64 (0)28 2558 3782

5 10

Redis issue when getting results in Kamailio
by Ali Taher 09 Nov '23

09 Nov '23

Hello all, I have redis database where the data is inserted in JSON format: #Redis Command JSON.GET Index1J:12345678 #Redis Result [ { "SupplierID": "7", "BCode": "987654", "Rate": 0.159 }, { "SupplierID": "7", "BCode": "765432", "Rate": 0.159 }, { "SupplierID": "7", "BCode": "5432159", "Rate": 0.159 } ] When I try to get the result using Lua script in Kamailio like the following: #kamailio command if KSR.ndb_redis.redis_cmd("srvN", "JSON.GET pricelistJ:441246890", "ra") then KSR.xlog.xinfo("array size: $redis(ra=>size)\n"); KSR.xlog.xinfo("Redis Response: " .. tostring(ra) .. "\n") KSR.xlog.xinfo("first values: $redis(ra=>value[0]) , $redis(ra=>value[1])\n"); end Nov 7 07:58:15 868d08ee318d /usr/sbin/kamailio[72]: INFO: LUA {INVITE}: <script>: array size: <null> Nov 7 07:58:15 868d08ee318d /usr/sbin/kamailio[72]: INFO: LUA {INVITE}: <script>: Redis Response: nil Nov 7 07:58:15 868d08ee318d /usr/sbin/kamailio[72]: INFO: LUA {INVITE}: <script>: first values: <null> , <null> I'm getting null results. I don't know what I'm doing wrong here. Can you please assist?

2 3

Sequential fork with different Call-Ids
by Vanderlei Torres Batistela 09 Nov '23

09 Nov '23

Hello all, I have a scenario on wich requires sequential fork (up to 30 possible destinations) with different Call-ID for each leg. I am using topoh module enabled, but it always puts the same Call-ID. Someone have a solution for this scenario? Regards

4 3

3xx is not relayed to the caller if there are 2 or more branches in the transaction
by Михаил Горюцкий 07 Nov '23

07 Nov '23

Hello, I encountered such a problem: An INVITE request comes to Kamailio. Kamailio finds a location and forwards this INVITE to a device. The device receives a push notification and registers on a new IP: port. The tsilo module creates a new branch. And this branch sends the INVITE. The device responds with 100 -> 180 -> 302. 100 and 180 are forwarded to the calling subscriber, but anything greater than 300, such as 302, is not forwarded. DEBUG: tm [t_reply.c:1363]: t_should_relay_response(): ->>>>>>>>> T_code=180, new_code=302 DEBUG: tm [t_reply.c:1448]: t_should_relay_response(): store - other branches still active DEBUG: tm [t_reply.c:1925]: relay_reply(): reply status=3 branch=1, save=1, relay=-1 icode=0 msg status=302 Kamailio saves this code and does not pass it to the caller. Is there a way to immediately pass this 302? It seems like something can be done in t_on_branch_failure, which is invoked, but I can't figure out what needs to be done there. Is there a parameter that can solve my problem? A similar question has been asked before, but the link in Daniel's response leads to a non-existent ID: https://lists.kamailio.org/pipermail/sr-users/2009-March/022447.html

2 2

defexps not working as expected
by Richard Chan 07 Nov '23

07 Nov '23

In the config file: #!define KEYVALUE "key=s:value" modparam("pv", "varset", KEYVALUE) works. But if I try to use defexp or defexps the ID KEYVALUE is not set as expected and the parser complains. ## this doesn't parse #!defexp KEYVALUE2 "key=s:value" #!defexps KEYVALUE3 "key=s:value" # both these lead to syntax error modparam("pv", "varset", KEYVALUE2) modparam("pv", "varset", KEYVALUE3) Any ideas why defexp doesn't behave the same way here? Shih-Ping

1 0

SIP Proxy : BYE next hop
by Ali Taher 03 Nov '23

03 Nov '23

Hello all, I'm using Kamailio as SIP proxy between session manager and SBC. I came across an issue in BYE request where the SBC sent in the header list of Routes where first route is Kamailio IP, and the second is SM IP, in addition to other routes (last route is the caller party) What Kamailio did is to route the BYE to the address set in the Request-URI, which is the caller party. What should be done instead is that Kamailio should remove the Route header including its own IP, and route the BYE to the next hop which is in this case the SM IP. How to accomplish that? Following is the Route header in the BYE request coming from SBC: [truncated]Route: <sip:KAMAILIO_IP;lr;ftag=xxxxxxxxxxxxxxxxxxxxxxx>,<sip:SM1@SM_IP;transport=udp;lr;av-asset-uid=xxxxxxxxxx>,<sip:127.0.0.2:15060;transport=udp;ibmsid=local.xxxxxxxxxxxx_xxxxxxxxx_xxxxxxxxx;lr;ibmdrr>,sips:127.0.0.2:15061;ibmsid=local.xxxxxxxxxx_xxxxxxxxxx_xxxxxxxx;lr;ibmdrr, sip:SM1@SM_IP;transport=tls;lr;av-asset-uid=xxxxxx, sip:CALLER_PARTY_IP:5061;transport=tls;lr Regards,

3 6

PLMN 31501 , VoLTE IMS Kamalio
by snahmed.snahmed＠gmail.com 31 Oct '23

31 Oct '23

Hi, I was able to test the PLMN 00101 for VoLTE, but unable to test it with other PLMNs. I am specifically looking to have a successful test with PLMN31501. VoLTE is not enabling once I configure it. I followed this https://open5gs.org/open5gs/docs/tutorial/02-VoLTE-setup/ Any one has experience for PLMN 315?

1 0

Registrar / Path
by Jawaid Bazyar 31 Oct '23

31 Oct '23

Hi, I have a scenario where I have an edge proxy (named RS), which locally stores registrations from Endpoints in its USRLOC, but which then also forward's REGISTER requests on to another proxy (named CN), which stores registrations in its USRLOC. (which then does DMQ with another CN like it). Both RS and CN are storing Path information, for example: kamctl ul show displays on both RS and CN: "Path": "sip:vs-rs01.blah.foo.bar;lr;received=sip:3.4.5.6:33577", So I know the path info is in there. I want CN , when presented with an INVITE, to reply with a 302 Redirect. Right now I have this: if (!lookup("location",sip:$tU@nodomain)) { } reg_fetch_contacts("location", "$tu", "called"); xlog("location info $ulc(called=>path)"); sl_send_reply("302","Redirect"); and the xlog does display the path. Good, so I have it being sent all the way through RS and CN and into CN’s USRLOC. but this isn’t complete. I am now faced with two issues. One, I need to mangle the Path into a Contact header for the Redirect. Two, I need to delete the Contact header that sl_send_reply is putting on there, which is the Contact as RS sees it from the endpoint. This needs to be removed and replaced with a Contact of only the RS server. It feels like there ought to be a simpler way to do this than parsing the Path string and reassembling a Contact from it, but if there is it's not readily apparent. Both Google and chatgpt have failed me :) Thanks in advance, Jawaid

3 7

Kamailio 5.7 still segfaulting on TLS with Ubuntu Jammy
by Benoît Panizzon 31 Oct '23

31 Oct '23

Hi Gang I just updated our dev plattform from 5.6 to 5.7 5.5 was working fine with TLS under Ubuntu Focal. 5.6 under Jammy started to dump cores. 5.7 still shows the same behaviour, usually shortly after a restart. Oct 20 09:45:01 dev-cpereg01 kamailio[11925]: CRITICAL: <core> [core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer (0x7f1bb0dd4bd8), called from tls: tls_init.c: ser_free(405), first free tls: tls_init.c: ser_free(405) - ignoring Oct 20 09:45:11 dev-cpereg01 kamailio[11905]: ALERT: <core> [main.c:776]: handle_sigs(): child process 11924 exited by a signal 11 Oct 20 09:45:11 dev-cpereg01 kamailio[11905]: ALERT: <core> [main.c:779]: handle_sigs(): core was generated Could anyone point me the correct direction on how to fix this issue? Am I the only one seeing this issue? -- 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 4

RPM Repos Maintenance Needed
by tyler moore 30 Oct '23

30 Oct '23

Hi All, I started a discussion on the matrix channel about some 404 RPM repos and wanted to bring it here to further discuss. We typically configure our various RPM-based package managers to allow patch updates from the repos. As an example, if trying to install 5.7.x, can be done as follows: |yum -y install yum-utils yum-config-manager --add-repo https://rpm.kamailio.org/centos/kamailio.repo yum-config-manager --disable \* yum-config-manager --enable kamailio-5.7 yum install kamailio | This will fail though because https://rpm.kamailio.org/centos/7/5.7/5.7/x86_64/ does not exist. Throughout the repos for centos/rhel/fedora I found the existence of packages is inconsistent. We can tell the intention was to allow the above behavior as the kamailio.repo comes with the above configuration. The above example will update /etc/yum.repos.d/kamailio.repo as follows: |[kamailio-5.7] name=Kamailio - 5.7 - Packages for the latest Kamailio 5.7 release baseurl=https://rpm.kamailio.org/centos/$releasever/5.7/5.7/$basearch/ enabled=1 metadata_expire=30d repo_gpgcheck=0 gpgkey=https://rpm.kamailio.org/rpm-pub.key type=rpm skip_if_unavailable=True | That is for centos though, and I found that some of the other distros have incomplete kamailio.repo files as well. In example, the rhel kamailio.repo is missing separate entries for 5.7, but it does exist in the centos version. Looks like some small cleanup is in order to make the end user experience more consistent. I believe sergey was maintaining those repos last, please chime in here if you can. If needed I can pick up some of those responsibilities as well. -- Regards, *Tyler Moore* <https://devopsec.net/> Full Stack Software Engineer <http://www.google.com/search?q=full+stack+software+engineer+job+description> Flyball Labs <http://goflyball.com/> Office: 888-907-2085, ext: 34 <tel:8889072085;ext=34> Cell: 248-909-2769 <tel:2489092769> Email: tmoore(a)goflyball.com FLYBALL TECHNICAL SOLUTIONS, LLC <http://flyballlabs.com/> -- Tyler Moore Regards, *Tyler Moore* <https://devopsec.net/> Full Stack Software Engineer <http://www.google.com/search?q=full+stack+software+engineer+job+description> Flyball Labs <http://goflyball.com/> Office: 888-907-2085, ext: 34 <tel:8889072085;ext=34> Cell: 248-909-2769 <tel:2489092769> Email: tmoore(a)goflyball.com FLYBALL TECHNICAL SOLUTIONS, LLC <http://flyballlabs.com/>

3 2

RPM Repos Maintenance Needed
by tyler moore 28 Oct '23

28 Oct '23

Hi All, I started a discussion on the matrix channel about some 404 RPM repos and wanted to bring it here to further discuss. We typically configure our various RPM-based package managers to allow patch updates from the repos. As an example, if trying to install 5.7.x, can be done as follows: yum -y install yum-utils yum-config-manager --add-repo https://rpm.kamailio.org/centos/kamailio.repo yum-config-manager --disable \* yum-config-manager --enable kamailio-5.7 yum install kamailio This will fail though because https://rpm.kamailio.org/centos/7/5.7/5.7/x86_64/ does not exist. Throughout the repos for centos/rhel/fedora I found the existence of packages is inconsistent. We can tell the intention was to allow the above behavior as the kamailio.repo comes with the above configuration. The above example will update /etc/yum.repos.d/kamailio.repo as follows: [kamailio-5.7] name=Kamailio - 5.7 - Packages for the latest Kamailio 5.7 release baseurl=https://rpm.kamailio.org/centos/$releasever/5.7/5.7/$basearch/ enabled=1 metadata_expire=30d repo_gpgcheck=0 gpgkey=https://rpm.kamailio.org/rpm-pub.key type=rpm skip_if_unavailable=True That is for centos though, and I found that some of the other distros have incomplete kamailio.repo files as well. In example, the rhel kamailio.repo is missing separate entries for 5.7, but it does exist in the centos version. Looks like some small cleanup is in order to make the end user experience more consistent. I believe sergey was maintaining those repos last, please chime in here if you can. If needed I can pick up some of those responsibilities as well. Regards, Tyler Moore Full Stack Software Engineer Flyball Labs Office: 888-907-2085, ext: 34 Cell: 248-909-2769 Email: tmoore(a)goflyball.com

2 2

Kamailio 5.4.3 Troubleshooting Traffic Blocking Issue After Docker and OpenSSL Update
by Pintu Lohar 27 Oct '23

27 Oct '23

Hi All, We have recently encountered a challenging issue in our environment that I wanted to bring to your attention. A few months ago, we performed updates to our Docker and OpenSSL installations, upgrading OpenSSL to version 1.1.1u. Since then, we have been experiencing intermittent traffic blocking (TLS and UDP both for around 10 minutes and getting recovered) on some of our instances. Prior to the OpenSSL upgrade, we had not observed any such issues. However, the situation has become more complex due to a substantial increase in traffic, with each instance now handling 4K-5K concurrent calls and a daily total of approximately 200,000 calls per instance. Our initial suspicion was related to a Docker iptable issue. To investigate further, we conducted a GDB trace using "kamctl pstrap" and discovered specific log entries indicating potential issues within the "pthread_rwlock_wrlock" function. This has prompted us to explore whether the problems are linked to the OpenSSL upgrade. We are considering upgrading Kamailio to the latest version, although this process typically requires a significant amount of time for proper planning and testing. Given the high volume of calls we are currently handling, we are also exploring the possibility of a temporary solution involving a rollback of the OpenSSL version to see if it resolves the issue. Curiously, during a recent load test using SIPP, which simulated 10,000 concurrent calls with a rate of 100 calls per second, we did not encounter the same problem. any hints or insights you may have that could help us pinpoint the root cause of the problem . We do have a complete GDB trace available, but its size necessitates sharing a truncated version for now. version: kamailio 5.4.3 (x86_64/linux) 0178a5 flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES 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: 0178a5 compiled on 12:36:56 Oct 22 2023 with gcc 4.8.5 Operating System Host : LSB Version: :core-4.1-amd64:core-4.1-noarch Distributor ID: Rocky Description: Rocky Linux release 8.8 (Green Obsidian) Release: 8.8 Codename: GreenObsidian container os (Centos7) Kamctl pstraip output (truncated to last few lines) ---start 154 ----------------------------------------------------- kamailio: No such file or directory. [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". 0x00007fbf6f38a0c3 in __epoll_wait_nocancel () from /lib64/libc.so.6 $1 = 82 $2 = {pid = 154, unix_sock = 182, idx = 27, status = 1, rank = 48, desc = "tcp receiver (tcp:xxx.xxx.xxx.xx:5060 <http://223.62.234.57:5060/>) child=27", '\000' <repeats 81 times>} #0 0x00007fbf6f38a0c3 in __epoll_wait_nocancel () from /lib64/libc.so.6 No symbol table info available. #1 0x0000000000684858 in io_wait_loop_epoll (h=0xb41720 <io_w>, t=2, repeat=0) at core/io_wait.h:1039 n = 84 r = 0 fm = 0x2 revents = 8201656 __FUNCTION__ = "io_wait_loop_epoll" #2 0x0000000000699e7a in tcp_receive_loop (unix_sock=186) at core/tcp_read.c:1997 __FUNCTION__ = "tcp_receive_loop" #3 0x00000000005279e7 in tcp_init_children () at core/tcp_main.c:5134 r = 27 i = -1 reader_fd_1 = 186 pid = 0 si_desc = "tcp receiver (tcp:xxx.xx.xxx.xxx:5060 <http://223.62.234.57:5060/> )\000\000\000\355\217c\000\000\000\000\000\240\213{\001\001\000\000\000\017\000\000\000\000\000\000\000\250\a2o\276\177\000\000\200\b\231o\000\000\000\000\260\006\346\261\376\177\000\000\230\210w\000\000\000\000\000=\000\000\000>\000\000\000\270\016z\350\274\177\000\000\060;8o\002\000\000\000P\224\346\352\001\000\000" si = 0x0 __FUNCTION__ = "tcp_init_children" #4 0x000000000042ae66 in main_loop () at main.c:1771 i = 16 pid = 94 si = 0x0 si_desc = "udp receiver child=15 sock=xxxx.xxx.xxx.xx:5060\000\000\000\v\235\200", '\000' <repeats 13 times>, "P\r\346\261\376\177\000\000\270%}\000\000\000\000\000T\000\000\000\000\000\000\000\060;8o\277\177\000\000\343\207\201\000\000\000\000\000\277;8o\277\177\000\000 \271A\000\000\000\000\000@\374Ko\276\177\000" nrprocs = 16 woneinit = 1 __FUNCTION__ = "main_loop" #5 0x0000000000433ad6 in main (argc=9, argv=0x7ffeb1e60e38) at main.c:2856 cfg_stream = 0x16c9010 c = -1 r = 0 tmp = 0x7ffeb1e61f0c "" tmp_len = 2496 port = 2496 proto = 1472 ahost = 0x0 aport = 0 options = 0x7d5238 ":f:cm:M:dVIhEeb:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:x:X:Y:" ret = -1 seed = 2208520674 rfd = 4 debug_save = 0 debug_flag = 0 dont_fork_cnt = 0 n_lst = 0x7fbf6f40f3a0 <intel_02_known> p = 0xf0b5ff <Address 0xf0b5ff out of bounds> st = {st_dev = 76, st_ino = 120506675, st_nlink = 2, st_mode = 16877, st_uid = 0, st_gid = 0, __pad0 = 0, st_rdev = 0, st_size = 40, st_blksize = 4096, st_blocks = 0, st_atim = {tv_sec = 1698340416, tv_nsec = 618631009}, st_mtim = {tv_sec = 1698340416, tv_nsec = 618631009}, st_ctim = {tv_sec = 1698340416, tv_nsec = 618631009}, __unused = {0, 0, 0}} tbuf = '\000' <repeats 376 times>... option_index = 0 long_options = {{name = 0x7d742f "help", has_arg = 0, flag = 0x0, val = 104}, {name = 0x7d2a34 "version", has_arg = 0, flag = 0x0, val = 118}, {name = 0x7d7434 "alias", has_arg = 1, flag = 0x0, val = 1024}, {name = 0x7d743a "subst", has_arg = 1, flag = 0x0, val = 1025}, {name = 0x7d7440 "substdef", has_arg = 1, flag = 0x0, val = 1026}, {name = 0x7d7449 "substdefs", has_arg = 1, flag = 0x0, val = 1027}, {name = 0x7d7453 "server-id", has_arg = 1, flag = 0x0, val = 1028}, {name = 0x7d745d "loadmodule", has_arg = 1, flag = 0x0, val = 1029}, {name = 0x7d7468 "modparam", has_arg = 1, flag = 0x0, val = 1030}, {name = 0x7d7471 "log-engine", has_arg = 1, flag = 0x0, val = 1031}, {name = 0x7d747c "debug", has_arg = 1, flag = 0x0, val = 1032}, {name = 0x0, has_arg = 0, flag = 0x0, val = 0}} __FUNCTION__ = "main" [Inferior 1 (process 154) detached] ---end 154 ------------------------------------------------------- ---start 155 ----------------------------------------------------- kamailio: No such file or directory. [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". 0x00007fbe6e5bd39e in pthread_rwlock_wrlock () from /lib64/libpthread.so.0 $1 = 83 $2 = {pid = 155, unix_sock = -1, idx = -1, status = 1, rank = -4, desc = "tcp main process", '\000' <repeats 111 times>} #0 0x00007fbe6e5bd39e in pthread_rwlock_wrlock () from /lib64/libpthread.so.0 No symbol table info available. #1 0x00007fbe68b745c9 in CRYPTO_THREAD_write_lock () from /lib64/libcrypto.so.1.1 No symbol table info available. #2 0x00007fbe68afe07e in CRYPTO_free_ex_data () from /lib64/libcrypto.so.1.1 No symbol table info available. #3 0x00007fbe68ea52c2 in SSL_free () from /lib64/libssl.so.1.1 No symbol table info available. #4 0x00007fbe69149480 in tls_h_tcpconn_clean_f (c=0x7fbceeae00d0) at tls_server.c:655 extra = 0x7fbceec3b898 __FUNCTION__ = "tls_h_tcpconn_clean_f" #5 0x00000000004fbf2d in _tcpconn_free (c=0x7fbceeae00d0) at core/tcp_main.c:1529 __FUNCTION__ = "_tcpconn_free" #6 0x0000000000510912 in tcpconn_put_destroy (tcpconn=0x7fbceeae00d0) at core/tcp_main.c:3284 __FUNCTION__ = "tcpconn_put_destroy" #7 0x00000000005156a5 in handle_tcp_child (tcp_c=0x7fbe6f813440, fd_i=-1) at core/tcp_main.c:3723 tcpconn = 0x7fbceeae00d0 response = {140449434960080, -2} cmd = -2 bytes = 16 n = 1865551792 t = 887186228 crt_timeout = 410 con_lifetime = 57680 __FUNCTION__ = "handle_tcp_child" #8 0x00000000005208ed in handle_io (fm=0x7fbe6f9d7c78, ev=1, idx=-1) at core/tcp_main.c:4542 ret = 1 __FUNCTION__ = "handle_io" #9 0x00000000004e93ed in io_wait_loop_epoll (h=0xad5740 <io_h>, t=5, repeat=0) at core/io_wait.h:1070 n = 1 r = 0 fm = 0x7fbe6f9d7c78 revents = 1 __FUNCTION__ = "io_wait_loop_epoll" #10 0x0000000000523c99 in tcp_main_loop () at core/tcp_main.c:4827 si = 0x0 r = 28 __FUNCTION__ = "tcp_main_loop" #11 0x000000000042b1be in main_loop () at main.c:1779 i = 16 pid = 0 si = 0x0 si_desc = "udp receiver child=15 sock=xxx.xx.xxx.xxx:5060 <http://223.62.234.76:5060/>\000\000\000\v\235\200", '\000' <repeats 13 times>, "P\r\346\261\376\177\000\000\270%}\000\000\000\000\000T\000\000\000\000\000\000\000\060;8o\277\177\000\000\343\207\201\000\000\000\000\000\277;8o\277\177\000\000 \271A\000\000\000\000\000@\374Ko\276\177\000" nrprocs = 16 woneinit = 1 __FUNCTION__ = "main_loop" #12 0x0000000000433ad6 in main (argc=9, argv=0x7ffeb1e60e38) at main.c:2856 cfg_stream = 0x16c9010 c = -1 r = 0 tmp = 0x7ffeb1e61f0c "" tmp_len = 2496 port = 2496 proto = 1472 ahost = 0x0 aport = 0 options = 0x7d5238 ":f:cm:M:dVIhEeb:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:x:X:Y:" ret = -1 seed = 2208520674 rfd = 4 debug_save = 0 debug_flag = 0 dont_fork_cnt = 0 n_lst = 0x7fbf6f40f3a0 <intel_02_known> p = 0xf0b5ff <Address 0xf0b5ff out of bounds> st = {st_dev = 76, st_ino = 120506675, st_nlink = 2, st_mode = 16877, st_uid = 0, st_gid = 0, __pad0 = 0, st_rdev = 0, st_size = 40, st_blksize = 4096, st_blocks = 0, st_atim = {tv_sec = 1698340416, tv_nsec = 618631009}, st_mtim = {tv_sec = 1698340416, tv_nsec = 618631009}, st_ctim = {tv_sec = 1698340416, tv_nsec = 618631009}, __unused = {0, 0, 0}} tbuf = '\000' <repeats 376 times>... option_index = 0 long_options = {{name = 0x7d742f "help", has_arg = 0, flag = 0x0, val = 104}, {name = 0x7d2a34 "version", has_arg = 0, flag = 0x0, val = 118}, {name = 0x7d7434 "alias", has_arg = 1, flag = 0x0, val = 1024}, {name = 0x7d743a "subst", has_arg = 1, flag = 0x0, val = 1025}, {name = 0x7d7440 "substdef", has_arg = 1, flag = 0x0, val = 1026}, {name = 0x7d7449 "substdefs", has_arg = 1, flag = 0x0, val = 1027}, {name = 0x7d7453 "server-id", has_arg = 1, flag = 0x0, val = 1028}, {name = 0x7d745d "loadmodule", has_arg = 1, flag = 0x0, val = 1029}, {name = 0x7d7468 "modparam", has_arg = 1, flag = 0x0, val = 1030}, {name = 0x7d7471 "log-engine", has_arg = 1, flag = 0x0, val = 1031}, {name = 0x7d747c "debug", has_arg = 1, flag = 0x0, val = 1032}, {name = 0x0, has_arg = 0, flag = 0x0, val = 0}} __FUNCTION__ = "main" [Inferior 1 (process 155) detached] ---end 155 ------------------------------------------------------- Thanks & Regards Pintu Lohar

1 0

Inquiry Regarding Kamailio Behavior and Drop Requests
by satyaprakash ch 26 Oct '23

26 Oct '23

Hi, We possess a code within Kamailio, which specifically handles malformed SIP responses. Below is the code snippet: *reply_routeCopy code if(!sanity_check("17604", "6")) { xlog("Malformed SIP response from $si:$sp\n"); drop;* Additionally, we have Kamailio drop request statistics as follows: Command: *kamctl stats | grep core:drop_requests* Output of the command: *core:drop_requests = 5* My queries are: 1. Is the aforementioned "reply_route" related to the drop requests we are experiencing? 2. If it is not related, what could be the cause of the drop requests?

3 8

Information about Kamailio operating as an SBC
by Alvaro Escobar 24 Oct '23

24 Oct '23

Hello, I am looking information about Kamailio operating as an SBC. I saw this video of Kamailio World 2021: Kamailio As An SBC For Network Segregation: https://www.youtube.com/watch?v=UW6l3R4OnsY&t=1381s But where I can find more detailed technical information ? Regards

3 3

How to filter out xhttp request in event_route[siptrace:msg]
by Benoit Panizzon 24 Oct '23

24 Oct '23

Hi Further trying to eliminate every possible cause of UDP drops... We use Homer as HEP server in conjunction with the siptrace module. So to prevent DQM traffic to be sent to Homer I added: event_route[siptrace:msg] { if(is_method("KDMQ")) { drop(); } } And had a closer look to the traffic sent to homer. I noticed, also xhttp:requests, as far as I see the replies, not the requests, get mirrored to homer. xhttp is not a sip method I could match I guess. The event_route[siptrace:msg] docs state only method can be filtered. So I can not filter requests on the separate http port I listen on for xhttp json-rpc requests. How can I prevent xhttp traffic to be mirrored to homer by the siptrace 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 ______________________________________________________

4 5

STIR/SHAKEN with Kamailio
by Olle E. Johansson 23 Oct '23

23 Oct '23

Hello Kamailians! As STIR/SHAKEN seems to cross the ocean and arrive on the European shores, I’m curious on how you’ve implemented it with Kamailio. I asked on our Matrix chat and got two responses that seems to not use the Kamailio STIR/SHAKEN support but rather a 3rd party service that they’ve integrated using restful APIs. Please help me and share how you’re implementing STIR/SHAKEN with Kamailio. I’m not shaken, nor stirred. yet. Regards, /O

7 9

How to configure ndb_redis sentinel
by mayamatakeshi 21 Oct '23

21 Oct '23

Hi, regarding ndb_redis, I have 3 sentinels like this: "192.168.88.155:26379" "192.168.88.156:26379" "192.168.88.157:26379" So was thinking that I would configure ndb_redis this way: modparam("ndb_redis", "server", "name=srvZ;sentinel_group=myredis;sentinel_master=1;sentinel= 192.168.88.155:26379") modparam("ndb_redis", "server", "name=srvZ;sentinel_group=myredis;sentinel_master=0;sentinel= 192.168.88.156:26379") modparam("ndb_redis", "server", "name=srvZ;sentinel_group=myredis;sentinel_master=0;sentinel= 192.168.88.157:26379") But the samples in the documentation show an extra sentinel key in the config lines: # sentinel (for a redis slave) modparam("ndb_redis", "server", "name=srvZ;sentinel_group=group_name;sentinel_master=0;sentinel=1.2.3.4:26379 ;sentinel=1.2.3.5:26379") # sentinel (for a redis master) modparam("ndb_redis", "server", "name=srvZ;sentinel_group=group_name;sentinel_master=1;sentinel=1.2.3.4:26379 ;sentinel=1.2.3.5:26379") So I am not sure if my configuration is correct. Can someone clarify?

1 0

lookup() and database
by Jawaid Bazyar 20 Oct '23

20 Oct '23

Hi, I have an application as follows: Multiple Kamailio Nodes Shared Postgres database Auth information will be stored in DB and accessed with Authdb. Here is the behavior I seek: I would like all the Kamailo nodes to cooperate in updating the database, each updating data as appropriate: When a registration comes in to any Node, and it authenticated, create or update a database record in location table. When a registration expires on that Node, delete database record in location table. When INVITE comes in on any Node, ignore local cache and always lookup() record from database. #1 and #2 are used so that a third SIP system can query the database and look up the Node a NAT’d subscriber is ‘connected’ to. #3 is to let NON-NAT’d subscribers be contacted from any Node. Now I have something close to this now – using following settings: modparam("usrloc", "db_mode", 1) # immediately write registrations to the database. modparam("usrloc", "db_timer_clean", 0) # do not expire DB records separately modparam("usrloc", "db_check_update", 1) This takes care of #1 and #2 above. However, #3 seems to still be relying purely on local cache and does not hit the database. Is there a way to do #3? I can set db_mode to 3 but that would seem to have other effects besides merely making lookup() read from database. Thanks in advance, Jawaid

3 8

TOPOS + Forcing the send socket
by Marrold 19 Oct '23

19 Oct '23

Hi all, I am using Kamailio (5.7.2, Debian 11, Python KEMI) in a mutli-homed environment with the topos module to hide the topology. I have noticed that when I use `set_send_socket` or `$fsn` to force the socket it's sent from, it breaks topos and the ACK is not proxied to the other leg of the call. I am calling record_route() *after* forcing the socket. If I disable TOPOS the ACK works as expected, and the signalling looks correct. Or, with TOPOS enabled, if I comment out set_send_socket TOPOS works as expected. If I disable enable_double_rr, TOPOS works as expected and the ACK is forwarded, but without the double RR subsequent in-dialog requests use the wrong socket. One other observation, when I change the send socket I also see these warnings in the logs: 24(32) WARNING: PY3 {ACK}: dialog [dlg_handlers.c:1348]: dlg_onroute(): tight matching failed for ACK with callid='!!:MByLMlFAM.NfWxFAM.cAMxyfWjyLz.yAO.y6MxF1MxVZWG4ZMy**'/55, ftag='2023101714101800015'/19, ttag='2f55349a-2c59-4e37-bf58-fd84fb69ece9'/36 and direction=0 24(32) WARNING: PY3 {ACK}: dialog [dlg_handlers.c:1355]: dlg_onroute(): dialog identification elements are callid='2023101714101800015@2900-0601-0284-80'/37, caller tag='2023101714101800015'/19, callee tag='2f55349a-2c59-4e37-bf58-fd84fb69ece9'/36 Is anyone using TOPOS + forcing the socket, or could someone advise where I am going wrong? Thanks in advance Matthew

3 8

Kamailio SIP proxy role
by Ali Taher 18 Oct '23

18 Oct '23

Hello, I'm using Kamailio as SIP proxy between Session Manager and SBC So here is the scenario : Session Manager sends a call (Invite) to Kamailio, kamailio needs to relay it to SBC after doing some modification. (-----Session Manager-----) ----------- > (----Kamailio----) ----------- > (-----SBC-----) My routing logic is similar to the below: route{ if ((method==OPTIONS) && (! uri=~"sip:.*[@]+.*")) { options_reply(); } if (is_method("INVITE")) { sql_query("cb", "select number from pool1 order by random() limit 1", "ra"); $var(rand)=$dbr(ra=>[0,0]); uac_replace_from($var(rand),"sip:$var(rand)@192.168.1.1"); xlog("L_INFO","Random: $var(rand)"); $var(ip) = $(ct{s.select,1,(a)}{s.select,0,;}{s.replace,>,}); remove_hf("Contact"); insert_hf("Contact: $var(rand) <sip:$var(rand)@$var(ip)>\r\n"); remove_hf("P-Asserted-Identity"); remove_hf("Route"); insert_hf("Route: <sip: 192.168.1.10>\r\n","Route"); record_route(); t_relay(); $td = "192.168.1.10"; $rd = "192.168.1.10"; t_relay(); } } Where: 192.168.1.1 is Kamailio IP 192.168.1.10 is SBC IP My question here is that Kamailio handle all in dialog messages between Session Manager and SBC? For example, after forwarding the invite packet to SBC, SBC sends 183 Session Progress to Kamailio, which in its turn relay it to the session manager, knowing that this is not mentioned in my routing logic, so how Kamailio knew that it must relay it to session manager in this case? Also I need to add to the 183 Session Progress sent to session manager by Kamailio record route and Via headers , how to do it ? Regards,

1 0

Dispatcher HA:won't route headers be wrong if in-dialog request is sent to backup?
by Richard Chan 18 Oct '23

18 Oct '23

Hi sr-users, In the case of dispatcher-based HA such as the Wazo example ( https://wazo-platform.org/blog/kamailio-ha-dispatcher-and-dmq) won't the Route: headers be wrong for in-dialog requests if the request is sent to the backup proxy? front proxy -> proxy A, B, C, D,... -> network Suppose the INVITE goes through proxy A, then proxy A goes down. Based on the HA logic, an in-dialog request will go to a backup, say, proxy B. However, won't the Route headers be wrong (since they are placed by A) in the original transaction? How do you handle Route:, Record-Route: headers at the HA tier? 1. In the front proxy & HA tier don't use route headers at all ?? 2. Manually check and remove route headers (i.e proxy B treats route headers for proxy A as "myself") ?? I am curious as to what is your practice. Regards Shih-Ping

1 0

Restarts Kamailio after general protection fault
by Daian Conrad 17 Oct '23

17 Oct '23

Hi all, I have started using kamailio as a proxy register for asterisk's and works fine, but in some moment kamailio show WARNINGs, ALERTS and CRITICAL logs and restart. I don't no how debug correctly, but the crash show this log lines *Oct 16 21:34:26 proxy /usr/sbin/kamailio[2148]: CRITICAL: <core> [core/mem/q_malloc.c:123]: qm_debug_check_frag(): BUG: qm: fragm. 0x7f14a27a5ab8 (address 0x7f14a27a5af0) beginning overwritten (7f14a27a8e58)! Memory allocator was called from uac: uac_send.c:860. Fragment marked by UH��AWAVAUATSH��:139726602009368. Exec from core/mem/q_malloc.c:511.* ------------------------------------------------------------- *Oct 16 21:39:46 proxy /usr/sbin/kamailio[2556]: CRITICAL: <core> [core/mem/q_malloc.c:123]: qm_debug_check_frag(): BUG: qm: fragm. 0x7ff7ad456330 (address 0x7ff7ad456368) beginning overwritten (0)! Memory allocator was called from uac: uac_send.c:860. Fragment marked by (null):0. Exec from core/mem/q_malloc.c:511.Oct 16 21:39:46 proxy /usr/sbin/kamailio[2578]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 19Oct 16 21:39:46 proxy /usr/sbin/kamailio[2539]: ALERT: <core> [main.c:774]: handle_sigs(): child process 2556 exited by a signal 6Oct 16 21:39:46 proxy /usr/sbin/kamailio[2539]: ALERT: <core> [main.c:777]: handle_sigs(): core was not generatedOct 16 21:39:46 proxy systemd[1]: kamailio.service: Main process exited, code=exited, status=1/FAILUREOct 16 21:39:46 proxy systemd[1]: kamailio.service: Failed with result 'exit-code'.Oct 16 21:39:46 proxy systemd[1]: kamailio.service: Service RestartSec=100ms expired, scheduling restart.Oct 16 21:39:46 proxy systemd[1]: kamailio.service: Scheduled restart job, restart counter is at 9.Oct 16 21:39:46 proxy systemd[1]: Stopped Kamailio - the Open Source SIP Server.* any advice is apreciated -- ================ **Daian Conrad** E-mail: daian.conrad(a)gmail.com OpenS Team (DaCoD) Linux user: #248912

2 3

ERROR: run_top_route
by satyaprakash ch 17 Oct '23

17 Oct '23

Hi, We are having an error in the Kamailio logs which we need to resolve this issue, ERROR is ::* /usr/local/sbin/kamailio[10149]: ERROR: tm [t_reply.c:1081]: run_failure_handlers(): error running run_top_route for failure handler.* We are getting this error at the time of the 3xx response, Can anyone help me on this? Thank you.

3 8

Wrong RTP endpoint announced by Kamailio when forwarding calls, but looks correct from RTPEngine
by Leonardo Arena 17 Oct '23

17 Oct '23

Hi all, I have the following setup: Phone <-> private net using TCP transport <-> (172.30.0.156) Kamailio v5.6.3 + RTPEngine v9.3.1 (22.33.177.156) <-> public net using UDP transport <-> Asterisk (22.33.178.77) Phone is registered on Kamailio and forward calls on no answer or when ext is unregistered, to Asterisk's custom IVR (nodejs app + CouchDB), using failure_route() [1]. The problem is that when the none answer the phone and the call is redirected to Asterisk, Kamailio announce its private IP address in the SDP connection endpoint, hence there is no audio [2]. From RTPEngine debug logs, it seems that RTPEngine replies with the correct SDP connection endpoint IP [3]. See also RTPEngine interfaces definition [4]. What am I missing? Why Kamailio is offering its private IP address in the SDP connection, instead of its public address when forwarding the call? If comment "route(SDP_MANAGE_IN)" in route[IN], Kamailio uses the correct IP endpoint address in the SDP offer when forwarding the call to Asterisk. But of course this breaks audio when someone answer the phone. It seems that Kamailio is storing the initial SDP offer settings and does not update it upon RTPEngine's request, even though I have added "replace-session-connection" in route[SDP_OFFER_IVR]. Thanks for any help! leo [1] route[IN] { if (!lookup('location')) { t_on_reply("SDP_MANAGE"); route(TOIVR); } else { xlog("L_INFO", "Route(IN) Req $mi $rm From <$fu> To <$tu> RURI <$ru>\n"); record_route(); t_on_reply("SDP_MANAGE"); route(SDP_MANAGE_IN); t_on_failure("TOIVR"); t_relay(); exit; } } route[SDP_MANAGE] { if (has_body("application/sdp")) { rtpengine_manage(); } } route[SDP_MANAGE_IN] { if (has_body("application/sdp")) { rtpengine_manage("direction=public direction=private via-branch=1"); } } ... route[SDP_OFFER_IVR] { if (has_body("application/sdp")) { rtpengine_offer("direction=public direction=public replace-session-connection via-branch=1"); } } failure_route[TOIVR] { if (t_is_canceled()) { exit; } append_branch(); route(SDP_OFFER_IVR); # using t_relay_to so that UDP is used with the correct IP address if (!t_relay_to("xh.voip.net")) { xlog("L_INFO", "No answer - Failure Route(TOIVR) Req $mi $rm From <$fu> To <$tu> RURI <$ru> failed\n"); t_reply("500", "Unable to route"); } else { xlog("L_INFO", "No answer - Failure Route(TOIVR) Req $mi $rm From <$fu> To <$tu> RURI <$ru>\n"); } } [2] U 2023/10/11 09:05:43.797393 22.33.177.156:5060 -> 22.33.176.8:5060 #3 SIP/2.0 180 Ringing. Via: SIP/2.0/UDP 22.33.176.8;branch=z9hG4bK2cb2.e559c4a326678f69ae9b4656be7bc36c.0. Via: SIP/2.0/UDP 22.33.176.20;branch=z9hG4bK2cb2.2920561c845ee5279051359f40cb7c0f.0. Via: SIP/2.0/UDP 44.55.73.157:5060;branch=z9hG4bK0cBdccef20c0d8bfefb. Record-Route: <sip:172.30.0.156;transport=TCP;r2=on;lr=on;ftag=gK0c1bb12e>. Record-Route: <sip:22.33.177.156;r2=on;lr=on;ftag=gK0c1bb12e>. Record-Route: <sip:22.33.176.8;lr=on;ftag=gK0c1bb12e;did=7ffe.26c8>. Record-Route: <sip:22.33.176.20;lr=on;ftag=gK0c1bb12e>. From: "Unavailable" <sip:013335553222@44.55.73.157>;tag=gK0c1bb12e. To: <sip:8555000033@22.33.176.20>;tag=660096088. Call-ID: 474758100_116775912(a)44.55.73.157. CSeq: 704680 INVITE. Contact: <sip:+18555000033@172.30.96.2:11815;transport=TCP>. Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE. User-Agent: Yealink SIP-T31P 124.86.0.40. Allow-Events: talk,hold,conference,refer,check-sync. Content-Length: 0. . U 2023/10/11 09:06:03.751585 22.33.177.156:5060 -> 22.33.178.77:5060 #4 INVITE sip:+18555000033@172.30.96.2:11815;transport=TCP SIP/2.0. Record-Route: <sip:22.33.177.156;lr=on;ftag=gK0c1bb12e>. Record-Route: <sip:22.33.176.8;lr=on;ftag=gK0c1bb12e;did=7ffe.26c8>. Record-Route: <sip:22.33.176.20;lr=on;ftag=gK0c1bb12e>. Via: SIP/2.0/UDP 22.33.177.156;branch=z9hG4bK2cb2.afb825e30e294872c72c5e21ef26f3f3.1. Via: SIP/2.0/UDP 22.33.176.8;branch=z9hG4bK2cb2.e559c4a326678f69ae9b4656be7bc36c.0. Via: SIP/2.0/UDP 22.33.176.20;branch=z9hG4bK2cb2.2920561c845ee5279051359f40cb7c0f.0. Via: SIP/2.0/UDP 44.55.73.157:5060;branch=z9hG4bK0cBdccef20c0d8bfefb. f: "Unavailable" <sip:013335553222@44.55.73.157>;tag=gK0c1bb12e. t: <sip:8555000033@22.33.176.20>. i: 474758100_116775912(a)44.55.73.157. CSeq: 704680 INVITE. Max-Forwards: 32. Allow: INVITE,ACK,CANCEL,BYE,REGISTER,REFER,INFO,SUBSCRIBE,NOTIFY,PRACK,UPDATE,OPTIONS,MESSAGE,PUBLISH. Accept: application/sdp, application/isup, application/dtmf, application/dtmf-relay, multipart/mixed. m: "Unavailable" <sip:013335553222@44.55.73.157:5060>. Remote-Party-ID: "Unavailable" <sip:013335553222@44.55.73.157:5060>;privacy=off. k: timer,100rel,precondition. Session-Expires: 1800. Min-SE: 90. l: 604. Content-Disposition: session; handling=required. c: application/sdp. . v=0. o=Sonus_UAC 525653 764118 IN IP4 44.55.73.157. s=SIP Media Capabilities. c=IN IP4 172.30.0.156. t=0 0. m=audio 30030 RTP/AVP 0 18 101. a=maxptime:20. a=rtpmap:0 PCMU/8000. a=rtpmap:18 G729/8000. a=fmtp:18 annexb=n [3] Oct 11 09:06:03 voipsipr7 daemon.info rtpengine[35061]: INFO: [474758100_116775912(a)44.55.73.157]: [control] Received command 'offer' from 127.0.0.1:39942 Oct 11 09:06:03 voipsipr7 daemon.debug rtpengine[35061]: DEBUG: [474758100_116775912(a)44.55.73.157]: [control] Dump for 'offer' from 127.0.0.1:39942: { "supports": [ "load limit" ], "sdp": "v=0^M o=Sonus_UAC 5 25653 764118 IN IP4 44.55.73.157^M s=SIP Media Capabilities^M c=IN IP4 44.55.78.60^M t=0 0^M m=audio 61610 RTP/AVP 0 18 101^M a=rtpmap:0 PCMU/8000^M a=rtpmap:18 G729/8000^M a=fmtp:18 annexb=no^M a=rtpmap:101 telephone-event/8000^M a=fmtp:101 0-15^M a=sendrecv^M a=maxptime:20^M ", "direction": [ "public", "public" ], "replace": [ "session-connection" ], "call-id": "474758100_116775912(a)44.55.73.157 ... Oct 11 09:06:03 voipsipr7 daemon.debug rtpengine[35061]: DEBUG: [474758100_116775912(a)44.55.73.157]: ... ", "via-branch": "z9hG4bK2cb2.e559c4a326678f69ae9b4656be7bc36c.0", "received-from": [ "IP4", "22.33.176 .8" ], "from-tag": "gK0c1bb12e", "command": "offer" } ... Oct 11 09:06:03 voipsipr7 daemon.info rtpengine[35061]: INFO: [474758100_116775912(a)44.55.73.157]: [control] Replying to 'offer' from 127.0.0.1:39942 (elapsed time 0.000638 sec) Oct 11 09:06:03 voipsipr7 daemon.debug rtpengine[35061]: DEBUG: [474758100_116775912(a)44.55.73.157]: [control] Response dump for 'offer' to 127.0.0.1:39942: { "sdp": "v=0^M o=Sonus_UAC 525653 764118 IN IP4 207 .223.73.157^M s=SIP Media Capabilities^M c=IN IP4 22.33.177.156^M t=0 0^M m=audio 30068 RTP/AVP 0 18 101^M a=maxptime:20^M a=rtpmap:0 PCMU/8000^M a=rtpmap:18 G729/8000^M a=fmtp:18 annexb=no^M a=rtpmap:101 teleph one-event/8000^M a=fmtp:101 0-15^M a=sendrecv^M a=rtcp:30069^M ", "result": "ok" } Oct 11 09:06:03 voipsipr7 daemon.info /usr/sbin/kamailio[35261]: INFO: <script>: No answer - Failure Route(TOIVR) Req 4 INVITE From <sip:013335553222@44.55.73.157> To <sip:8555000033@22.33.176.20> RURI <sip: +18555000033@172.30.96.2:11815;transport=TCP> Oct 11 09:06:03 voipsipr7 daemon.info rtpengine[35061]: INFO: [474758100_116775912(a)44.55.73.157]: [control] Received command 'answer' from 127.0.0.1:53245 Oct 11 09:06:03 voipsipr7 daemon.debug rtpengine[35061]: DEBUG: [474758100_116775912(a)44.55.73.157]: [control] Dump for 'answer' from 127.0.0.1:53245: { "supports": [ "load limit" ], "sdp": "v=0^M o=- 525653 7 64120 IN IP4 22.33.178.77^M s=Asterisk^M c=IN IP4 22.33.178.77^M t=0 0^M m=audio 11264 RTP/AVP 0 101^M a=rtpmap:0 PCMU/8000^M a=rtpmap:101 telephone-event/8000^M a=fmtp:101 0-16^M a=ptime:20^M a=maxptime:150^M a=sendrecv^M m=audio 0 RTP/AVP 0 18 101^M ", "call-id": "474758100_116775912(a)44.55.73.157", "received-from": [ "IP4", "22.33.178.77" ], "from-tag": "gK0c1bb12e", "to-tag": "a21c53b6-ca33-43b ... Oct 11 09:06:03 voipsipr7 daemon.debug rtpengine[35061]: DEBUG: [474758100_116775912(a)44.55.73.157]: ... 4-a585-af9b568a5ecb", "command": "answer" } ... Oct 11 09:06:03 voipsipr7 daemon.info rtpengine[35061]: INFO: [474758100_116775912(a)44.55.73.157]: [control] Replying to 'answer' from 127.0.0.1:53245 (elapsed time 0.000915 sec) Oct 11 09:06:03 voipsipr7 daemon.debug rtpengine[35061]: DEBUG: [474758100_116775912(a)44.55.73.157]: [control] Response dump for 'answer' to 127.0.0.1:53245: { "sdp": "v=0^M o=- 525653 764120 IN IP4 22.33.178 .77^M s=Asterisk^M c=IN IP4 22.33.177.156^M t=0 0^M m=audio 30056 RTP/AVP 0 101^M a=maxptime:150^M a=rtpmap:0 PCMU/8000^M a=rtpmap:101 telephone-event/8000^M a=fmtp:101 0-16^M a=sendrecv^M a=rtcp:30057^M a=ptime :20^M m=audio 0 RTP/AVP 0 18 101^M ", "result": "ok" } Oct 11 09:06:03 voipsipr7 daemon.debug rtpengine[35061]: DEBUG: [474758100_116775912(a)44.55.73.157]: [core] Forward to sink endpoint: 22.33.178.77:11264 (RTP seq 0 TS 0) [4] Interface definition in RTPEngine: interface = public/22.33.177.156;public/22:33:201:105::156;private/172.30.0.156

3 3

Switching DMQ transport to TCP?
by Benoit Panizzon 17 Oct '23

17 Oct '23

Hi Gang While still hunting DMQ issues, I noticed that the OS is reporting UDP drops. Maybe DMQ packets? Would DMQ re-send a lost packet? I increased OS UDP RX buffers times 10 and monitoring counters. I also found that DMQ can use tcp or tls as transport. Could this help to prevent loosing DMQ messages? Or is this prone to cause new issues? 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

UDP Fragmentation webRTC/UDP Call
by Social Boh 16 Oct '23

16 Oct '23

Hello, I'm trying to solve a problem with calls WebRTC/UDP. I think is a fragmentation problem because udp/webRTC calls works without problem. The INVITE from Kamailio to the UDP device not receive any type of answer. I'm trying to reduce the SDP annex size using: |sdp_remove_line_by_prefix| for some lines unsuccessfully. Maybe I don't know where put this function in the script. Or, is there another way to solve this issue? Thank you in advance Regards -- --- I'm SoCIaL, MayBe

5 10

Dialog Module: enable_dmq and multiple nodes update SAME profiles_with_value counter?
by Benoit Panizzon 16 Oct '23

16 Oct '23

Hi Team I'm still hunting down DMQ dialog issues. https://www.kamailio.org/docs/modules/devel/modules/dialog.html#dialog.p.en… Quote: "Notably, it is not possible to send in-dialog requests on any but the original proxy instance." I make sure, that if a procied call (with same callID) is being redirected from anywhere, it is send to the came dialog aware kamailio instance it originated from. This seems to have fixed a lot of issues with dialogues getting corrupted. The two main purposed we use dialog is: * CDR * Channel Counting / Limiting modparam("dialog", "profiles_with_value", "custprofilecounter"); Can a such profile WITH value be written from any node sharing dialog via DMQ or is this bound to cause troubes? Example. Two call get to same customer, but over two different nodes. Node A is getting a call: set_dlg_profile("custprofilecounter","Customer7664"); get_profile_size("custprofilecounter","Customer7664","$var(busy_count)"); => $var(busy_count) is now 1. The profile is replicated to Node B and the value can be accessed there. While Call on Node A is running, Node B is getting a call to same customer: set_dlg_profile("custprofilecounter","Customer7664"); get_profile_size("custprofilecounter","Customer7664","$var(busy_count)"); => $var(busy_count) is now 2 on Node B. Is this value being replicated BACK to Node A where the profile counter originally was created? As far as I have experienced, this is the case. But what happens if the call on Node B is ending before the Call on Node A? Will the counter being decreased also correctly be replicated to Node A? What happens the other way round? What happens if both call end at the same time? Is a race condition possible, or is there some sort of locking to prevent this? Can I use profiles_with_value the way I use them? Or is this bound to fail because it's not supported? 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

Discrepancy between RPC stats and real data from the UAC module
by Denys Pozniak 16 Oct '23

16 Oct '23

Hello! We use the UAC module for outbound registrations and when we try to get RPC statistics we see that the data does not match, what could be the reason? # kamcmd stats.get_statistics uac: uac:regactive = 14 uac:regdisabled = 0 uac:regtotal = 0 # kamctl rpc uac.reg_dump | grep flag | grep 20 -c 745 # kamailio -v version: kamailio 5.6.4 (x86_64/linux) flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_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: unknown compiled with gcc 10.2.1 -- BR, Denys Pozniak

1 0

Re: Crypto module AES algorithm details
by Henning Westerholt 16 Oct '23

16 Oct '23

(Please keep the list in CC) Hello, The web tools might use another logic internally. I had some success with a java library use case and also with PostgreSQL, I think. A usual use-case is to have an encrypted password value in a DB, for data at rest encryption. The password is encrypted from something else. Then inside the Kamailio cfg you want to encrypt it on the fly, to use it for example for challenging a phone with username/password. Maybe you can give it a try with some python or other script languages, where you can play with the different crypto system parameter more easily. Cheers, Henning -- Henning Westerholt – https://skalatan.de/blog/ Kamailio services – https://gilawa.com<https://gilawa.com/> From: Jayesh Nambiar <jayesh1017(a)gmail.com> Sent: Donnerstag, 5. Oktober 2023 06:41 To: Henning Westerholt <hw(a)gilawa.com> Subject: Re: [SR-Users] Crypto module AES algorithm details Hello Henning, Thanks for the super fast reply. I tested this within kamailio 5.3.4 and I can successfully encrypt a header value and also the same encrypted value decrypts to proper plain text when. But when I compare the encrypted text with online resources like https://www.devglan.com/online-tools/aes-encryption-decryption and https://www.javainuse.com/aesgenerator, their encrypted text value is different from what I see from kamailio. Both these resources produce the same encrypted text while the encrypted text from kamailio is different. How do I validate this? My use case is as follows: -- I get an encrypted text in a SIP Header -- I decrypt it and validate it against some DB -- If valid proceed or else exit Now if the algorithm doesnt match exactly, there are chances of error, hence asking question on how to validate it. On Wed, Oct 4, 2023 at 1:43 PM Henning Westerholt <hw(a)gilawa.com<mailto:hw@gilawa.com>> wrote: Hello Jayesh, AFAIK its uses AES 256 with CBC mode. The IV is generated from OpenSSL, e.g. https://www.openssl.org/docs/man3.0/man3/EVP_BytesToKey.html For newer versions I have added the init_vector functionality to enable interoperability with other crypto functions, e.g. some databases, java frameworks etc. If you want to use this functionality, I’d suggest to update, as the 5.3. is also end of life since some time. Otherwise you can of course also backport this feature. Cheers, Henning -- Henning Westerholt – https://skalatan.de/blog/ Kamailio services – https://gilawa.com<https://gilawa.com/> From: Jayesh Nambiar via sr-users <sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org>> Sent: Mittwoch, 4. Oktober 2023 08:54 To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org>> Cc: Jayesh Nambiar <jayesh1017(a)gmail.com<mailto:jayesh1017@gmail.com>> Subject: [SR-Users] Crypto module AES algorithm details Hello, I am running kamailio-5.3.4 on one of my setup and I intend to use the crypto module in the same. I wanted to understand the following details when the module is used: I understand it uses the AES algorithm, is that correct? Does it use AES 128, 192 or 256 bit algorithms? Does it use CBC or ECB mode for AES? The 5.3 version does not have an parameter for init-vector, so does kamailio use any init vector internally in this case? When i compared the encrypted text that kamailio produces and the ones available online, they were producing different outputs even when same shared secret was used. Hence asking for more clarification PS: Upgrading kamailio is my very last option as this is one af an old setup which only needs this feature without much changes. Thanks for any valuable response. -- Jayesh

2 2

503(service unavailable)
by masoud96＠mail.ru 16 Oct '23

16 Oct '23

Hello! It often happens to me that the service begins to refuse service (503) and so far I have not been able to understand the exact reason. Typically, before clients start receiving 503, many before them receive a 408 code. As soon as the service starts responding with 503, it does not recover on its own, you have to restart. There is no way to understand from the logs what led to this (nothing unusual). My server is powerful enough for the number of users of my service (what I mean is that there is no problem with resources). For example, 64 cores, 125GB of DDR4 RAM, 2TB of disk, of which 1TB SSD for the database, 10Gigabit channel, this is only a server for Kamailio for Rtpengines separate servers. Please help me figure out what causes a service failure!? OS: Debian 11, 64 cores, 125GB of DDR4 RAM; DB: MariaDB 10.5.15; kamailio -v version: kamailio 5.5.3 (x86_64/linux) 473cef 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. udp_children: 30; tcp_children: 34; TLS: YES; async_workers: 64. Incoming calls are sent via push notifications( Federico Cabiddu method: https://www.voztovoice.org/sites/default/files/KamilioWorld2015%20-Federico…). NetBridging(for SIP and RTPEngine). ims_charging for billing (integration with our billing system using the Diameter protocol). In the logs exactly at the moment when the service began to refuse, the recording disappears completely for 7 minutes, absolutely no entries, after which the recording of the TCP queue full begins. Oct 3 18:38:07 sip1-life3 kamailio[3380553]: CRITICAL: {2 3691 INVITE 672699d1-c76b-4153-b72a-fe647913a9e9} tm [../../core/forward.h:292]: msg_send_buffer(): tcp_send failed Oct 3 18:38:09 sip1-life3 kamailio[3380539]: CRITICAL: {2 3691 INVITE 672699d1-c76b-4153-b72a-fe647913a9e9} tm [../../core/forward.h:292]: msg_send_buffer(): tcp_send failed Oct 3 18:38:12 sip1-life3 kamailio[3380534]: CRITICAL: {2 30106 INVITE 032f8650-1d90-49ed-82f1-c50ccbef191d} tm [../../core/forward.h:292]: msg_send_buffer(): tcp_send failed Oct 3 18:45:14 sip1-life3 /usr/local/sbin/kamailio[3380778]: CRITICAL: [core/tcp_main.c:4170]: send2child(): tcp child 11, socket 224: queue full, 285 requests queued (total handled 2899418) Oct 3 18:45:15 sip1-life3 /usr/local/sbin/kamailio[3380778]: CRITICAL: [core/tcp_main.c:4170]: send2child(): tcp child 1, socket 204: queue full, 286 requests queued (total handled 2964063) Oct 3 18:45:15 sip1-life3 /usr/local/sbin/kamailio[3380778]: CRITICAL: [core/tcp_main.c:4170]: send2child(): tcp child 4, socket 210: queue full, 286 requests queued (total handled 2923484) Oct 3 18:45:15 sip1-life3 /usr/local/sbin/kamailio[3380778]: CRITICAL: [core/tcp_main.c:4170]: send2child(): tcp child 6, socket 214: queue full, 286 requests queued (total handled 2911633) Oct 3 18:45:15 sip1-life3 /usr/local/sbin/kamailio[3380778]: CRITICAL: [core/tcp_main.c:4170]: send2child(): tcp child 7, socket 216: queue full, 286 requests queued (total handled 2907132) Oct 3 18:45:15 sip1-life3 /usr/local/sbin/kamailio[3380778]: CRITICAL: [core/tcp_main.c:4170]: send2child(): tcp child 8, socket 218: queue full, 286 requests queued (total handled 2903281) Oct 3 18:45:15 sip1-life3 /usr/local/sbin/kamailio[3380778]: CRITICAL: [core/tcp_main.c:4170]: send2child(): tcp child 9, socket 220: queue full, 286 requests queued (total handled 2903438) Oct 3 18:45:15 sip1-life3 /usr/local/sbin/kamailio[3380778]: CRITICAL: [core/tcp_main.c:4170]: send2child(): tcp child 11, socket 224: queue full, 286 requests queued (total handled 2899419) Oct 3 18:45:15 sip1-life3 /usr/local/sbin/kamailio[3380778]: CRITICAL: [core/tcp_main.c:4170]: send2child(): tcp child 12, socket 226: queue full, 286 requests queued (total handled 2897842) Oct 3 18:45:16 sip1-life3 /usr/local/sbin/kamailio[3380778]: CRITICAL: [core/tcp_main.c:4170]: send2child(): tcp child 16, socket 234: queue full, 286 requests queued (total handled 2895429) Oct 3 18:45:16 sip1-life3 /usr/local/sbin/kamailio[3380778]: CRITICAL: [core/tcp_main.c:4170]: send2child(): tcp child 17, socket 236: queue full, 286 requests queued (total handled 2895303) Oct 3 18:45:16 sip1-life3 /usr/local/sbin/kamailio[3380778]: CRITICAL: [core/tcp_main.c:4170]: send2child(): tcp child 22, socket 246: queue full, 286 requests queued (total handled 2891873) Oct 3 18:45:16 sip1-life3 /usr/local/sbin/kamailio[3380778]: CRITICAL: [core/tcp_main.c:4170]: send2child(): tcp child 26, socket 254: queue full, 286 requests queued (total handled 2892619) Oct 3 18:45:16 sip1-life3 /usr/local/sbin/kamailio[3380778]: CRITICAL: [core/tcp_main.c:4170]: send2child(): tcp child 27, socket 256: queue full, 286 requests queued (total handled 2891769) Oct 3 18:45:16 sip1-life3 /usr/local/sbin/kamailio[3380778]: ERROR: [core/tcp_main.c:3458]: send_fd_queue_run(): send_fd failed on socket 224 , queue entry 0, retries 98, connection 0x7f0b6d974348, tcp so Oct 3 18:45:16 sip1-life3 /usr/local/sbin/kamailio[3380778]: CRITICAL: [core/tcp_main.c:4170]: send2child(): tcp child 30, socket 262: queue full, 286 requests queued (total handled 2891614) Oct 3 18:45:16 sip1-life3 /usr/local/sbin/kamailio[3380778]: CRITICAL: [core/tcp_main.c:4170]: send2child(): tcp child 31, socket 264: queue full, 286 requests queued (total handled 2890778) Oct 3 18:45:16 sip1-life3 /usr/local/sbin/kamailio[3380778]: CRITICAL: [core/tcp_main.c:4170]: send2child(): tcp child 33, socket 268: queue full, 286 requests queued (total handled 2890852) Oct 3 18:45:16 sip1-life3 /usr/local/sbin/kamailio[3380778]: CRITICAL: [core/tcp_main.c:4170]: send2child(): tcp child 0, socket 202: queue full, 287 requests queued (total handled 3071438) Oct 3 18:45:17 sip1-life3 /usr/local/sbin/kamailio[3380778]: CRITICAL: [core/tcp_main.c:4170]: send2child(): tcp child 1, socket 204: queue full, 287 requests queued (total handled 2964064) Oct 3 18:45:17 sip1-life3 /usr/local/sbin/kamailio[3380778]: CRITICAL: [core/tcp_main.c:4170]: send2child(): tcp child 2, socket 206: queue full, 287 requests queued (total handled 2944928) Oct 3 18:45:17 sip1-life3 /usr/local/sbin/kamailio[3380778]: CRITICAL: [core/tcp_main.c:4170]: send2child(): tcp child 4, socket 210: queue full, 287 requests queued (total handled 2923485) Oct 3 18:45:17 sip1-life3 /usr/local/sbin/kamailio[3380778]: CRITICAL: [core/tcp_main.c:4170]: send2child(): tcp child 5, socket 212: queue full, 287 requests queued (total handled 2915778) Oct 3 18:45:17 sip1-life3 /usr/local/sbin/kamailio[3380778]: CRITICAL: [core/tcp_main.c:4170]: send2child(): tcp child 6, socket 214: queue full, 287 requests queued (total handled 2911634) Oct 3 18:45:17 sip1-life3 /usr/local/sbin/kamailio[3380778]: CRITICAL: [core/tcp_main.c:4170]: send2child(): tcp child 7, socket 216: queue full, 287 requests queued (total handled 2907133) Oct 3 18:45:17 sip1-life3 /usr/local/sbin/kamailio[3380778]: CRITICAL: [core/tcp_main.c:4170]: send2child(): tcp child 8, socket 218: queue full, 287 requests queued (total handled 2903282) Oct 3 18:45:17 sip1-life3 /usr/local/sbin/kamailio[3380778]: CRITICAL: [core/tcp_main.c:4170]: send2child(): tcp child 9, socket 220: queue full, 287 requests queued (total handled 2903439) Oct 3 18:45:17 sip1-life3 /usr/local/sbin/kamailio[3380778]: CRITICAL: [core/tcp_main.c:4170]: send2child(): tcp child 10, socket 222: queue full, 287 requests queued (total handled 2900227) Oct 3 18:45:17 sip1-life3 /usr/local/sbin/kamailio[3380778]: CRITICAL: [core/tcp_main.c:4170]: send2child(): tcp child 11, socket 224: queue full, 287 requests queued (total handled 2899420) Oct 3 18:45:17 sip1-life3 /usr/local/sbin/kamailio[3380778]: CRITICAL: [core/tcp_main.c:4170]: send2child(): tcp child 12, socket 226: queue full, 287 requests queued (total handled 2897843) Oct 3 18:45:17 sip1-life3 /usr/local/sbin/kamailio[3380778]: ERROR: [core/tcp_main.c:3458]: send_fd_queue_run(): send_fd failed on socket 204 , queue entry 0, retries 88, connection 0x7f0b742a1968, tcp so Oct 3 18:45:17 sip1-life3 /usr/local/sbin/kamailio[3380778]: CRITICAL: [core/tcp_main.c:4170]: send2child(): tcp child 13, socket 228: queue full, 287 requests queued (total handled 2896210) Oct 3 18:45:17 sip1-life3 /usr/local/sbin/kamailio[3380778]: ERROR: [core/tcp_main.c:3458]: send_fd_queue_run(): send_fd failed on socket 210 , queue entry 0, retries 86, connection 0x7f0b74ffaa08, tcp so Oct 3 18:45:17 sip1-life3 /usr/local/sbin/kamailio[3380778]: CRITICAL: [core/tcp_main.c:4170]: send2child(): tcp child 16, socket 234: queue full, 287 requests queued (total handled 2895430) Oct 3 18:45:17 sip1-life3 /usr/local/sbin/kamailio[3380778]: ERROR: [core/tcp_main.c:3458]: send_fd_queue_run(): send_fd failed on socket 214 , queue entry 0, retries 88, connection 0x7f0b75003218, tcp so Oct 3 18:45:17 sip1-life3 /usr/local/sbin/kamailio[3380778]: ERROR: [core/tcp_main.c:3458]: send_fd_queue_run(): send_fd failed on socket 216 , queue entry 1, retries 86, connection 0x7f0b75007620, tcp so Oct 3 18:45:17 sip1-life3 /usr/local/sbin/kamailio[3380778]: ERROR: [core/tcp_main.c:3458]: send_fd_queue_run(): send_fd failed on socket 218 , queue entry 2, retries 84, connection 0x7f0b74772f70, tcp so Oct 3 18:45:17 sip1-life3 /usr/local/sbin/kamailio[3380778]: CRITICAL: [core/tcp_main.c:4170]: send2child(): tcp child 17, socket 236: queue full, 287 requests queued (total handled 2895304) Oct 3 18:45:17 sip1-life3 /usr/local/sbin/kamailio[3380778]: ERROR: [core/tcp_main.c:3458]: send_fd_queue_run(): send_fd failed on socket 220 , queue entry 0, retries 87, connection 0x7f0b74777378, tcp so Oct 3 18:45:17 sip1-life3 /usr/local/sbin/kamailio[3380778]: ERROR: [core/tcp_main.c:3458]: send_fd_queue_run(): send_fd failed on socket 224 , queue entry 1, retries 83, connection 0x7f0b7477fb88, tcp so Oct 3 18:45:17 sip1-life3 /usr/local/sbin/kamailio[3380778]: CRITICAL: [core/tcp_main.c:4170]: send2child(): tcp child 21, socket 244: queue full, 287 requests queued (total handled 2893042)

4 7

183 Session Progress Acknowledgment
by Ali Taher 14 Oct '23

14 Oct '23

Hello, Is there a way to send PRACK as reply to a 183 Session Progress (with Require: 100rel) sent to Kamailio sip proxy? Regards,

2 3

Kamailio as SIP proxy
by Ali Taher 12 Oct '23

12 Oct '23

Hello, I'm using Kamailio as SIP proxy between Session Manager and SBC So here is the scenario : Session Manager sends a call (Invite) to Kamailio, kamailio needs to relay it to SBC after doing some modification. (-----Session Manager-----) ----------- > (----Kamailio----) ----------- > (-----SBC-----) My routing logic is similar to the below: route{ if ((method==OPTIONS) && (! uri=~"sip:.*[@]+.*")) { options_reply(); } if (is_method("INVITE")) { sql_query("cb", "select number from pool1 order by random() limit 1", "ra"); $var(rand)=$dbr(ra=>[0,0]); uac_replace_from($var(rand),"sip:$var(rand)@192.168.1.1"); xlog("L_INFO","Random: $var(rand)"); $td = "192.168.1.10"; $rd = "192.168.1.10"; t_relay(); } } Where: 192.168.1.1 is Kamailio IP 192.168.1.10 is SBC IP The issue is that I'm not sure to handle the other SIP packets like 183,CANCEL, BYE etc that can be received from both SBC and session Manager? What to add to my configuration to handle it properly? Regards,

2 1

Using DMQ to sync the TM module.
by Michel Pelletier 11 Oct '23

11 Oct '23

Hi, I have 2 kamailio instances behind a load balancer. The problem I have is that the load balancer can only track TCP connections, but not UDP. So one Kamailio instance might send a request using UDP, while the corresponding UDP reply arrives on the other. This doesn't play well with the (stateful) TM module. Is there a way to synchronize the TM module accross Kamailio instances using DMQ? Cheers, Michel Pelletier

4 8

rtpproxy -- timeout_socket
by James Lipski 11 Oct '23

11 Oct '23

Hello, I'm a bit confused about a piece of the documentation. I'm using rtpproxy 3.0.1 + rtpproxy module on kamailio 5.6.4. On the rtpproxy module, I'm trying to get the "timeout_socket" param working. From the documentation, I have modparam("rtpproxy", "timeout_socket", "xmlrpc:http://192.168.155.64:8888/XMLRPC") modparam("xmlrpc", "route", "XMLRPC_ROUTE") modparam("xmlrpc", "mode", 1) modparam("xmlrpc", "url_match", "^/XMLRPC") /usr/bin/rtpproxy -i -u rtpproxy -n tcp:192.168.155.64:8888 -l 192.168.155.64 -s udp:127.0.0.1:7333 -m 29152 -M 49150 -d DBUG However when purposely trying to timeout RTP, I'm seeing the following in my rtpproxy logs: Oct 10 00:31:22 localhost rtpproxy[3802129]: DBUG:GLOBAL:rtpp_command_split:401: received command "3801518_4 USc9,0,8,18,101 219b2465decc-n7al36xva4lw 192.168.155.168 2266 C60D788E-8E14A9FA;1 w6p2ke9ttk;1 xmlrpc:http://192.168.155.64:8888/XMLHTTP" Oct 10 00:31:22 localhost rtpproxy[3802129]: ERR:219b2465decc-n7al36xva4lw:rtpp_command_ul_handle:603: invalid socket name w6p2ke9ttk;1 I'm just wondering if I'm missing anything, do I need to define "listen=tcp:192.168.155.64:8888" in my configs? I know that rtpengine is recommended/ I would like to experiement with rtpproxy. Do I need a specific version of rtpproxy in order for this to work -- I did try it with 2.1.1 however that didn't work. Thanks.

2 2

Kamailio Developers Meeting, Nov 7-8, 2023, in Dusseldorf
by Daniel-Constantin Mierla 11 Oct '23

11 Oct '23

Hello, Kamailio SIP Server project is organizing another meeting of its developers and community members during November 7-8, 2023, hosted again by sipgate.de in Dusseldorf, Germany. The event is intended to facilitate the interaction between Kamailio developers and contributors in order to offer a convenient environment for working together on several topics of high interest for the project, including writing code for Kamailio and its tools, improving documentation, or discuss about future development. Everyone from the community is welcome to join, developer or user interested in helping the project. Please note we have a limited capacity of seats in the meeting room, the main policy for accepting participants being first come first server. Also, very important to be aware that this is not an event to learn how to use Kamailio. More details about the event, the venue, how to register, are available at: * https://www.kamailio.org/w/developers-meeting/ Looking forward to those two intensive hacking Kamailio days in Dusseldorf! Cheers, Daniel -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy and Development Services Kamailio Advanced Training - Online - Nov 14-16, 2023 -- asipto.com

1 0

Error reporting when developing a custom module to link to a third-party library
by bikq＠163.com 11 Oct '23

11 Oct '23

Dear friends, I have a question: When adding a custom module in kamailio, I referenced a third-party library. There was no problem with compilation, but when I ran it, it reported that the third-party library could not be found. What is the reason? The current Makefile is as follows： ``` # WARNING: do not run this directly, it should be run by the main Makefile include ../../Makefile.defs auto_gen= NAME=rocketmq.so THIRDPARTY=/mnt/vdd/kqbi2/3rdparty ROCKETMQ_ROOT_PATH=${THIRDPARTY}/rocketmq CXX?=g++ LD?=g++ LIBS+=-L$(LOCALBASE)/lib -L$(ROCKETMQ_ROOT_PATH)/lib/linux/x64 crocketmq.o -lstdc++ -lrocketmq DEFS+=-I$(LOCALBASE)/include -I${ROCKETMQ_ROOT_PATH}/include CXXFLAGS=$(CFLAGS:-Wno-deprecated option=) CXXFLAGS+=-Wno-write-strings -Wno-deprecated -Wno-unused-function -Wno-sign-compare -Wno-strict-aliasing include ../../Makefile.modules crocketmq.o: crocketmq.cpp crocketmq.h @echo "Compiling $<" $(CXX) -std=c++11 $(CXXFLAGS) $(CFLAGS) $(C_DEFS) $(DEFS) -c $< -o $@ rocketmq.so: crocketmq.o modclean: -@rm -f crocketmq.o crocketmq.d rocketmq_mod.o rocketmq_mod.d clean clean-modules: modclean proper realclean distclean maintainer-clean: modclean ``` There is no problem in compiling, but when running, the third-party librocketmq.so library cannot be found, and various export LD_LIBRARY_LIBRARY also does not work. ``` 0(13229) DEBUG: <core> [core/cfg.y:2053]: yyparse(): loading module rocketmq.so 0(13229) DEBUG: <core> [core/sr_module.c:516]: ksr_locate_module(): found module to load <lib64/kamailio/modules/rocketmq.so> 0(13229) DEBUG: <core> [core/sr_module.c:573]: ksr_load_module(): trying to load <lib64/kamailio/modules/rocketmq.so> 0(13229) ERROR: <core> [core/sr_module.c:591]: ksr_load_module(): could not open module <lib64/kamailio/modules/rocketmq.so>: librocketmq.so: cannot open shared object file: No such file or directory 0(13229) CRITICAL: <core> [core/cfg.y:3900]: yyerror_at(): parse error in config file /mnt/vdd/kqbi2/install/kamailio/etc/kamailio/kamailio.cfg, line 380, column 12-24: failed to load module ```

1 2

Serial Forking with differing next hop for each branch?
by Barry Flanagan 10 Oct '23

10 Oct '23

Hi I have a scenario where I need to implement serial forking but each destination has also a next hop proxy. I can do the forking using append_branch, but how can I set the destination URI for each branch? In some cases the R-URI does not change, only the next hop proxy. Example: R-URI Next Hop user1(a)domain.com XXX.XXX.XXX.XXX user1(a)domain.com YYY.YYY.YYY.YYY user2(a)domain.com XXX.XXX.XXX.XXX I was thinking I could use a htable to store the next hop using the R-URI as the key, but as can be seen above there are possibly duplicate R-URIs with only the next hop changing. Thanks. -- -Barry

4 18

0.0.0.0 in VIA header
by Lewis Hutchinson 10 Oct '23

10 Oct '23

Morning What have you got your listen / advertise address / port set as? See this link > https://www.kamailio.org/wiki/cookbooks/5.5.x/core#advertised_address I'd probably start by looking at that. Lewis Mission Labs Limited is registered in England, company number 10040088. Trading Office: The Old Milk Depot, Bacup Rd, Rossendale, BB4 7FE. Registered office: The Scalpel, 18th Floor 52 Lime Street, London, EC3M 7AF. Email confidentiality notice: This message is private and confidential. If you have received this message in error, please notify us and remove it from your system. Please consider the environment before you print this email.

1 0

0.0.0.0 in VIA header
by Ali Taher 10 Oct '23

10 Oct '23

Hello, I'm using Kamailio as SIP proxy to receive INVITE packets, randomize A-number and then relay it to a certain gateway. I noticed that a Via header is added to the INVITE sent by Kamailio to the gateway with 0.0.0.0 as address as shown below: Via: SIP/2.0/UDP 0.0.0.0;branch=z9hG4bK2d97.61de75dd58fa7ca7450cc8b9b01db62f.0 As far as I know, the IP that should be used in the new added VIA header must be Kamailio IP, but it's not the case here, knowing that Kamailio is not behind NAT. Regards, Ali Taher

2 1

CANCEL first, then INVITE.
by James Lipski 09 Oct '23

09 Oct '23

Hello, Is there a way to change the transaction order when a failure fork occurs -- to explain, endpoint 1 calls endpoint 2. Call towards endpoint 2 goes unanswered, and so the call forks to voicemail, I see that an INVITE is sent towards my voicemail server first, followed by a CANCEL towards the endpoint; can I send the CANCEL first to the endpoint and then INVITE towards my voicemail server. I'm essentially using the bundled/sample configurations for testing. Thank you.

4 10

kamailio Behind nat. How Record-Route should be added ？
by codenot＠msn.com 09 Oct '23

09 Oct '23

UA1(192.168.0.1) --> kamailio (internal:192.168.0.2 public:1.1.1.1) --> UA2(2.2.2.2) if in UA1 INVITE, I write KSR.rr.record_route(). so UA2(2.2.2.2) received sip msg (Record-Route: <sip:1.1.1.1:7080>), so Kamailio can received BYE/ACK from UA2. but，Kamailio can't received BYE/ACK from UA1. if in UA1 INVITE, i write KSR.rr.record_route_advertised_address("192.168.0.2"), then Kamailio can received BYE/ACK from UA1, but not from UA2. what can i do, let Kamailio receive BYE/ACK from both sides ？

6 10

[Dialog Module] questions about early_timeout param
by Abdoul Osséni 08 Oct '23

08 Oct '23

Hello all, Can you please clarify part of the following doc for me? -- 6.7. early_timeout (integer) The timeout (in seconds) after which the dialogs in unconfirmed or early state (no final response received) are destroyed. * Default value is “300 (5 minutes)”. * *Example 1.7. Set early_timeout parameter* ... modparam("dialog", "early_timeout", 180) --- In the case where Kamailio acts as an SBC, will kamailio send a SIP BYE message to both devices (UAC and UAC)? Or Can Kamailio send a BYE message to both parties when timer b has expired? If yes, how to do it? Regards Abdoul

1 0

kamailio Behind nat. How Record-Route should be added ？
by 城门虾米 08 Oct '23

08 Oct '23

UA(192.168.0.11) received 183, find Record-Route(36.140.122.12) then send ACK to 36.140.122.12(Kamialio public ip) not 192.168.0.2(kamailio internal ip), so Kamailio can't receive ACK. this is my config，192.168.0.11 -> Kamailio -> Other SBC(public ip) function ksr_request_route() if KSR.is_INVITE() then KSR.rr.record_route(); KSR.nathelper.fix_nated_contact() end end This question has been bothering me for a long time, help me [cid:d1ec74be-1c33-406e-80d5-68663d1cd21f] [cid:bda00d0d-e6e6-4dc9-9462-141ad42b09b8]

1 1

uac_req_send + evroute + crash
by Dr. Barabás Péter 06 Oct '23

06 Oct '23

Hi All, I use kamailio In front of Asterisk and kamailio needs to refresh registrations periodically towards Asterisk to ensure the availability of users from Asterisk side. I use uac module and call uac_req_send() for sending REGISTER requests. I set $uac_req(evroute)=1 The event_route[uac:reply] is called fine, but in kamailio logs I see the next lines: CRITICAL: <core> [core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer (0x7f114995ada8), called from uac: uac_send.c: uac_send_tm_callback(860), first free uac: uac_send.c: uac_resend_tm_callback(732) - ignoring After some time, kamailio has crashed. CRITICAL: <core> [core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer (0x7f114995ada8), called from uac: uac_send.c: uac_send_tm_callback(860), first free uac: uac_send.c: uac_resend_tm_callback(732) – ignoring CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 34 ALERT: <core> [main.c:774]: handle_sigs(): child process 1407950 exited by a signal 6 Any idea that is it a bug or I use something wrong in config? Thanks in advance! Péter Barabás

2 4

Crypto module AES algorithm details
by Jayesh Nambiar 04 Oct '23

04 Oct '23

*Hello,* I am running kamailio-5.3.4 on one of my setup and I intend to use the crypto module in the same. I wanted to understand the following details when the module is used: I understand it uses the AES algorithm, is that correct? Does it use AES 128, 192 or 256 bit algorithms? Does it use CBC or ECB mode for AES? The 5.3 version does not have an parameter for init-vector, so does kamailio use any init vector internally in this case? When i compared the encrypted text that kamailio produces and the ones available online, they were producing different outputs even when same shared secret was used. Hence asking for more clarification PS: Upgrading kamailio is my very last option as this is one af an old setup which only needs this feature without much changes. Thanks for any valuable response. *-- Jayesh*

2 1

error in parsing HTTP messages
by sigxcpu＠gmail.com 02 Oct '23

02 Oct '23

Hello, In reference to this issue https://github.com/kamailio/kamailio/issues/3081 I've been advised to set http_reply_parse to "no" which I did (and it is the default value anyways). # grep http_reply_parse /etc/kamailio/kamailio.cfg http_reply_parse=no After setting this, I still get these parsing errors: { "idx": 23, "pid": 102, "level": "ERROR", "module": "core", "file": "core/parser/msg_parser.c", "line": 748, "function": "parse_msg", "logprefix": "", "message": "ERROR: parse_msg: message=<HTTP/1.1 100 Continue\r\n\r\nHTTP/1.1 200 OK\r\ndate: Wed, 26 Jul 2023 16:43:19 GMT\r\ncontent-length: 224\r\ncontent-type: text/plain; charset=utf-8\r\n\r\n{\"result\": {\"ruri\":\"\",\"fU\":\"\",\"tU\":\"\",\"privacy\":\"\",\"identity\":\"\",\"error\":{\"code\":0,\"message\":\"\"},\"mb\":\"\",\"Headers\":null,\"encrypted\":\"\",\"sipsScheme\":\"\",\"attestation\":\"\",\"authUser\":\"\",\"authPassword\":\"\",\"disableStirShaken\":\"\"}}>" } Is there anything that I am missing beyond setting that parameter? Thank you, Alexandru

1 1

Software bill of materials (SBOM)
by Ivan Ribakov 30 Sep '23

30 Sep '23

Any recommendations for a tool that can generate SBOM for a Kamailio instance based on configured modules? Thanks, Ivan

6 10

periodic could not resolve hostname
by Sergiu Pojoga 28 Sep '23

28 Sep '23

Aloha, I'm experiencing this internal DNS problem with Kamailio, can't seem to figure out what's causing it. Maybe someone can help. Essentially, from time to time (one or two times a day) this situation happens, starting with logs: linux kamailio[773]: ERROR: uac [uac_reg.c:1163]: uac_reg_send(): failed to send request for [some-uuid] linux kamailio[773]: ERROR: <core> [core/resolve.c:1730]: sip_hostport2su(): could not resolve hostname: "my.domain.net" linux kamailio[773]: ERROR: tm [ut.h:309]: uri2dst2(): failed to resolve " my.domain.net" linux kamailio[773]: ERROR: tm [uac.c:480]: t_uac_prepare(): no socket found # Do a Kamailio internal DNS lookup, no results found??? root@linux:~# kamcmd dns.lookup a my.domain.net error: 400 - Not found # Do a system DNS lookup. All good. root@linux:~# dig my.domain.net ;; QUESTION SECTION: ;my.domain.net. IN A ;; ANSWER SECTION: my.domain.net. 18000 IN A 192.168.0.1 # Delete internal Kamailio DNS record root@linux:~# kamcmd dns.delete_a my.domain.net # Lookup again right away. It's there, problem fixed. Why?? root@linux:~# kamcmd dns.lookup a my.domain.net { name: my.domain.net type: A size_bytes: 120 reference_counter: 2 permanent: no expires: 7674 last_used: 0 negative_entry: no records: { { rr_idx: 0 rr_ip: 192.168.0.1 rr_permanent: no rr_expires: 7674 } } }

2 2

What is the expected behavior for dispatcher's ds_next_dst?
by geoff.goas＠interoptechnologies.com 28 Sep '23

28 Sep '23

Hello, I have some questions about dispatcher's behavior. I noticed that when I first ds_select_dst() a specific dispatcher group ID, ds_next_dst() will cycle through the active destinations in that group. When it reaches the end of the destinations in the group, it does not return "false", instead it starts to return destinations that are not a part of that group, ie. those destinations which are listed prior to the selected group in the dispatcher.list file. Is this the expected behavior? I've observed it on kamailio 5.3 and 5.5 releases. My dispatcher.list: # Group 1 1 sip:127.0.0.1:5071;transport=udp 8 0 # Group 2 2 sip:127.0.0.1:5072;transport=udp 8 0 # Group 3 3 sip:127.0.0.1:7010;transport=udp 8 0 3 sip:127.0.0.1:7011;transport=udp 8 0 3 sip:127.0.0.1:7012;transport=udp 8 0 # Group 4 4 sip:127.0.0.1:5071;transport=udp 8 0 4 sip:127.0.0.1:5072;transport=udp 8 0 I have the following in failure_route (excerpt): $var(dsFoundDestination) = 0; if (t_any_replied()) { xavp_params_implode("_dsdst_", "$var(dsDestinations)"); xlog("L_INFO", "FAILURE ROUTE: Already have replies on this transaction. Selecting next destination from: [$var(dsDestinations)]"); if (ds_next_dst()) { xavp_params_implode("_dsdst_", "$var(dsDestinations)"); xlog("L_INFO", "FAILURE ROUTE: Next destination selected: [$du] from [$var(dsDestinations)]"); $var(dsFoundDestination) = 1; } } else if (ds_select_dst("3", "8")) // Dispatcher Group 3 { xlog("L_INFO", "FAILURE ROUTE: Did not find any replies on this transaction. Selected destination: [$du]"); $var(dsFoundDestination) = 1; } if ($var(dsFoundDestination)) { $var(logString) = "FAILURE ROUTE: Relayed to [" + $du + "]"; if (t_relay()) { xlog("L_INFO", "$var(logString)"); } } Produces the following logs: FAILURE ROUTE: Did not find any replies on this transaction. Selected destination: [sip:127.0.0.1:7012;transport=udp] FAILURE ROUTE: Relayed to [sip:127.0.0.1:7012;transport=udp] FAILURE ROUTE: Already have replies on this transaction. Selecting next destination from: [grp=3;uri=sip:127.0.0.1:7012;transport=udp;] FAILURE ROUTE: Next destination selected: [sip:127.0.0.1:7011;transport=udp] from [grp=3;uri=sip:127.0.0.1:7011;transport=udp;] FAILURE ROUTE: Relayed to [sip:127.0.0.1:7011;transport=udp] FAILURE ROUTE: Already have replies on this transaction. Selecting next destination from: [grp=3;uri=sip:127.0.0.1:7011;transport=udp;] FAILURE ROUTE: Next destination selected: [sip:127.0.0.1:7010;transport=udp] from [grp=3;uri=sip:127.0.0.1:7010;transport=udp;] FAILURE ROUTE: Relayed to [sip:127.0.0.1:7010;transport=udp] FAILURE ROUTE: Already have replies on this transaction. Selecting next destination from: [grp=3;uri=sip:127.0.0.1:7010;transport=udp;] FAILURE ROUTE: Next destination selected: [sip:127.0.0.1:5072;transport=udp] from [grp=2;uri=sip:127.0.0.1:5072;transport=udp;] FAILURE ROUTE: Relayed to [sip:127.0.0.1:5072;transport=udp] FAILURE ROUTE: Already have replies on this transaction. Selecting next destination from: [grp=2;uri=sip:127.0.0.1:5072;transport=udp;] FAILURE ROUTE: Next destination selected: [sip:127.0.0.1:5072;transport=udp] from [grp=2;uri=sip:127.0.0.1:5072;transport=udp;] FAILURE ROUTE: Relayed to [sip:127.0.0.1:5072;transport=udp] FAILURE ROUTE: Already have replies on this transaction. Selecting next destination from: [grp=2;uri=sip:127.0.0.1:5072;transport=udp;] FAILURE ROUTE: Next destination selected: [sip:127.0.0.1:5071;transport=udp] from [grp=1;uri=sip:127.0.0.1:5071;transport=udp;] FAILURE ROUTE: Relayed to [sip:127.0.0.1:5071;transport=udp] I want to stop the loop once there are no more active destinations in group 3. Is the solution simply to check that the selected destination is part of the desired group and stop processing if it is not? Thanks for your time.

5 8

Kamailio v5.7.2 Released
by Daniel-Constantin Mierla 27 Sep '23

27 Sep '23

Hello, Kamailio SIP Server v5.7.2 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.1. 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.2. For more details about version 5.7.2 (including links and guidelines to download the tarball or from GIT repository), visit: * https://www.kamailio.org/w/2023/09/kamailio-v5-7-2-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

Releasing v5.7.2
by Daniel-Constantin Mierla 27 Sep '23

27 Sep '23

Hello, I am considering to release Kamailio v5.7.2 (out of branch 5.7) this week (likely on Wednesday or Thursday, Sep 27/28, 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

failure_route, change_reply_status, and append_hf: Not Working as Expected
by sadik.oualla.mohamed＠gmail.com 26 Sep '23

26 Sep '23

Hello Kamailio Community, I'm currently working on a project that involves complex SIP routing and handling. I've encountered some difficulties while using change_reply_status, and append_hf functions in failure_route route in Kamailio. Although the documentation does provide guidance, the behaviors I am experiencing aren't aligning with the expected outcomes. Issue 1: failure_route I've set up a failure_route to handle specific SIP response codes (>4xx). However, I've observed that it get trigered and lunched, but I can't use change_reply_status or append_hf, I was using this first in onreply_route. Issue 2: change_reply_status I tried to use the change_reply_status function to modify the status of SIP replies, but it raises an error that this command cannot be executed here. Issue 3: append_hf I've also attempted to use append_hf in my failure_route block to add headers to replies, but the headers are not being added as expected. As a workaround, I've been using send_reply and append_to_reply for adding custom headers, and they seem to be working as expected. However, I found some old messages in kamailio mailing list, I can summerize what I learned like this ``` #Functions and Context - append_hf(): Adds a header to the currently processed SIP message. If you are in a route {...} block, then this adds the header to the request. If you are in an onreply_route, it adds the header to the reply. This function always acts on the message currently under scrutiny. - append_to_reply(): This function is used to add a header to a reply that will be generated by Kamailio at a later time. This function only affects replies generated by Kamailio itself and is not applicable for messages that are simply being forwarded. #Contexts - route {...}: This is typically where the incoming SIP request gets processed. Here, append_hf() will add headers to that request, and append_to_reply() will add headers to any replies that Kamailio might generate for this request. - onreply_route: This is where incoming SIP replies are processed. Here, append_hf() will act on the reply, not the request. ``` I'd like to know if there is a way to handle sip replies in failure_route, because send_reply make a new reply from kamailio, instead I want to keep some important headers from the original reply. I'd appreciate any insights or guidance the community can offer. Best regards,

2 1

RTPengine use single port for all calls
by Mahmood Alkhalil 26 Sep '23

26 Sep '23

Hello Kamailio, Is it possible to use RTPengine with a single UDP port for all calls instead of a range of ports? For example, when an invite is received or sent, the offered SDP for RTPengine is to receive RTP packets on a single port that is the same for all other calls, so that on firewalls only one port is to be opened.

2 2

Re: Choose RTP port in routing script
by Duarte Rocha 26 Sep '23

26 Sep '23

2 1

cdr_json_pre_encoded_prefix
by Oleg Podguyko 26 Sep '23

26 Sep '23

I try to use cdr_json_pre_encoded_prefix (string) parameters from acc_json module modparam("acc_json", "cdr_extra", "spx_resp=$avp(spx_resp)") modparam("acc_json", "cdr_json_pre_encoded_prefix", "spx_resp") do restart and get next mistakes: sep 22 14:17:15 vms-vms-spx-1 kamailio[581922]: ERROR: <core> [core/modparam.c:169]: set_mod_param_regex(): parameter <cdr_json_pre_encoded_prefix> of type <1:string> not found in module <acc_json> сен 22 14:17:15 vms-vms-spx-1 kamailio[581922]: CRITICAL: <core> [core/cfg.y:3686]: yyerror_at(): parse error in config file /etc/kamailio_vmsspx/modules.cfg, line 125, column 63: Can't set module parameter sep 22 14:17:15 vms-vms-spx-1 kamailio[581922]: ERROR: bad config file (1 errors) (parsing code: 0) sep 22 14:17:15 vms-vms-spx-1 systemd[1]: kamailio_vmsspx.service: Control process exited, code=exited status=255 sep 22 14:17:15 vms-vms-spx-1 systemd[1]: kamailio_vmsspx.service: Failed with result 'exit-code'. What’s wrong? I used: [opodguyko@vms-vms-spx-1 ~]$ kamailio -version version: kamailio 5.5.3 (x86_64/linux) b02728-dirty 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: b02728 -dirty compiled on 15:35:46 Dec 15 2021 with gcc 8.3.1 [opodguyko@vms-vms-spx-1 ~]$ This parameter was added at release 5.5.0 Oleg Podguyko

3 3

Choose RTP port in routing script
by Duarte Rocha 26 Sep '23

26 Sep '23

Hello all, I have my rtpengine configured to use ports 20000 - 50000 for RTP in rtpengine.conf. Now i want to able to select the port or the port range in a call by call basis. Is that possible? I've tried to use "media-address" flag on rtpengine_manage but i wasn't successful. Thanks in advance, Cheers, Duarte Rocha

2 1

Several crashs in prepare_new_uac
by Igor Potjevlesch 26 Sep '23

26 Sep '23

Hello! We had several crashs of Kamailio (5.3.4) in the last weeks. Each time, the last logs are: /usr/local/sbin/kamailio[20942]: CRITICAL: <core> [core/forward.c:347]: get_send_socket2(): unsupported proto 0 (*) /usr/local/sbin/kamailio[20966]: CRITICAL: <core> [core/forward.c:347]: get_send_socket2(): unsupported proto 111 (unknown) When we look to the coredump, here below the first traces: (gdb) bt #0 0x00007f70131b3d91 in prepare_new_uac (t=0x7f6fe1d45340, i_req=0x7f7016fbe208, branch=0, uri=0x7fff37142fa0, path=0x7fff37142f80, next_hop=0x7f7016fbe480, fsocket=0x0, snd_flags=..., fproto=0, flags=2, instance=0x7fff37142f70, ruid=0x7fff37142f60, location_ua=0x7fff37142f50) at t_fwd.c:463 #1 0x00007f70131b7c42 in add_uac (t=0x7f6fe1d45340, request=0x7f7016fbe208, uri=0x7f7016fbe480, next_hop=0x7f7016fbe480, path=0x7f7016fbe848, proxy=0x0, fsocket=0x0, snd_flags=..., proto=0, flags=2, instance=0x7f7016fbe858, ruid=0x7f7016fbe870, location_ua=0x7f7016fbe880) at t_fwd.c:805 #2 0x00007f70131bfebd in t_forward_nonack (t=0x7f6fe1d45340, p_msg=0x7f7016fbe208, proxy=0x0, proto=0) at t_fwd.c:1667 #3 0x00007f701316cf44 in t_relay_to (p_msg=0x7f7016fbe208, proxy=0x0, proto=0, replicate=0) at t_funcs.c:332 #4 0x00007f70131a3a11 in _w_t_relay_to (p_msg=0x7f7016fbe208, proxy=0x0, force_proto=0) at tm.c:1689 #5 0x00007f70131a4c51 in w_t_relay (p_msg=0x7f7016fbe208, _foo=0x0, _bar=0x0) at tm.c:1889 #6 0x00000000005a1f57 in do_action (h=0x7fff37143d90, a=0x7f7016bd1b10, msg=0x7f7016fbe208) at core/action.c:1071 #7 0x00000000005aeb1e in run_actions (h=0x7fff37143d90, a=0x7f7016bd1b10, msg=0x7f7016fbe208) at core/action.c:1576 #8 0x00000000005af1df in run_actions_safe (h=0x7fff37146e90, a=0x7f7016bd1b10, msg=0x7f7016fbe208) at core/action.c:1640 #9 0x000000000066aa50 in rval_get_int (h=0x7fff37146e90, msg=0x7f7016fbe208, i=0x7fff37144238, rv=0x7f7016bd1e60, cache=0x0) at core/rvalue.c:915 #10 0x000000000066f000 in rval_expr_eval_int (h=0x7fff37146e90, msg=0x7f7016fbe208, res=0x7fff37144238, rve=0x7f7016bd1e58) at core/rvalue.c:1913 #11 0x000000000066f453 in rval_expr_eval_int (h=0x7fff37146e90, msg=0x7f7016fbe208, res=0x7fff371446ec, rve=0x7f7016bd2588) at core/rvalue.c:1921 #12 0x00000000005a1a1d in do_action (h=0x7fff37146e90, a=0x7f7016bd2e08, msg=0x7f7016fbe208) at core/action.c:1047 #13 0x00000000005aeb1e in run_actions (h=0x7fff37146e90, a=0x7f7016bcbd20, msg=0x7f7016fbe208) at core/action.c:1576 #14 0x000000000059e97d in do_action (h=0x7fff37146e90, a=0x7f7016ef19b8, msg=0x7f7016fbe208) at core/action.c:695 #15 0x00000000005aeb1e in run_actions (h=0x7fff37146e90, a=0x7f7016e3f578, msg=0x7f7016fbe208) at core/action.c:1576 #16 0x000000000059e97d in do_action (h=0x7fff37146e90, a=0x7f7016c220a0, msg=0x7f7016fbe208) at core/action.c:695 #17 0x00000000005aeb1e in run_actions (h=0x7fff37146e90, a=0x7f7016c220a0, msg=0x7f7016fbe208) at core/action.c:1576 #18 0x00000000005aae93 in do_action (h=0x7fff37146e90, a=0x7f7016c23978, msg=0x7f7016fbe208) at core/action.c:1207 #19 0x00000000005aeb1e in run_actions (h=0x7fff37146e90, a=0x7f7016c20748, msg=0x7f7016fbe208) at core/action.c:1576 #20 0x00000000005a1ec6 in do_action (h=0x7fff37146e90, a=0x7f7016c576a0, msg=0x7f7016fbe208) at core/action.c:1062 #21 0x00000000005aeb1e in run_actions (h=0x7fff37146e90, a=0x7f7016c0b770, msg=0x7f7016fbe208) at core/action.c:1576 #22 0x000000000059e97d in do_action (h=0x7fff37146e90, a=0x7f7016bc9920, msg=0x7f7016fbe208) at core/action.c:695 #23 0x00000000005aeb1e in run_actions (h=0x7fff37146e90, a=0x7f7016bb9100, msg=0x7f7016fbe208) at core/action.c:1576 #24 0x00000000005af2a7 in run_top_route (a=0x7f7016bb9100, msg=0x7f7016fbe208, c=0x0) at core/action.c:1661 #25 0x00000000005bcb7a in receive_msg ( buf=0xadbd80 <buf.6971> "INVITE sip:AAAAAAAAAA@W.X.Y.Z SIP/2.0\r\nVia: SIP/2.0/UDP W.X.Y.Z;rport;branch=z9hG4bKZD8Za7p2XF7cF\r\nMax-Forwards: 69\r\nFrom: \"AAAAAAAAAA\" sip:AAAAAAAAAA@W.X.Y.Z;tag=aXy4Na2NtvKBK\r\nTo: <"..., len=1011, rcv_info=0x7fff371474c0) at core/receive.c:423 #26 0x0000000000488e7f in udp_rcv_loop () at core/udp_server.c:548 #27 0x000000000042650f in main_loop () at main.c:1673 #28 0x000000000042ec18 in main (argc=7, argv=0x7fff37147c38) at main.c:2802 Is there anything relevant in this to know what's wrong? Regards, Igor. -- Cet e-mail a été vérifié par le logiciel antivirus d'Avast. www.avast.com

3 4

Planning Kamailio Developers Meeting 2023
by Daniel-Constantin Mierla 26 Sep '23

26 Sep '23

Hello, we are considering to organize another edition of Kamailio Developers Meeting, to be hosted again by sipgate.de in Dusseldorf, Germany. There is no fee for participants (i.e., free entry), but each one has to take care of travelling and accommodation (drinks and food are provided during the day). A few developers are already on board, we are looking to see if anyone else from the broader community wants to join us. Likely it is going to be during 2 days (with the option of doing it during three days still open at this moment, if there is going to be enough interest to have it longer). The proposed time frames are: - Nov 7-9, 2023 - Nov 21-23, 2023 The event is about discussing the internals of Kamailio (e.g., architectural changes, development strategies) and writing code or documentation for it. This is not an event about learning how to use Kamailio, but to work on improving it. As a bonus, there will be a social networking event in the evening with some fun activities, drinks and food. If you want to join, state your preference for any of the two time frames (or even just for 2 days in one of the two time frames). It is not a large meeting room, if we get too many join requests, we may have to select based on past contributions, and if that is not the case, then is just the first come first served. You can reply to this thread or just write me directly if you want to join and when you prefer to happen. By mid of next week, we plan to select the event dates so everyone that comes to it can start planning the trip. Cheers, Daniel -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy - Training Services -- asipto.com Kamailio World Conference - kamailioworld.com

1 1

Iterating Through Multiple IP Peers for DID Call Termination in Kamailio
by Shah Hussain Khattak 26 Sep '23

26 Sep '23

Hello Team, I hope you're all doing well. I'm reaching out to request your insights on the following scenario. Overview: I have successfully configured Kamailio to authenticate IP addresses, primarily for PBXs and customers unable to register. With this setup, I can flawlessly receive incoming traffic and forward it to our internal FreeSwitch servers. Current issue: Now, I'm focusing on managing traffic in the opposite direction—specifically for DIDs. I have a DID table set up in Kamailio that associates DID numbers with their respective IP peers. Upon receiving a call, a database lookup is performed to find the destination number, after which the call is terminated at the customer's IP. I'm facing difficulty in handling situations where a customer has multiple IP peers (for redundancy). My aim is to try each of these IPs sequentially when terminating a specific DID call towards them. The current logic I'm employing for the INVITE lookup looks like this: # Database lookup for INVITEs if (is_method("INVITE")) { sql_query("didrouting_db", "SELECT route_to FROM did_routing WHERE did_number='$rU'", "result"); if ($dbr(result=>rows) > 0) { $var(route_to) = $dbr(result=>[0,0]); xlog("L_INFO", "Routing DID $rU to $var(route_to)\n"); $du = "sip:" + $var(route_to) + ":5060"; } else { $du = "sip:" + FS_IP + ":5060"; } } The above logic works fine for a single IP. I intend to use a comma-separated list of IPs in my route_to column (for example 192.168.1.2,192.168.1.3, ...) and then iterate through these IPs one by one. I'm having trouble coming up with a workable logic or loop to achieve this. Would you be able to offer any guidance or suggestions? Please also recommend if there is a better approach available to handle this scenario. Thank you in advance for your valuable input. Regards, Shah Hussain

4 3

TM max_inv_lifetime being reset by downstream responses
by James Browne 25 Sep '23

25 Sep '23

Hi all I see this old thread from 2015. - https://kamailio.org/mailman3/hyperkitty/list/sr-users@lists.kamailio.org/t… It's about max_inv_lifetime not working properly. I have this problem today: SIP-180 responses from downstream apparently reset max_inv_lifetime, and the transaction can live for hours (apparently indefinitely) even though max_inv_lifetime is set to just over a minute. By spacing the SIP-180 responses (from downstream) slightly longer apart than than max_inv_lifetime in kamailio, I don't get the problem, so it looks to me that this is TM not matching what's in the documentation (which mentions that this should be a hard limit). With this configuration, SIP-180 responses every minute result in the transaction never ending (until the client CANCELs the call). - kamailio.cfg:modparam("tm", "fr_timer", 3000) - kamailio.cfg:modparam("tm", "fr_inv_timer", 300000) - kamailio.cfg:modparam("tm", "max_inv_lifetime", 65000) - kamailio.cfg:modparam("tm", "noisy_ctimer", 1) That other thread ends with Daniel mentioning that he'd have to look at the code, but nothing further. Running "git log --grep max_inv_lifetime" shows me that the last/only update that wasn't just documentation was in 2007. Has anyone got an ideas? James

2 2

Modifying SDP as drop-in replacement for overloaded Asterisk box - looking for help/paid consulting fast
by Markus 23 Sep '23

23 Sep '23

Hi list, I'm trying to use Kamailio 4.4.4 with rtpengine in a self-inflicted emergency situation (didn't monitor traffic growth properly and now encountering packet loss during peak times) as a drop-in replacement for an overloaded Asterisk box in a call-termination-to-upstream-carrier scenario. My test scenario is to make a call from a SIP softphone to Asterisk IP 1.1.1.1 -> Kamailio/rtpengine IP 2.2.2.2 -> Upstream carrier 3.3.3.3 sngrep on Kamailio box 2.2.2.2 - the following SDP will not work - carrier is rejecting it. Carrier is authenticating our calls based on our IP address 2.2.2.2, no username/pass involved. 2023/09/22 02:06:49.216136 2.2.2.2:5060 -> 3.3.3.3:5060 INVITE sip:+32xxxxxxxx@2.2.2.2;user=phone SIP/2.0 Record-Route: <sip:2.2.2.2;lr> Via: SIP/2.0/UDP 2.2.2.2;branch=z9hG4bKd9c3.d6fa3abe5d52b827e2054de5573028e0.0 Via: SIP/2.0/UDP 1.1.1.1:5060;branch=z9hG4bK473270e8 Max-Forwards: 69 From: "61xxxxxxxxx" <sip:+61xxxxxxxxx@1.1.1.1>;tag=as3d75aadd To: <sip:+32xxxxxxxx@2.2.2.2;user=phone> Contact: <sip:+61xxxxxxxxx@1.1.1.1:5060> Call-ID: 3f31e1622a72b6d17f24e42362f4f1d0@1.1.1.1:5060 CSeq: 102 INVITE User-Agent: Asterisk PBX 20.0.0 Date: Fri, 22 Sep 2023 00:06:50 GMT Session-Expires: 1800 Min-SE: 90 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE Supported: replaces, timer P-Asserted-Identity: <sip:+61xxxxxxxxx@2.2.2.2;user=phone> Content-Type: application/sdp Content-Length: 314 X-SIP: 1.1.1.1 v=0 o=root 1093000903 1093000903 IN IP4 1.1.1.1 s=Asterisk PBX 20.0.0 c=IN IP4 2.2.2.2 t=0 0 m=audio 25742 RTP/AVP 8 9 0 101 a=maxptime:150 a=rtpmap:8 PCMA/8000 a=rtpmap:9 G722/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=sendrecv a=rtcp:25743 a=ptime:20 I'm comparing this rejected INVITE to a successful INVITE sent by the original Asterisk box at IP 2.2.2.2 (now Kamailio box) to the carrier without Kamailio in the path, and these are the differences I noticed, and probably the things I have to mimick with Kamailio in order to make it work: INVITE sip:+32xxxxxxxxx@2.2.2.2;user=phone SIP/2.0 should be INVITE sip:+32xxxxxxxxx@3.3.3.3;user=phone SIP/2.0 To: <sip:+32xxxxxxxx@2.2.2.2;user=phone> should be To: <sip:+32xxxxxxxx@3.3.3.3;user=phone> From: "61xxxxxxxxx" <sip:+61xxxxxxxxx@1.1.1.1>;tag=as3d75aadd should be From: "61xxxxxxxxx" <sip:+61xxxxxxxxx@2.2.2.2>;tag=as3d75aadd Contact: <sip:+61xxxxxxxxx@1.1.1.1:5060> should be Contact: <sip:+61xxxxxxxxx@2.2.2.2:5060> Call-ID: 3f31e1622a72b6d17f24e42362f4f1d0@1.1.1.1:5060 should be Call-ID: 3f31e1622a72b6d17f24e42362f4f1d0@2.2.2.2:5060 o=root 1093000903 1093000903 IN IP4 1.1.1.1 should be o=root 1093000903 1093000903 IN IP4 2.2.2.2 My kamailio.cfg can be found here: https://pastebin.com/6PKcRjPU These are the Asterisk boxes I want to originate calls from to Kamailio: [root@voip30 ~]# kamctl address show +-----+-----+----------+------+------+-----------+ | id | grp | ip_addr | mask | port | tag | +-----+-----+----------+------+------+-----------+ | 195 | 1 | 1.1.1.1 | 32 | 0 | voip20.sv | | 196 | 1 | 1.1.1.2 | 32 | 0 | voip21.sv | | 197 | 1 | 1.1.1.3 | 32 | 0 | voip22.sv | | 198 | 1 | 1.1.1.4 | 32 | 0 | voip23.sv | | 199 | 1 | 1.1.1.5 | 32 | 0 | voip24.sv | | 200 | 1 | 1.1.1.6 | 32 | 0 | voip25.sv | | 201 | 1 | 1.1.1.7 | 32 | 0 | voip26.sv | | 202 | 1 | 1.1.1.8 | 32 | 0 | voip27.sv | | 203 | 1 | 1.1.1.9 | 32 | 0 | voip28.sv | +-----+-----+----------+------+------+-----------+ This is the upstream carrier I want Kamailio to proxy calls to: [root@voip30 ~]# kamctl dispatcher show dispatcher gateways +----+-------+------------------+-------+-------+------------+------+ | id | setid | destination | flags | prio. | attrs | desc | +----+-------+------------------+-------+-------+------------+------+ | 12 | 1 | sip:3.3.3.3:5060 | 0 | 0 | weight=100 | | +----+-------+------------------+-------+-------+------------+------+ (output manually slightly modified to look properly over E-Mail) As you might have guessed I'm a Kamailio noob... and don't have the resources to learn it as fast as I must to avoid further packet loss. If there's anyone available who can help me to get this done today, optionally in exchange for money, I'd be grateful. Thank you! Markus

5 11

Multi-dimensional data in htable
by Ben Kaufman 22 Sep '23

22 Sep '23

What's the best way to store multi-dimensional data within an htable? For example, storing an avp stack: $avp(foo) = "first"; $avp(foo) = "second"; $sht(bar=>foo) = $avp(foo); The result of which is that only $avp(foo[0]) is stored in the htable: kamcmd htable.dump bar { entry: 2 size: 1 slot: { { name: bar value: second type: str } } } The htable documentation shows support for lists, but it doesn't make clear if this is really usable outside of loading from a database, and looks like it's short hand for managing/creating linked lists. The other option would be to simply serialize the data before storing it in the htable - which is fine, I just want to be sure I'm not overlooking a more convenient method. Regards, Kaufman

4 5

no corresponding socket found error
by David Escartín 22 Sep '23

22 Sep '23

Hello all we are seeing these kind of logs in a Debian GNU/Linux 11 using kamailio 5.5.6 Sep 21 17:41:13 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155702]: ERROR: <core> [core/forward.c:183]: get_out_socket(): no corresponding socket found for(udp:164.152.22.248:5060) Sep 21 17:41:13 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155698]: ERROR: <core> [core/forward.c:183]: get_out_socket(): no corresponding socket found for(udp:208.74.138.184:5060) Sep 21 17:41:13 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155695]: ERROR: <core> [core/forward.c:183]: get_out_socket(): no corresponding socket found for(udp:208.74.138.181:5060) Sep 21 17:41:14 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155693]: ERROR: <core> [core/forward.c:183]: get_out_socket(): no corresponding socket found for(udp:38.102.250.60:5060) Sep 21 17:41:14 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155707]: ERROR: <core> [core/forward.c:183]: get_out_socket(): no corresponding socket found for(udp:87.1.1.27:5060) Sep 21 17:41:14 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155707]: ERROR: tm [ut.h:302]: uri2dst2(): no corresponding socket for "87.1.1.27" af 2 Sep 21 17:41:14 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155707]: ERROR: tm [t_fwd.c:470]: prepare_new_uac(): can't fwd to af 2, proto 1 (no corresponding listening socket) Sep 21 17:41:14 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155697]: ERROR: <core> [core/forward.c:183]: get_out_socket(): no corresponding socket found for(udp:208.74.138.184:5060) Sep 21 17:41:14 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155694]: ERROR: <core> [core/forward.c:183]: get_out_socket(): no corresponding socket found for(udp:192.40.216.97:5060) Sep 21 17:41:14 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155694]: ERROR: <core> [core/forward.c:183]: get_out_socket(): no corresponding socket found for(udp:208.74.138.180:5060) Sep 21 17:41:14 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155714]: ERROR: <core> [core/forward.c:183]: get_out_socket(): no corresponding socket found for(udp:87.1.1.27:5060) The kamailio instance we are using is receiving around 1500 calls per second in average when we do start seeing these errors more frequently In this instance we are using multihomed the listen address list is children=14 socket_workers=1 listen=udp:192.168.99.70:5081 listen=udp:192.168.99.81:5060 listen=udp:87.1.1.27:5060 listen=tcp:192.168.96.105:8095 listen=tcp:87.1.1.27:5060 tcp_children=6 port=5060 We use the first worker only to perform the OPTIONS requests from the dispatcher module. The sockets listen=udp:192.168.99.81:5060 listen=udp:87.1.1.27:5060 are used to communicate both A and B legs so when a message is received at 192.168.99.81:5060 we send it to 87.1.1.27:5060 and viceversa We were using $fs variable before doing the t_relay() function. This way is working, but when load increases, seems sometimes kamailio doesn't get the proper socket to forward the reply. I think the errors mainly are related to responses which are being forwarded, like if the function get_sock_info_list was not able to retrieve the listen interfaces we have tried to set in the onreply routes the commands set_recv_socket("udp:192.168.99.81:5060"); set_send_socket("udp:87.1.1.27:5060"); (when reply goes from private to public domain) and it seems it reduces the number of Sep 21 17:41:13 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155702]: ERROR: <core> [core/forward.c:183]: get_out_socket(): no corresponding socket found for(udp:164.152.22.248:5060) Sep 21 17:41:13 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155698]: ERROR: <core> [core/forward.c:183]: get_out_socket(): no corresponding socket found for(udp:208.74.138.184:5060) Sep 21 17:41:13 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155695]: ERROR: <core> [core/forward.c:183]: get_out_socket(): no corresponding socket found for(udp:208.74.138.181:5060) Sep 21 17:41:14 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155693]: ERROR: <core> [core/forward.c:183]: get_out_socket(): no corresponding socket found for(udp:38.102.250.60:5060) errors But i honestly don't know why the Sep 21 17:41:14 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155707]: ERROR: tm [ut.h:302]: uri2dst2(): no corresponding socket for "87.1.1.27" af 2 Sep 21 17:41:14 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155707]: ERROR: tm [t_fwd.c:470]: prepare_new_uac(): can't fwd to af 2, proto 1 (no corresponding listening socket) appear We aldso tried to increase the kernel buffers rmem and wmem from 208KB (as we had by default) to 4MB Do you know a reason which could cause these logs to appear? Any setup that could mitigate them? thanks a lot and regards david escartin -- <http://www.sonoc.io/> David Escartín NOC engineer www.sonoc.io [image: LinkedIn] <https://www.linkedin.com/company/sonoc> [image: Twitter] <https://twitter.com/sonoc_> [image: Instagram] <https://www.instagram.com/sonoc.io/> This e-mail is for the exclusive use of its recipients and may contain business secrets or other confidential or privileged information. Any unauthorised use, copying, publication or distribution of this e-mail is strictly prohibited. If you are not the intended recipient, please inform us immediately by replying to this e-mail and delete it, including any attachments or copies on your system. In accordance with the GDPR (EU) 2016/679 and the LOPDGDD 3/2018, we inform you that this e-mail address and/or any other personal data you have provided us with will be treated by SONOC with absolute confidentiality and with the only purpose of providing you with the requested services, due to your condition as a client, supplier or because you have requested information from us at any time. These data will only be kept for as long as required to comply with legal obligations. You can exercise your rights at any time by sending an e-mail to: dataprotection(a)sonoc.io. <dataprotection(a)sonoc.io>

1 0

"no corresponding socket found" logs
by David Escartín 22 Sep '23

22 Sep '23

Hello all we are seeing these kind of logs in a Debian GNU/Linux 11 using kamailio 5.5.6 Sep 21 17:41:13 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155702]: ERROR: <core> [core/forward.c:183]: get_out_socket(): no corresponding socket found for(udp:164.152.22.248:5060) Sep 21 17:41:13 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155698]: ERROR: <core> [core/forward.c:183]: get_out_socket(): no corresponding socket found for(udp:208.74.138.184:5060) Sep 21 17:41:13 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155695]: ERROR: <core> [core/forward.c:183]: get_out_socket(): no corresponding socket found for(udp:208.74.138.181:5060) Sep 21 17:41:14 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155693]: ERROR: <core> [core/forward.c:183]: get_out_socket(): no corresponding socket found for(udp:38.102.250.60:5060) Sep 21 17:41:14 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155707]: ERROR: <core> [core/forward.c:183]: get_out_socket(): no corresponding socket found for(udp:87.1.1.27:5060) Sep 21 17:41:14 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155707]: ERROR: tm [ut.h:302]: uri2dst2(): no corresponding socket for "87.1.1.27" af 2 Sep 21 17:41:14 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155707]: ERROR: tm [t_fwd.c:470]: prepare_new_uac(): can't fwd to af 2, proto 1 (no corresponding listening socket) Sep 21 17:41:14 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155697]: ERROR: <core> [core/forward.c:183]: get_out_socket(): no corresponding socket found for(udp:208.74.138.184:5060) Sep 21 17:41:14 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155694]: ERROR: <core> [core/forward.c:183]: get_out_socket(): no corresponding socket found for(udp:192.40.216.97:5060) Sep 21 17:41:14 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155694]: ERROR: <core> [core/forward.c:183]: get_out_socket(): no corresponding socket found for(udp:208.74.138.180:5060) Sep 21 17:41:14 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155714]: ERROR: <core> [core/forward.c:183]: get_out_socket(): no corresponding socket found for(udp:87.1.1.27:5060) The kamailio instance we are using is receiving around 1500 calls per second in average when we do start seeing these errors more frequently In this instance we are using multihomed the listen address list is children=14 socket_workers=1 listen=udp:192.168.99.70:5081 listen=udp:192.168.99.81:5060 listen=udp:87.1.1.27:5060 listen=tcp:192.168.96.105:8095 listen=tcp:87.1.1.27:5060 tcp_children=6 port=5060 We use the first worker only to perform the OPTIONS requests from the dispatcher module. The sockets listen=udp:192.168.99.81:5060 listen=udp:87.1.1.27:5060 are used to communicate both A and B legs so when a message is received at 192.168.99.81:5060 we send it to 87.1.1.27:5060 and viceversa We were using $fs variable before doing the t_relay() function. This way is working, but when load increases, seems sometimes kamailio doesn't get the proper socket to forward the reply. I think the errors mainly are related to responses which are being forwarded, like if the function get_sock_info_list was not able to retrieve the listen interfaces we have tried to set in the onreply routes the commands set_recv_socket("udp:192.168.99.81:5060"); set_send_socket("udp:87.1.1.27:5060"); (when reply goes from private to public domain) and it seems it reduces the number of Sep 21 17:41:13 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155702]: ERROR: <core> [core/forward.c:183]: get_out_socket(): no corresponding socket found for(udp:164.152.22.248:5060) Sep 21 17:41:13 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155698]: ERROR: <core> [core/forward.c:183]: get_out_socket(): no corresponding socket found for(udp:208.74.138.184:5060) Sep 21 17:41:13 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155695]: ERROR: <core> [core/forward.c:183]: get_out_socket(): no corresponding socket found for(udp:208.74.138.181:5060) Sep 21 17:41:14 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155693]: ERROR: <core> [core/forward.c:183]: get_out_socket(): no corresponding socket found for(udp:38.102.250.60:5060) errors But i honestly don't know why the Sep 21 17:41:14 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155707]: ERROR: tm [ut.h:302]: uri2dst2(): no corresponding socket for "87.1.1.27" af 2 Sep 21 17:41:14 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155707]: ERROR: tm [t_fwd.c:470]: prepare_new_uac(): can't fwd to af 2, proto 1 (no corresponding listening socket) appear We aldso tried to increase the kernel buffers rmem and wmem from 208KB (as we had by default) to 4MB Do you know a reason which could cause these logs to appear? Any setup that could mitigate them? thanks a lot and regards david escartin -- <http://www.sonoc.io/> David Escartín NOC engineer www.sonoc.io [image: LinkedIn] <https://www.linkedin.com/company/sonoc> [image: Twitter] <https://twitter.com/sonoc_> [image: Instagram] <https://www.instagram.com/sonoc.io/> This e-mail is for the exclusive use of its recipients and may contain business secrets or other confidential or privileged information. Any unauthorised use, copying, publication or distribution of this e-mail is strictly prohibited. If you are not the intended recipient, please inform us immediately by replying to this e-mail and delete it, including any attachments or copies on your system. In accordance with the GDPR (EU) 2016/679 and the LOPDGDD 3/2018, we inform you that this e-mail address and/or any other personal data you have provided us with will be treated by SONOC with absolute confidentiality and with the only purpose of providing you with the requested services, due to your condition as a client, supplier or because you have requested information from us at any time. These data will only be kept for as long as required to comply with legal obligations. You can exercise your rights at any time by sending an e-mail to: dataprotection(a)sonoc.io. <dataprotection(a)sonoc.io>

1 0

Change in mailing list configuration related to DMARC spam filtering
by Henning Westerholt 22 Sep '23

22 Sep '23

Hello, due to some changes from certain cloud infrastructure provider related to spam filtering with DMARC, we need to change the list manager "mailman" configuration for the following lists: * sr-users * sr-user-es * sr-dev * business * sr-docs * kamailio-announce * the administrative mailing list The change will impact the "From" that is displayed in your email program. Without that change large e-mail providers (Gmail, Microsoft O365) will reject messages from a sender with certain strict DMARC policy. This is already affecting several people on the lists (for example with GitHub notice mails), but over time the problem will certainly increase. Regarding the technical change: We will munge the From: header so it doesn't contain the domain that triggers the DMARC rejection. Essentially, the Mailman list takes ownership of the message and injects its own address into the From: header. This can affect reply-to-sender, although we add the original From: address in the Reply-To: header (or sometimes the Cc: header) to reduce the impact of this. We plan to do this for all emails unconditionally, regardless of their sender DMARC policy, to have an identical behaviour for all users. Please refer to this [1] page for more details. For a general description of DMARC refer to this page [2]. This change should have not a big impact for you, but some users might need to adapt some mail filters. Therefore, we would like to gather feedback on that change from you. We expect that the most visible change is that It will be not possible anymore to just reply by e-mail to mails from GitHub and have them "automatically" added to the discussed issue. This feature was so far used rarely and only from a few people. We plan to implement this change by the end of this week, when its done it will be also shortly announced. Best regards, Henning Westerholt [1] https://wiki.list.org/DEV/DMARC [2] https://dmarc.org/overview/ -- Henning Westerholt - https://skalatan.de/blog/ Kamailio services - https://gilawa.com<https://gilawa.com/>

1 1

RTP traffic through kamailio
by Shravan 22 Sep '23

22 Sep '23

2 1

insert_dlg_timer(): Trying to insert a bogus dlg
by Benoît Panizzon 22 Sep '23

22 Sep '23

Hi Team Could anyone point me in the direction where I could find out more what's going wrong and what could be the cause of messages like: Sep 22 07:32:29 dev-core02 kamailio[915066]: CRITICAL: dialog [dlg_timer.c:129]: insert_dlg_timer(): Trying to insert a bogus dlg tl=0x7f9617d967b0 tl->next=0x7f9618e11198 tl->prev=0x7f9617e20548 Sep 22 07:32:29 dev-core02 kamailio[915066]: CRITICAL: dialog [dlg_dmq.c:314]: dlg_dmq_handle_msg(): Unable to insert dlg timer 0x7f9617d96750 [1598:12168] Are the numbers in brackets [hash_id:hash_entry] ? -- 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

Dialog: bogus event 2 in state 3
by Benoît Panizzon 21 Sep '23

21 Sep '23

Hi Team I'm still hunting dialog errors which cause my dialog counters to divert and stick around, basically exploding in my face now and then. I suppose they are DMQ related (maybe packet loss, maybe retransmissions, maybe generic overloading of the virtualized kamailio instances) causing issues with inserting dialog timers on the peer etc. So for the moment I'm running only one instance, no DMQ peer. What I still occasionally see are messages: INVITE]dialog [dlg_hash.c:1182]: next_state_dlg(): bogus event 2 in state 3 for dlg 0x7ff906294be8 [2482:872] with clid 'A8459C74@7f33ff47' and tags '7f33ff47+1+7d820120+89494caf' '3904288054-1882699775' I found an ancient post, confirming this to be an open bug in Kamailio 1.4 and race condition between the 200 OK reply to an INVITE and the ACK confirming the 200 OK. Someone attempted to backport a fix for opensips to kamailio. Indeed, I see this message occur occasionally after managing the 200 OK reply and routing the ACK. Does anyone know, if this is still a open bug with Kamailio 5.5? Or what else could be the cause of this message? -- 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

Floating Point in variables and arithmetic
by Barry Flanagan 21 Sep '23

21 Sep '23

Hi I need to take in a priority (from 0 to 100, 0 being highest prio) and convert this into a Q value between 0 and 1.0 My idea was to simply do: q_value = 1 - ($var(priority)/100) However, it seems Kamailio only deals in integers in the config. A Previous post suggested using xavp vars, but this ends up the same result. Apart from doing a pseudo SQL query "SELECT 1 - (20/100)" is there any way within the config I can do such maths? Thanks -- -Barry Flanagan

2 8

uac_auth() in KEMI Python - Drop 401 sent to caller
by Marrold 21 Sep '23

21 Sep '23

Hi all, I'm attempting to use the uac module in KEMI (Python) to authenticate outbound requests. When the downstream replies with a 401 the proxy correctly re-sends the request with a Authorization header, but the 401 is also relayed to the caller. As far as I can tell I've converted the example to KEMI correctly, but no matter what I try the 401 is still sent to the caller. Any ideas? The config I'm using is below - The avps are set when the request is sent so aren't visible here. Thanks def ksr_failure_manage(self, msg): if self.ksr_route_natmanage(msg)==-255 : return 1 if KSR.tm.t_is_canceled()>0 : return 1 if KSR.tm.t_check_status("401|407") >0 : KSR.info(f"Got a 40X, should attempt authentication") if KSR.uac.uac_auth()>0: KSR.tm.t_relay() KSR.info (f"Dropping further replies") KSR.set_drop() exit() return 1

2 1

Handle the DNS SRV to manage failover
by Massimo Dal Sasso 20 Sep '23

20 Sep '23

I need to manage failover in the connection between SCSCF and AS. I need to understand how it is possible to configure Kamailio to handle the DNS SRV to manage failover for UAS transaction like REGISTER. I see that it works for UAC transaction like INVITE, but I am not able to configure Kamailio to work for UAS transaction. Thanks, Massimo ________________________________ Massimo Dal Sasso SW Developer massimo.dalsasso(a)ext.athonet.com [Athonet logo]<https://www.athonet.com/> the mobile core that works for you Athonet Italy Via Cà del Luogo 6/8 36050 Bolzano Vicentino Vicenza-Italy +39 0444 750045 This email and any attachments are confidential and intended solely for the use of the intended recipient. If you are not the named addressee, please be aware that you shall not distribute, copy, use or disclose this email. If you have received this email by error, please notify us immediately and delete this email from your system. Email transmission cannot be guaranteed to be secured or error-free or not to contain viruses. Athonet S.r.l. processes any personal data exchanged in email correspondence in accordance with EU Reg. 679/2016 (GDPR) - you may find here the privacy policy with information on such processing and your rights. Any views or opinions presented in this email are solely those of the sender and do not necessarily represent those of Athonet S.r.l.

1 0

Creating CDRs for Missed and failed calls
by Marrold 19 Sep '23

19 Sep '23

Hi all, I'm using the acc module along with postgres to generate CDRs. For connected calls the CDRs are created as expected, but in the scenario where a lookup() fails and Kamailio sends a stateless 404 there's no CDR logged. I'm setting the FLT_ACCMISSED and FLT_ACCFAILED flags in the initial request route, but perhaps I have a misunderstanding of how these work? Thanks Matthew

2 2

How to validate re-invites without challenging them?
by Benoit Panizzon 19 Sep '23

19 Sep '23

Hi List At the moment, we challenge every invite (and re-invite) to make sure the customer is authenticated. Now we have one kind of PBX, which never does not authenticate when we challenge a Re-Invite. According to the vendor of that PBX's RFC interpretation, answering a challenge to a re-invite is optional. If that is ignored by the PBX, then the existing established dialog shall not end. Unfortunately this causes the session timer to run out. I am therefore wondering, if there is a safe way not to challenge re-invites. A Re-Invite contains a To-Tag. So I could bypass authentication on presence of a to-Tag. But then, how do I prevent a customer to just set a spoofed To-Tag to circumvent authentication? Is there a feasible 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 ______________________________________________________

4 3

DBTEXT + TOPOS
by James Lipski 19 Sep '23

19 Sep '23

Hello, I'm doing an experiment with the DB_TEXT module. I have the topos module enabled; however it doesn't seem to function properly with db_text. Going over my syslog I see the following, and not quite understanding why it's failing to insert the row; I was hoping someone can point me in the right direction. This is a fresh install/ fresh DB. Thank you. Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:227]: dbt_load_file(): column[5] is actually STRING! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:195]: dbt_load_file(): column[6] is STR! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:227]: dbt_load_file(): column[6] is actually STRING! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:195]: dbt_load_file(): column[7] is STR! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:227]: dbt_load_file(): column[7] is actually STRING! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:200]: dbt_load_file(): column[8] is INT! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:195]: dbt_load_file(): column[9] is STR! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:227]: dbt_load_file(): column[9] is actually STRING! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:239]: dbt_load_file(): column[9] NULL flag set! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:195]: dbt_load_file(): column[10] is STR! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:227]: dbt_load_file(): column[10] is actually STRING! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:195]: dbt_load_file(): column[11] is STR! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:227]: dbt_load_file(): column[11] is actually STRING! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:239]: dbt_load_file(): column[11] NULL flag set! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:195]: dbt_load_file(): column[12] is STR! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:227]: dbt_load_file(): column[12] is actually STRING! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:239]: dbt_load_file(): column[12] NULL flag set! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:195]: dbt_load_file(): column[13] is STR! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:227]: dbt_load_file(): column[13] is actually STRING! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:239]: dbt_load_file(): column[13] NULL flag set! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:195]: dbt_load_file(): column[14] is STR! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:227]: dbt_load_file(): column[14] is actually STRING! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:195]: dbt_load_file(): column[15] is STR! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:227]: dbt_load_file(): column[15] is actually STRING! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:195]: dbt_load_file(): column[16] is STR! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:227]: dbt_load_file(): column[16] is actually STRING! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:195]: dbt_load_file(): column[17] is STR! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:227]: dbt_load_file(): column[17] is actually STRING! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:195]: dbt_load_file(): column[18] is STR! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:227]: dbt_load_file(): column[18] is actually STRING! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:195]: dbt_load_file(): column[19] is STR! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:227]: dbt_load_file(): column[19] is actually STRING! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:195]: dbt_load_file(): column[20] is STR! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:227]: dbt_load_file(): column[20] is actually STRING! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:195]: dbt_load_file(): column[21] is STR! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:227]: dbt_load_file(): column[21] is actually STRING! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:195]: dbt_load_file(): column[22] is STR! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:227]: dbt_load_file(): column[22] is actually STRING! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:195]: dbt_load_file(): column[23] is STR! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:227]: dbt_load_file(): column[23] is actually STRING! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:195]: dbt_load_file(): column[24] is STR! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:227]: dbt_load_file(): column[24] is actually STRING! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:195]: dbt_load_file(): column[25] is STR! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:227]: dbt_load_file(): column[25] is actually STRING! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:119]: db_new_result(): allocate 56 bytes for result set at 0x7fd70c7f4c40 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:156]: db_allocate_columns(): allocate 160 bytes for result names at 0x7fd70cacabf8 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:167]: db_allocate_columns(): allocate 80 bytes for result types at 0x7fd70c7f4ce0 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_api.c:73]: dbt_get_columns(): allocate 16 bytes for RES_NAMES[0] at 0x7fd70cacad00 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_api.c:73]: dbt_get_columns(): allocate 16 bytes for RES_NAMES[1] at 0x7fd70cacad78 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_api.c:73]: dbt_get_columns(): allocate 16 bytes for RES_NAMES[2] at 0x7fd70cacadf0 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_api.c:73]: dbt_get_columns(): allocate 16 bytes for RES_NAMES[3] at 0x7fd70cacae68 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_api.c:73]: dbt_get_columns(): allocate 16 bytes for RES_NAMES[4] at 0x7fd70cacaee0 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_api.c:73]: dbt_get_columns(): allocate 16 bytes for RES_NAMES[5] at 0x7fd70cacaf58 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_api.c:73]: dbt_get_columns(): allocate 16 bytes for RES_NAMES[6] at 0x7fd70cacafd0 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_api.c:73]: dbt_get_columns(): allocate 16 bytes for RES_NAMES[7] at 0x7fd70cacb048 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_api.c:73]: dbt_get_columns(): allocate 16 bytes for RES_NAMES[8] at 0x7fd70cacb0c0 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_api.c:73]: dbt_get_columns(): allocate 16 bytes for RES_NAMES[9] at 0x7fd70cacb138 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_api.c:73]: dbt_get_columns(): allocate 16 bytes for RES_NAMES[10] at 0x7fd70cacb1b0 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_api.c:73]: dbt_get_columns(): allocate 16 bytes for RES_NAMES[11] at 0x7fd70cacb228 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_api.c:73]: dbt_get_columns(): allocate 16 bytes for RES_NAMES[12] at 0x7fd70cacb2a0 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_api.c:73]: dbt_get_columns(): allocate 16 bytes for RES_NAMES[13] at 0x7fd70cacb318 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_api.c:73]: dbt_get_columns(): allocate 16 bytes for RES_NAMES[14] at 0x7fd70c7c2368 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_api.c:73]: dbt_get_columns(): allocate 16 bytes for RES_NAMES[15] at 0x7fd70c7c23e0 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_api.c:73]: dbt_get_columns(): allocate 16 bytes for RES_NAMES[16] at 0x7fd70c7c2458 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_api.c:73]: dbt_get_columns(): allocate 16 bytes for RES_NAMES[17] at 0x7fd70c7c24d0 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_api.c:73]: dbt_get_columns(): allocate 16 bytes for RES_NAMES[18] at 0x7fd70c7c2548 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_api.c:73]: dbt_get_columns(): allocate 16 bytes for RES_NAMES[19] at 0x7fd70c7c25c0 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} topos [tps_storage.c:1244]: tps_db_load_branch(): no stored record for <z9hG4bK22d5.7fedda308f2b91b2c0c83021c6adfaec.0> Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:79]: db_free_columns(): freeing 20 columns Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[0] at 0x7fd70cacad00 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[1] at 0x7fd70cacad78 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[2] at 0x7fd70cacadf0 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[3] at 0x7fd70cacae68 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[4] at 0x7fd70cacaee0 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[5] at 0x7fd70cacaf58 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[6] at 0x7fd70cacafd0 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[7] at 0x7fd70cacb048 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[8] at 0x7fd70cacb0c0 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[9] at 0x7fd70cacb138 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[10] at 0x7fd70cacb1b0 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[11] at 0x7fd70cacb228 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[12] at 0x7fd70cacb2a0 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[13] at 0x7fd70cacb318 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[14] at 0x7fd70c7c2368 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[15] at 0x7fd70c7c23e0 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[16] at 0x7fd70c7c2458 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[17] at 0x7fd70c7c24d0 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[18] at 0x7fd70c7c2548 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[19] at 0x7fd70c7c25c0 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:96]: db_free_columns(): freeing result names at 0x7fd70cacabf8 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:101]: db_free_columns(): freeing result types at 0x7fd70c7f4ce0 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:138]: db_free_result(): freeing result set at 0x7fd70c7f4c40 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [core/utils/sruid.c:214]: sruid_nextx(): new sruid is [tpsh-6508d6d9-14577b-1] (1 / 22) Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} topos [tps_storage.c:451]: tps_storage_fill_contact(): td->bs <sip:leg_a@host1.sip-example.com;ccr=btpsh-6508d6d9-14577b-1> Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} topos [tps_storage.c:454]: tps_storage_fill_contact(): td->as <sip:leg_b@host1.sip-example.com;ccr=atpsh-6508d6d9-14577b-1> Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} topos [tps_storage.c:552]: tps_storage_link_msg(): downstream: yes - acontact: [sip:133@172.16.1.169:33880;line=g2l0pi9q;alias=72.255.5255.255~33880~1] - bcontact: [] Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_lib.c:285]: dbt_db_get_table(): cache or mtime succeeded for [topos_t] Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: ERROR: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_tb.c:468]: dbt_table_check_row(): null value not allowed - field 2 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: ERROR: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_base.c:525]: dbt_insert(): cannot insert the new row!! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: ERROR: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} topos [tps_storage.c:1004]: tps_db_insert_branch(): failed to store message Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: ERROR: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} topos [tps_storage.c:615]: tps_storage_record(): failed to store

2 1

Using maxload in dispatcher list
by Calvin E. 19 Sep '23

19 Sep '23

Should maxload work with all dispatcher algorithms? I'm trying to add a test node to dispatcher.list with maxload=1 and it is getting a lot more than one concurrent call. The test node is the last one in the list. 16 sip:10.x.x.43:5070 0 0 duid=duid01;user=+10007787878;sockname=floating-internal-ip;maxload=0 16 sip:10.x.x.44:5070 0 0 duid=duid02;user=+10007787878;sockname=floating-internal-ip;maxload=0 16 sip:10.x.x.47:5070 0 0 duid=duid03;user=+10007787878;sockname=floating-internal-ip;maxload=0 16 sip:10.x.x.48:5070 0 0 duid=duid04;user=+10007787878;sockname=floating-internal-ip;maxload=0 16 sip:10.x.x.56:5070 0 0 duid=duid05;user=+10007787878;sockname=floating-internal-ip;maxload=0 16 sip:10.x.x.57:5070 0 0 duid=duid06;user=+10007787878;sockname=floating-internal-ip;maxload=0 16 sip:10.x.x.58:5070 0 0 duid=duid07;user=+10007787878;sockname=floating-internal-ip;maxload=0 16 sip:10.x.x.x:5070 0 0 duid=duid08;user=+10007787878;sockname=floating-internal-ip;maxload=0 16 sip:10.x.x.104:5060 0 0 duid=duid09;user=+10007787878;sockname=floating-internal-ip;maxload=1

2 1

SIP Registartion Sharing between two kamailio
by Lewis Hutchinson 19 Sep '23

19 Sep '23

On the understanding that you have checked the INVITE to 802 and it looks OK but not getting there then I would probably start digging on the networking side of it. You have said no Firewalls however there may be Security Groups and VPC bits going on in AWS. It's hard to say as the level of detail is not in the ticket. Can 802 call 801? What happens if you log 802 into Kamailio 1 and 801 into Kamailio 2 and call either way. Lewis Mission Labs Limited is registered in England, company number 10040088. Trading Office: The Old Milk Depot, Bacup Rd, Rossendale, BB4 7FE. Registered office: The Scalpel, 18th Floor 52 Lime Street, London, EC3M 7AF. Email confidentiality notice: This message is private and confidential. If you have received this message in error, please notify us and remove it from your system. Please consider the environment before you print this email.

1 0

SIP Registartion Sharing between two kamailio using AWS NLB having issue.
by pra.savaliya1987＠gmail.com 19 Sep '23

19 Sep '23

Hello All, I have two kamailio servers and shared the database between two kamailio. version: kamailio 5.5.6 (x86_64/linux) . I have used AWS network load balancer. domain pointed to AWS network load balancer IP address,AWS Network Load Balancer (NLB) to distribute incoming requests to kamailio servers. I have two users in same domain(dev.domain.com). 1. 801(a)dev.domain.com --> Registered on kamailio 1 2. 802(a)dev.domain.com --> Registered on kamailio 2 Two call invites have been received, one for extension 801 and another for extension 802. These call invites will reach kamailio Server 1. kamailio Lookup the users and send call invite to both the devices. 801 registered user will get a ring because it is registered from kamailio 1. but 802 will not get a ring because it's register from kamailio 2. I can able see kamailio send call invite to the both registered devices using sngrep. but it not reach to the 802 device. there i no firewalls so far. also i have took 802 Registered device IP phone logs but there is no Call Invite reach to the 802 device. I have also tried by using "dmq" and "dmq_usrloc" module but the same behavior. what could be the reason? It will be appreciable if anyone help to resolve the issue. Thank you in advance! Pratik Svaliya.

2 1

Increase MAX_BRANCHES_LIMIT
by Lars Jansson 18 Sep '23

18 Sep '23

Hi, I am building a configuration script where for some traffic flows parallel forking will be needed, and in this case I need to go beyond the default max limit of the max amount of branches. Apart from this specific case the traffic load that kamailio will need to handle is very low, let's say just one second here and there with up to 5 concurrent calls at most. This limit is as far as I understand set here: usr/local/src/kamailio-5.6/kamailio/src/core/config.h And the default limit is: #define MAX_BRANCHES_LIMIT 32 /*!< limit of maximum number of branches per transaction */ Here are the questions I have related to this: 1) If I increase the value of this constant in config.h, how high is it reasonable to set this value and still have a stable system? 2) If I increase MAX_BRANCHES_LIMIT beyond 32, are there also other parameters that needs to be changed for the system to be able to cope, and if so whichparameters? Regards, Lars

4 9

. Re: Multiple headers in http client request
by Lewis Hutchinson 18 Sep '23

18 Sep '23

Hi Matteo I have used http_async_client and http_client in both Native & KEMI to good affect for handling SUBSCRIBE & NOTIFY flows however did have a few issues with formatting which took a bit of work to get right. Just to note, something you may want to test. Initially I set about my task using http client within Python (aiohttp and ayncio) and stepped in and out of it from various points in the logic depending on the config I was using at the time. Under load this proved to be a bottle neck and failed load testing. The best options under load were using http_async_client or http_client modules which offered significantly better performance. In the end we took a different approach of using Kafka Module as that had even better performance but that was a decision taken our side not through any fault of the http_async_client or http_client modules Lewis Mission Labs Limited is registered in England, company number 10040088. Trading Office: The Old Milk Depot, Bacup Rd, Rossendale, BB4 7FE. Registered office: The Scalpel, 18th Floor 52 Lime Street, London, EC3M 7AF. Email confidentiality notice: This message is private and confidential. If you have received this message in error, please notify us and remove it from your system. Please consider the environment before you print this email.

1 0

Add Header to reply on failure_route
by Benoit Panizzon 18 Sep '23

18 Sep '23

Hi List I'm attempting to add a header to a reply message on failure. Situation: Registrar => Core => (dispatcher list) => Various IC I would like to know on the registrar, which of the dispatcher groups failed. What I attempted sofar: failure_route[DISPATCH_FAILURE] { append_to_reply("X-RR: (append reply) Final Dispatch Failure $avp(dispgroup):$avp(trunkname)\r\n"); append_hf("X-RR: (append hf) Final Dispatch Failure $avp(dispgroup):$avp(trunkname)\r\n"); $avp(rstatus) = t_get_status_code(); $avp(rtext) = $T_rpl($rr); $avp(rtext) = "REMOTE REPLY: " + $T_rpl($rr); t_send_reply("$avp(rstatus)", "$avp(rtext)"); } I only get status text is getting through to my reply. I would much prefer to add a header which I could then extract on the registrar. Am I missing something which could prevent addition of a header in a reply? 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 1

Multiple headers in http client request
by Matteo Brancaleoni 17 Sep '23

17 Sep '23

Hello all :) I'm struggling to add two headers to an http client request, but cannot find a proper way to do it. The headers are Authorization and Content-Type. The first try is with http_client module, beside undocumented, is possible to add multiple headers separating them with "\r\n". What I see is the correct Authorization header, and two Content-Type headers, one with my content type the other with x-www-form-urlencoded, which no one sets ? Second try is with http_async_client which supports multiple headers, but since I'm calling it from an xhttp event route, there's no transaction and request cannot be suspended, so I cannot get results before sending out xhttp response... Any hint? br, Mat

2 3

Orphan Dialog Vars: Probable cause found!
by Benoît Panizzon 15 Sep '23

15 Sep '23

Hi List I wonder if some of the devs could look at the dialog code and maybe confirm my observation of this supposed Bug in Kamailio 5.6 Situation: Two Kamailio, dialog counters synced via DMQ and each node using a local DB as dialog backend. Goal is to count channel usage per customer. modparam("dialog", "db_mode", 1 ) modparam("dialog", "enable_dmq", 1) modparam("dialog", "h_id_start", -1) # Use server_id modparam("dialog", "h_id_step", 2) modparam("dialog", "profiles_with_value", "custcallcounter") If 'JohnDoe' is involved in a call, I do: set_dlg_profile("custcallcounter","JohnDoe"); To check how many calls are busy by JohnDoe I do: get_profile_size("custcallcounter","JohnDoe","$var(channel_use)"); Picture this situation: JohnDoe is initiating a first call via Node1: Node1 created the dialogue and variables, writes them to the database and replicates the dialog vars to Node2 => IN MEMORY Nothing about the running dialog is being written to the Database on Node2, but get_profile_size returns the count on Node2. So while the first call aka dialog is running via Node1, JohnDoe is initiating a second call, this time via Node2. Node2 creates the dialog and writes this to the database. Then the profile with Name 'JohnDoe' is INCREASED on Node2. This is when I suddenly find the dialog_vars on the Node2 database containing information about the dialog started on Node1. So I guess writing to a dialog counter triggers the dialog_vars being written to the Database. When JohnDoe is ending it's first call, then the dialog and dialog_vars are cleaned out of the database on Node1, but NOT on Node2 What I fear happens next: They dialog_vars remaining on the Database of Node 2 accumulate more and more, making the database slower. When a call happens to re use the same hash id and entry, things start going really badly. Could I be right? -- 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

Set a License for Kamailio
by Ali Taher 15 Sep '23

15 Sep '23

Hello, Is it possible to put a kind of license for Kamailio, in a way that it works for 1 week for example, and after that it will not process new requests? Regards,

3 4

client sending message and refresh register normal. But KSR.uac.uac_req_send() ERROR
by riffs＠sina.cn 14 Sep '23

14 Sep '23

The client uses the TLS protocol registered and TCP Connection established . There is a problem now, sending message KSR.uac.uac_req_send() from the kamilio server to client failed sometimes,and the error is as follows： “2023-09-04T17:22:01.515763+08:00 (3429) ERROR: tm [../../core/forward.h:292]: msg_send_buffer(): tcp_send failed 2023-09-04T17:22:01.515763+08:00 (3429) ERROR: tm [uac.c:678]: send_prepared_request_impl(): Attempt to send to precreated request failed ”. meantime, the client sending message to Kamalio server succeded, and the register status and tcp connection is normal. After 30s, obtained the $uac_req(evcode) from the event_route[uac:reply] is 408.After this error appears, all the messages sent to this client are 408. " 2023-08-29T03:48:43.738152+08:00 (3349) NOTICE: <script>: ===uac reply received, callid = 0B6ECB534AE24281AED9BBBC56B140A6`yangwang2`1693252093, code is: 408 2023-08-29T03:48:43.738825+08:00 (3349) NOTICE: <script>: ===uac reply received, callid = 0B6ECB534AE24281AED9BBBC56B140A6`yangwang2`1693252093, code is: 408 " But from other information, the TCP connection is normal. Because from Kamailio to querying this user's Location, it has not changed all day. The client sends messages is also normal. That is, the user's registration and sending messages can receive 200 OK. We use netstat commands to view the user's TCP connection information on the client and server, and the connection status is also normal.The status of the corresponding port of the TCP connection is ESTABLISHED. client: netstat -ano | findstr 49957 "172. 17. 47.125:49957 XXX.96.XXX.XXX:5061 ESTABLISHED 10516" server: "tcp 0 0 10.11.xx.xx:5061 xxx.xxx.xxx.xxx:49957 ESTABLISHED 3467/kamailio" This client is normal after logging in, and the problem that occurs after a period of use (maybe some hours), and once it occurs, it fails until the user creates a new connection and logs back in. Not all users will appear. Why is this the case? The socket connection is fine, but uac_req_send () get an ERROR? I found a problem from the log file. Is it caused by duplicate callids pushed to the same user at the same second? Looking forward to your answer, thank you very much Script information that may be required kamailio.cfg ： tm mode # ----- tm params ----- # auto-discard branches from previous serial forking leg modparam("tm", "failure_reply_mode", 3) # default retransmission timeout: 30sec modparam("tm", "fr_timer", 30000) # default invite retransmission timeout after 1xx: 120sec modparam("tm", "fr_inv_timer", 120000) modparam("tm", "auto_inv_100", 1) kamalio.lua uac_req_send() " --uac_req_send KSR.pv.sets("$uac_req(hdrs)", hdrs) KSR.pv.sets("$uac_req(method)", "MESSAGE") KSR.pv.sets("$uac_req(ruri)", "sip:" .. to .. "@" .. KAM_DOMAIN) KSR.pv.sets("$uac_req(furi)", "sip:" .. from .. "@" .. KAM_DOMAIN) KSR.pv.sets("$uac_req(turi)", "sip:" .. to .. "@" .. KAM_DOMAIN) KSR.pv.seti("$uac_req(evroute)", 1) KSR.pv.sets("$uac_req(body)", content) local ouri = (row.received ~= "" and row.received) or row.contact KSR.pv.sets("$uac_req(ouri)", ouri) local callid = rows[i].clientid .. "`" .. rows[i].username .. "`" .. os.time() KSR.pv.sets("$uac_req(callid)", callid) KSR.uac.uac_req_send()

1 0

MS Teams and ca_list.pem
by Social Boh 13 Sep '23

13 Sep '23

Hello, I'd like to know where i can download/search ca_list.pem file to use in tls.cfg configuration file for MS TEAMS. Without the file: ERROR: tls [tls_util.h:50]: tls_err_ret(): TLS write:error:0A000086:SSL routines::certificate verify failed (sni: unknown) ERROR: tls [tls_server.c:1336]: tls_h_read_f(): src addr: 52.114.76.76:506 ERROR: tls [tls_server.c:1339]: tls_h_read_f(): dst addr: KamailioIP:0 ERROR: <core> [core/tcp_read.c:1476]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7fb6a23ba4f8 r: 0x7fb6a23ba620 (-1) Thank you Regards -- --- I'm SoCIaL, MayBe

1 0

number based routing and NATed peers
by Kiss Zoltán 12 Sep '23

12 Sep '23

Hello, Im gathering ideas about routing based on caller number to multiple peers and -lets say- subscribers. As far as i know we can route the calls with LCR based on prefix or the whole number to the LCR gateways which are specified in the LCR module gateway table. This is working very well with public IP based "peers". We can route calls to these gateways. But what can we do if we have to route to a "peer" which is behind NAT. Basically they have to REGISTER as a subscriber, but we cannot add a subscriber to the LCR gateway table, beacuse LCR module needs a directly reachable IP address with a fixed port. Does anyone have any ideas on how to handle these mixed type peers? Or maybe we have to add the fixed IP peers which are not REGISTERing to the usrloc database somehow and then we can do a lookup location based on $rU. To make myself clear, it would be nice if we can handle those 2 types of our peers unifromly in terms of SIP routing, thats why im looking for a "unified" solution. Thanks for your suggestions. With kind regards, Zoltan

1 0

Skip/discard branch in branch route?
by Benoît Panizzon 11 Sep '23

11 Sep '23

Hi all Is there a way to skip a branch in branch route? Situation: Two registrar server with DMQ synced location database. CPE register via TCP or TLS. To properly work, message have to be sent over the existing TCP connection. Multiple CPE register to one AOR. CPE1 and CPE2 register to Registrar 1 CPE3 registers to Registrar 2 On Registrar 1 there is an established TCP connection to CPE1 and CPE2 but not to CPE3. Within the Branch Route to the CPE I can check if there is a TCP as the Branch Route is executed for every contact in that AOR: branch_route[BR_TO_CPE] { [...] $var(reg_contact_addr) = $(ulc(aor=>addr)[$T_branch_idx]{uri.host}); $var(socket) = $(ulc(aor=>socket)[$T_branch_idx]); if ($var(socket) == 0) { xlog("L_ERROR", "$cfg(route): No Socket for: $var(reg_contact_addr)"); } [...] } This log an error if the socket is not present on the local registrar. But is there a way to tell kamailio to skip/discard that contact? My intention is to parallel branch from the core to both registrars, that way all contacts would still get the call but via established TCP socket (and in case of UDP and NAT via correct know ip for ALG port-forwarding). -- 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 12

load_module(): could not find module <mi_fifo> in </usr/lib64/kamailio/modules/>
by amit＠cosmicinfotech.com 08 Sep '23

08 Sep '23

using kamailio 5.3.9 [244@root ~]$ kamailio -f /etc/kamailio/kamailio.cfg -E loading modules under config path: /usr/lib64/kamailio/modules/ 0(1071336) ERROR: <core> [core/sr_module.c:500]: load_module(): could not find module <mi_fifo> in </usr/lib64/kamailio/modules/> 0(1071336) CRITICAL: <core> [core/cfg.y:3543]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 294, column 12-23: failed to load module 0(1071336) ERROR: <core> [core/modparam.c:176]: set_mod_param_regex(): No module matching <mi_fifo> found 0(1071336) CRITICAL: <core> [core/cfg.y:3546]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 582, column 63: Can't set module parameter ERROR: bad config file (2 errors) 0(1071336) INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized please help!

2 2

Re: uac_replace_to() without RR params
by Duarte Rocha 08 Sep '23

08 Sep '23

2 1

Question about a Slow timer process.
by Володимир Іванець 07 Sep '23

07 Sep '23

Hello everyone! I'm running Kamailio 5.6.2 and having a potential problem on one of the systems. The Slow timer process slowly consumes more and more of its PKG memory. I did not allow it to use all memory by restartink Kamailio during afterhours so I'm not sure what the consequences might be. I'm suspecting that this could be caused by my configuration but not sure how exactly. Can anyone please tell me how the Slow timer process can be debugged? Is it possible to see what it is storing in the memory and what data is piling up? Thanks a lot! Regarts, Volodymyr Ivanets.

1 0

uac_replace_to() without RR params
by Duarte Rocha 07 Sep '23

07 Sep '23

Hello all, I'm currently working on a proxy where I need to change To and From headers in order to normalize the numbers to +E164. I would like to be able to restore using and $avp() or $dlg_var() and without writing parameters on the Record-Route headers. I've tried to use restore_mode in auto mode and restore_dlg parameter with value 1 but still got the parameters on the inserted Record-Route. I've tried manual mode and using the configured $avp() to restore, but the parameters still got written on the Request-URI. I thought of using restore_mode with value "none" saving original values in an $avvp() and doing the replace, however, uac_replace() on Request Route or branch routes. That way i can't replace the values of To and From in the replies. That being said, my questions are : - Is there a way to use manual or auto mode without writing info on the Record-Route and only using $avp() ? - Is there a way to make changes on the To and From header on replies? Thanks in advance, Best Regards, Duarte Rocha

1 0

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