Re: [asterisk-dev] Memory leak since Asterisk 16.5.x / pjsip

2019-09-16 Thread Michael Maier
Am 16.09.19 um 20:19 schrieb Kevin Harwell: Actually can you create a new issue for this on the issue tracker. As well included the following: Has anything else changed? For instance was openssl upgraded between then too? > Speaking of which, what version of openssl is installed? As well what

Re: [asterisk-dev] Memory leak since Asterisk 16.5.x / pjsip

2019-09-16 Thread Corey Farrell
Updating pjproject does take less time/effort than maintaining a fork for the many years of an LTS release.  That reduced effort isn't just free time to developers, the time is instead spent working on enhancements and bug fixes.  Maintaining a fork would prevent users from getting important

Re: [asterisk-dev] Memory leak since Asterisk 16.5.x / pjsip

2019-09-16 Thread Kevin Harwell
Actually can you create a new issue for this on the issue tracker. As well included the following: Has anything else changed? For instance was openssl upgraded between then too? Speaking of which, what version of openssl is installed? As well what OS, and version? I assume before downgrading

Re: [asterisk-dev] pjsip asterisk 13.24: sips / srtp and Deutsche Telekom doesn't work because of missing mediasec parameters

2019-09-16 Thread Michael Maier
On 02.09.19 at 19:03 Michael Maier wrote: > On 30.05.19 at 10:24 Michael Maier wrote: >> Hello! >> >> I wrote some code, which adds basic media encryption support to be used with >> Deutsche Telekom. The attached patch is based on Asterisk 16.3 >> and works for me :-) - not fully tested yet. If

Re: [asterisk-dev] Memory leak since Asterisk 16.5.x / pjsip

2019-09-16 Thread Sylvain Boily
Le lun. 16 sept. 2019 13 h 07, Michael Maier a écrit : > On 15.09.19 at 21:19 Joshua C. Colp wrote: > > On Sun, Sep 15, 2019, at 2:21 AM, Michael Maier wrote: > > >> BTW: I'm not really happy with the fact, that an existing LTS / stable > version gets a new pjsip version "on the fly". From my

Re: [asterisk-dev] Memory leak since Asterisk 16.5.x / pjsip

2019-09-16 Thread Michael Maier
On 15.09.19 at 21:19 Joshua C. Colp wrote: > On Sun, Sep 15, 2019, at 2:21 AM, Michael Maier wrote: >> BTW: I'm not really happy with the fact, that an existing LTS / stable >> version gets a new pjsip version "on the fly". From my point of view, this >> should have been >> done during a normal

Re: [asterisk-dev] Memory leak since Asterisk 16.5.x / pjsip

2019-09-16 Thread Matt Fredrickson
On Mon, Sep 16, 2019 at 12:39 PM Andreas Wehrmann wrote: > > > >> BTW: I'm not really happy with the fact, that an existing LTS / stable > >> version gets a new pjsip version "on the fly". From my point of view, > >> this should have been done > >> during a normal development cycle and not during

Re: [asterisk-dev] Memory leak since Asterisk 16.5.x / pjsip

2019-09-16 Thread Andreas Wehrmann
BTW: I'm not really happy with the fact, that an existing LTS / stable version gets a new pjsip version "on the fly". From my point of view, this should have been done during a normal development cycle and not during a stable phase. Since support for bundled PJSIP we've actively tried to keep