sr-users January 2023

sr-users@lists.kamailio.org

56 participants
70 discussions

unsubscribe.pls
by Stanly Levyy 11 Jan '23

11 Jan '23

*** THIS E-MAIL MESSAGE AND ANY DOCUMENTS ATTACHED IS/ARE INTENDED ONLY FOR THE USE OF THE INDIVIDUAL(S) OR ENTITY TO WHICH IT IS ADDRESSED; AND MAY CONTAIN INFORMATION THAT IS LEGALLY PRIVILEGED, CONFIDENTIAL AND/OR EXEMPT FROM DISCLOSURE UNDER APPLICABLE LAW, including the Electronic Communications Privacy Act, 18 U.S.C. Secs 2510-2521 *** On Wednesday, January 11, 2023, 01:36:44 AM PST, <sr-users-request(a)lists.kamailio.org> wrote: Send sr-users mailing list submissions to sr-users(a)lists.kamailio.org To subscribe or unsubscribe via email, send a message with subject or body 'help' to sr-users-request(a)lists.kamailio.org You can reach the person managing the list at sr-users-owner(a)lists.kamailio.org When replying, please edit your Subject line so it is more specific than "Re: Contents of sr-users digest..." Today's Topics: 1. Re: Performing async_http calls on stateless Loadbalancers (Julius Flohr) 2. Re: Releasing v5.6.3 (Daniel-Constantin Mierla) 3. Performing async_http calls on stateless Load balancers (Lewis Hutchinson) ---------------------------------------------------------------------- Message: 1 Date: Tue, 10 Jan 2023 18:50:44 +0100 From: Julius Flohr <flohr(a)sipgate.de> Subject: [SR-Users] Re: Performing async_http calls on stateless Loadbalancers To: Henning Westerholt <hw(a)gilawa.com> Cc: "Kamailio (SER) - Users Mailing List" <sr-users(a)lists.kamailio.org>, Alles wird besser <alleswirdbesser(a)sipgate.de> Message-ID: <34C7487C-0900-4C49-BBB4-49A0291D83E6(a)sipgate.de> Content-Type: multipart/alternative; boundary=Apple-Mail-0AF7C672-1C85-4A98-9DDC-EED95FFB4B7E A message part incompatible with plain text digests has been removed ... Name: not available Type: text/html Size: 7117 bytes Desc: not available ------------------------------ Message: 2 Date: Wed, 11 Jan 2023 08:30:17 +0100 From: Daniel-Constantin Mierla <miconda(a)gmail.com> Subject: [SR-Users] Re: Releasing v5.6.3 To: "Kamailio (SER) - Users Mailing List" <sr-users(a)lists.kamailio.org>, "Kamailio (SER) - Devel Mailing List" <sr-dev(a)lists.kamailio.org> Message-ID: <454ae3b5-a810-f393-4196-e71c4482e9d3(a)gmail.com> Content-Type: text/plain; charset=UTF-8 Hello, the usual note that preparing the release of Kamailio v5.6.3 starts soon, therefore any commits to branch 5.6 should be announced first on sr-dev mailing list and wait for the ack before pushing to repo. Once the announcement is out, commits can go in the branch directly. Cheers, Daniel On 06.01.23 16:44, Daniel-Constantin Mierla wrote: > Hello, > > I am considering to release Kamailio v5.6.3 (out of branch 5.6) next > week (likely on Wednesday, Jan 11, 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 - June 5-7, 2023 - www.kamailioworld.com > -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - June 5-7, 2023 - www.kamailioworld.com ------------------------------ Message: 3 Date: Wed, 11 Jan 2023 09:20:28 +0000 From: Lewis Hutchinson <lewis.hutchinson(a)missionlabs.co.uk> Subject: [SR-Users] Performing async_http calls on stateless Load balancers To: "sr-users(a)lists.kamailio.org" <sr-users(a)lists.kamailio.org> Cc: "flohr(a)sipgate.de" <flohr(a)sipgate.de>, "alleswirdbesser(a)sipgate.de" <alleswirdbesser(a)sipgate.de> Message-ID: <CWXP265MB2517CB6E3E8188F3E3BB5B2AC5FC9(a)CWXP265MB2517.GBRP 265.PROD.OUTLOOK.COM> Content-Type: text/plain; charset="us-ascii" Hi Julius If I have understood this correctly, I think you can achieve this using KEMI Python leveraging aiohttp & asyncio i.e async with aiohttp.ClientSession() as session: This can be done outside of REQUEST_ROUTE Requires a rewrite from Native to KEMI so might be a bit excessive but would work. Regards Lewis ------------------------------ Subject: Digest Footer _______________________________________________ sr-users mailing list -- sr-users(a)lists.kamailio.org To unsubscribe send an email to sr-users-leave(a)lists.kamailio.org ------------------------------ End of sr-users Digest, Vol 212, Issue 33 *****************************************

1 0

Performing async_http calls on stateless Load balancers
by Lewis Hutchinson 11 Jan '23

11 Jan '23

Hi Julius If I have understood this correctly, I think you can achieve this using KEMI Python leveraging aiohttp & asyncio i.e async with aiohttp.ClientSession() as session: This can be done outside of REQUEST_ROUTE Requires a rewrite from Native to KEMI so might be a bit excessive but would work. Regards Lewis

1 0

Releasing v5.6.3
by Daniel-Constantin Mierla 11 Jan '23

11 Jan '23

Hello, I am considering to release Kamailio v5.6.3 (out of branch 5.6) next week (likely on Wednesday, Jan 11, 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 - June 5-7, 2023 - www.kamailioworld.com

1 1

Help with rtpengine_delete()
by Jose Figueroa 10 Jan '23

10 Jan '23

Hello everyone! I've been struggling with a kamailio scenario with the rtpengine_delete. My scenario is the following: I've setup a Kamailio multihomed, since some of my vendors has provided us a direct link using a different local subnet in eth2 and I have my public IP in eth1. The kamailio i've been working on is using app_lua module. SIP A <---------> 200.XXX.XXX.14 (eth1) [Kamailio 5.6] (eth2) 10.203.5.8 <------> Vendor 10.203.5.20 100.XXX.XXX.22 Basically, I receive a call from public IP eth1 and according to the logic from the vendor I forward statefully the call to 10.203.5.20 in second branch. I've been reading a lot of issues and documentation such as:[#840 rptengine], [#875 rtpengine] and [#2222 kamailio], but I don't really get working the rtpengine_delete() correctly, since I go to netstat -plan|grep rtpengine and I see some sessions still that are not freed. My second case is the following when I receive a 503 from another GW: SIP A <---------> 200.XXX.XXX.14 (eth1) [Kamailio 5.6] (eth1) 200.XXX.XXX.14 <-----------> Vendor GW 233.XXX.XXX.19 100.XXX.XXX.22 In that case I still see the rtpengine ports, mostly with my public IP 200.XXX.XXX.14 but some of them with the LAN 10.203.5.8 IP. Also, something curious I see on my 2nd use case is the following: https://pastebin.com/raw/B4vCgExX So, it would be great if someone can point me to the right direction, how and when I should use rtpengine_delete in order to finish the rtpengine sessions correctly and the ports can be freed up. Any help will be great! [840] https://github.com/sipwise/rtpengine/issues/840 [875] https://github.com/sipwise/rtpengine/issues/875 [2222] https://github.com/kamailio/kamailio/issues/2222 -- Regards, Jose Figueroa

3 2

Why do htable Keys have two colons?
by Noah Mehl 10 Jan '23

10 Jan '23

Hey everyone, Whenever I read documentation for htable usage, and other examples of other scripts in Kamailio, htable keys are typically named: something::something Examples are: $au::auth_count, $ci::srcip, join::$rU Why are there two colons (as opposed to a | )? Is this just a standard semantic thing in Kamailio? Is there something about that double character that’s unusual and easy to parse with SIP values? Or is it just what people do, and that’s a good choice to continue for all other Kamailio script writers to have understanding? Any insight would be appreciated. Thanks! ~Noah

3 6

Kamailio Crypto module and 3rd party openssl
by Arsenijs Kabihno 10 Jan '23

10 Jan '23

Hello, I am trying to make use of crypto module. The scenario is the following: 1. Encrypt plaintext passwords on kamailio side using crypto_aes_encrypt function of crypto module 2. Decrypt them outside of kamailio using 3rd party tools, such as PHP openssl_decrypt Crypto module parametrs are the following: modparam("crypto", "salt", "") modparam("crypto", "key_derivation", 0) If encryption and decription are handled by kamailio, the initial password matches the decrypted string (initial password -> encrypted string -> decrypted string) For example: sql_query("ds_dburl", "select secret from kamailio_sip_buddies where username='$au'", "secret"); $avp(secret_plain) = $dbr(secret=>[0,0]); //value: 'kamailio' crypto_aes_encrypt("$avp(secret_plain)", "YUZySHVtdlVTYjI0TGJNd3JTeVV0MlRaRWFraFNBRlM=", "$var(encrypted)"); //value: 'qfOqTMoJMgGAherGCqLRRQc4zTlqsEj3MEtcORurFf0=' crypto_aes_decrypt("$avp(secret_plain)", "YUZySHVtdlVTYjI0TGJNd3JTeVV0MlRaRWFraFNBRlM=", "$var(decrypted)"); //value: 'kamailio' But in case I try to decrypt the value of $var(encrypted) using PHP openssl_decrypt or online tool like https://www.devglan.com/online-tools/aes-encryption-decryption, I am getting the result 'kamailio' prepended by 16 random bytes, like: 6“¤›¿Ð+IÊ\ñžïZkamailio or 6��+I\��Zkamailio I believe this 16 bytes are actually random initialization vector in some encoding. Possibly kamailio is trimming them from result here: https://github.com/kamailio/kamailio/blob/master/src/modules/crypto/crypto_… Moreover, if secret was encrypted using crypto_aes_encrypt and random IV, you can use any IV while decrypting and get 16 different bytes+result Please advice if someone have used crypto module in similar way and what are the possible ways to acheive results consistency

2 5

pkg memory leak when acc module cdr_enabled
by Juha Heinanen 10 Jan '23

10 Jan '23

In latest stable K release, we noticed pkg memory leak (pgk memory usage increases by each processed call). It turned out that the leak goes away if acc module cdr_enable is not enabled. Could be a bug in dialog or acc module. Any debug instructions if the bug is not obvious? -- Juha

4 14

wrong char / bad PVE format
by Nathan Stratton 09 Jan '23

09 Jan '23

Trying to rename rtpengine files with: exec_msg("mv /var/spool/rtpengine/rtpengine-recording/$ci* /var/spool/rtpengine/rtpengine-recording/$ci.wav"); But get this error: Jan 06 13:59:19 proxy1 /usr/sbin/kamailio[2929]: ERROR: <core> [core/pvapi.c:924]: pv_parse_spec2(): error searching pvar "ci.wav" Jan 06 13:59:19 proxy1 /usr/sbin/kamailio[2929]: ERROR: <core> [core/pvapi.c:1127]: pv_parse_spec2(): wrong char [v/118] in [$ci.wav] at [6 (0)] Jan 06 13:59:19 proxy1 /usr/sbin/kamailio[2929]: ERROR: <core> [core/sr_module.c:1157]: fix_param(): bad PVE format: "mv /var/spool/rtpengine/rtpengine-recording/$ci* /var/spool/rtpengine/rtpengine-recording/$ci.wav" Jan 06 13:59:19 proxy1 /usr/sbin/kamailio[2929]: ERROR: <core> [core/mod_fix.c:564]: fixup_spve_null(): Cannot convert function parameter 1 to space Any ideas? ><> Nathan Stratton Founder, CTO Vocinity, Inc. <https://www.vocinity.com/gabbi>

3 2

RABBITMQ and AWS
by Fred Posner 06 Jan '23

06 Jan '23

Has anyone had any success connecting to RabbitMQ via a TLS 1.2 connection (such as the AWS MQ product)? Fred Posner https://pgpx.io

3 3

TypeError exception in Kemi with python3
by Michel Pelletier 06 Jan '23

06 Jan '23

Hello, I am using Kemi with Python3. I am getting a TypeError exception when using the following: KSR.presence.handle_subscribe() 40(208) INFO: PY3 {SUBSCRIBE}: app_python3 [apy_kemi.c:1839]: sr_apy_kemi_exec_func(): alert - action KSR.presence.handle_subscribe(...) took too long [2004761 ms] (file:(null) func:(null) line:733) 40(208) ERROR: PY3 {SUBSCRIBE}: app_python3 [python_support.c:156]: python_handle_exception(): apy_exec: ksr_request_route((null)): Unhandled exception in the Python code: TypeError: expected bytes, str found The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/etc/kamailio/kamailio.py", line 152, in ksr_request_route if self.ksr_route_presence(msg) == -255: File "/etc/kamailio/kamailio.py", line 733, in ksr_route_presence KSR.presence.handle_subscribe() SystemError: <built-in function handle_subscribe> returned a result with an error set Using the following appears to be a good workaround, as it does not exhibit the issue at all: KSR.presence.handle_subscribe_uri(KSR.pv.get("$fu")) Cheers, Michel Pelletier

1 0

2026

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 January 2023