[SR-Users] Re: rtpproxy -- timeout_socket

Hey James, Thanks for your interest! Indeed this functionality is somewhat broken (in the module), not very well documented and some of the documentation is not actually correct, so let me explain some basics: 1. The rtpproxy notification mechanism is rather low-level, it has no notion of

[SR-Users] Re: extreme dildoes

 you never know! On Sat, Aug 26, 2023, 7:13 AM Giovanni Maruzzelli wrote: > On Sat, Aug 26, 2023 at 1:23 PM Julien Chavanton > wrote: > >> Are you trying to connect them over SIP ? >> >> > :D > > -- > Sincerely, > > Giovanni Maruzzelli > OpenTelecom.IT > cell: +39 347 266 56 18 > >

[SR-Users] Re: RTC/Kamailio dinner at Fosdem 2023

t does > not look good if reserved tables are empty. Can you come at that time? > > Daniel > On 17.01.23 06:57, Maxim Sobolev wrote: > > I will be interested, potentially together with Giovanni Maruzzelli. > Assuming we arrive in town early enough for that. Thanks for organizing!!!

[SR-Users] Re: RTC/Kamailio dinner at Fosdem 2023

I will be interested, potentially together with Giovanni Maruzzelli. Assuming we arrive in town early enough for that. Thanks for organizing!!! -Max On Mon, Jan 9, 2023, 8:32 AM Daniel-Constantin Mierla wrote: > Hello, > > Fosdem 2023 returns to Brussels, Belgium, for a physical event and I'm

[SR-Users] Re: Dockerized VoIP Stack

"up to 91%". -Max P.S. We are usually running off master. ;-) On Thu, Dec 22, 2022 at 9:25 AM Maxim Sobolev wrote: > That is certainly not true or inaccurate. The RTPProxy is quite a mature > package, so we don't have to release it every few months. Instead I am > focusin

[SR-Users] Re: Dockerized VoIP Stack

y want also use transcoding or > advanced en/decryption which rtpengine offers. > > Cheers, > > Henning > > Cheers, > > Henning > > -- > *Von:* Maxim Sobolev > *Gesendet:* Donnerstag, 22. Dezember 2022, 19:49 > *An:* Kamailio (SER) -

[SR-Users] Re: Dockerized VoIP Stack

Terrance, Both are actively maintained & developed with a slightly different focus. Speaking of k8s in particular you might want to check presentation done by Liviu Chircu at the last OpenSIPS summit here: https://youtu.be/JwO0UmauuT4?t=13034 Most of the stuff he talked about would apply to

Re: [SR-Users] Let's Encrypt DST Root CA X3 cert CA expiration 30th/Sept - Any issues?

Some of our internal API have started to fail and most of software update routines jammed up as a result until we figured out how to cope with that issue. Not the first one and certainly not the last. In general PKI/TLS is by design prone to issues like this and I am sad industry has not come up

Re: [SR-Users] Kamailio vulnerable to header smuggling possible due to bypass of remove_hf

wrote: > > Hello Maxim, > > have a look to the first sentence: > > “A security vulnerability is (for example) when a user of Kamailio can > cause Kamailio to crash or lock up by sending messages to the server > process.” > > So there is some limitation regarding vuln

Re: [SR-Users] REST API to initiate a call in Kamailio

Ameed, you might be interested to look at Jambonz, which runs in node and is very HTTPS-friendly. Kind-of HTTP-to-SIP B2BUA. There are few presentations Dave Horton done on YouTube about it recently. He is very nice guy also has some mailings lists where you can ask questions like this. Good luck!

Re: [SR-Users] Kamailio vulnerable to header smuggling possible due to bypass of remove_hf

mailio to crash or lock up by sending messages to the server > process.” > > > > So there is some limitation regarding vulnerability criticality defined in > there. But of course (as I already mentioned), it might be improved to e.g. > use CVSS scoring instead. > > >

Re: [SR-Users] Kamailio vulnerable to header smuggling possible due to bypass of remove_hf

On Wed, Sep 2, 2020 at 11:30 AM Henning Westerholt wrote: > Hello Maxim, > > > > thank you for the clarification, appreciated. > No worries, hope to have a civilized discussion. > Just one clarification, my comment regarding the advisory from 2018 was > not meant as advertisement etc.. >

Re: [SR-Users] Kamailio vulnerable to header smuggling possible due to bypass of remove_hf

Hey Daniel, Henning, Tao, Thanks for commenting out. There are a lot of opinions for me to address individually, so I will just clarify my opinion. The only substantial difference I think is whether the issue at hand warrants a security advisory to be issued by the Kamailio project or not. I

Re: [SR-Users] Kamailio vulnerable to header smuggling possible due to bypass of remove_hf

Thanks Daniel for patching up the bug, however I think you are downplaying severity of the problem at hand. You see, from the point of view of outside world, kamailio is not just engine and default config. All APIs that are provided are also part of the product, especially those "core" ones. As

Re: [SR-Users] MD5 and SHA-256 instead of MD5 or SHA-256...

On Thu, Jun 18, 2020 at 1:42 AM Olle E. Johansson wrote: > > > On 17 Jun 2020, at 17:22, Maxim Sobolev wrote: > > Whoever works on this needs to consider two things I think: > > - ability to select algorithms when challenging UAC (MD5-only, > SHA256-only, SHA-512/25

Re: [SR-Users] MD5 and SHA-256 instead of MD5 or SHA-256...

Whoever works on this needs to consider two things I think: - ability to select algorithms when challenging UAC (MD5-only, SHA256-only, SHA-512/256-only, all permutations). The RFC allows UAS to include multiple HFs(*). MD5-only should probably be the default. I suspect there might be a

[SR-Users] Join us for SIP Chronicles Live #1, featuring Giovanni Maruzelli

Dear Real-Time Friends and Colleagues! As many of you we have been totally devastated that we will have no chance to see you in the next few months to come. :-/ Some people in the community believe it might be years. I don’t necessarily agree with that opinion myself. Over the course of the

Re: [SR-Users] FreeBSD Kamailio pkg

This question has to be directed to maintainer of the kamailio package in FreeBSD, as the Kamailio project has no oversight or control over what's being decided on that end WRT it's defaults. -Max On Wed, Dec 12, 2018, 1:36 PM Sergiu Pojoga Did anyone notice that when installing Kamailio from

Re: [SR-Users] Touching Base / Question

9a80b54d47eaabef6f25d7b2f0659e7 > > There is 5 values but I'm not sure what they represent. I've also asked > Daniel so you may be hearing for him as well. > > On Sep 29, 2017 3:51 PM, "Maxim Sobolev" <sobo...@sippysoft.com> wrote: > >> Hi, Michael,

Re: [SR-Users] rtpproxy rtp timeout

Android > вторник, 22 августа 2017г., 08:02 +03:00 от Maxim Sobolev > sobo...@sippysoft.com: > > Hi. 2.1 is the version we recommend using. > > -Max > > On Aug 21, 2017 1:22 PM, <y...@yu-boot.ru> wrote: > > Hello. > > What version of rtpproxy app should be use

Re: [SR-Users] rtpproxy rtp timeout

Hi. 2.1 is the version we recommend using. -Max On Aug 21, 2017 1:22 PM, wrote: > Hello. > > What version of rtpproxy app should be used for this feature to work with > Kami? How to use it correctly? > > -- > Отправлено из myMail для Android > >

Re: [SR-Users] RTPProxy - lookup request failed

Yes, Daniel is correct you can bump overall timeout with the -T option. There is also another option -W now since 3 years ago (2.0+) to set timeout specifically on early sessions, so that you can have bigger timeout during call setup phase which might be relevant in this case. Hope it helps. -Max

Re: [SR-Users] Can rtpproxy stream audio inside a call?

Daniel is right. Technically speaking it can be done at any point after the media session has been established, but you need some kind of trigger to start/stop it from your routing script. Such as re-INVITE for example. -Max On May 8, 2017 7:52 AM, "Daniel-Constantin Mierla"