Re: [OpenSIPS-Users] Segfault in 3.2.2 (inc nightly) but not 3.2 in mid_registrar

2021-09-28 Thread Andrew Yager
No worries; glad the detective work born out of frustration helped ;) (and thanks to my colleague Mark V who is lurking around here for his work in getting to this point!) We’ll give it a test in the next nightly build! A From: Liviu Chircu Sent: Tuesday,

Re: [OpenSIPS-Users] Segfault in 3.2.2 (inc nightly) but not 3.2 in mid_registrar

2021-09-28 Thread Liviu Chircu
On 28.09.2021 14:29, Liviu Chircu wrote: Will put up a fix soon, thanks again for the nice hint! Done, see: https://github.com/OpenSIPS/opensips/commit/6765b7d95b99626ca81986561f3d7851b3e90c8f -- Liviu Chircu www.twitter.com/liviuchircu | www.opensips-solutions.com

Re: [OpenSIPS-Users] Segfault in 3.2.2 (inc nightly) but not 3.2 in mid_registrar

2021-09-28 Thread Liviu Chircu
On 28.09.2021 14:00, Andrew Yager wrote: Just further to this, I'm pretty sure this is a regression introduced in https://github.com/OpenSIPS/opensips/commit/c11f92698c6f345d8921d645177f71aa36c9791d . Haha,

Re: [OpenSIPS-Users] Segfault in 3.2.2 (inc nightly) but not 3.2 in mid_registrar

2021-09-28 Thread Andrew Yager
Just further to this, I'm pretty sure this is a regression introduced in https://github.com/OpenSIPS/opensips/commit/c11f92698c6f345d8921d645177f71aa36c9791d . On Tue, 28 Sept 2021 at 19:04, Andrew Yager wrote: > Hi, > > Since testing 3.2.2 we've noticed a segfault affecting registrations >

[OpenSIPS-Users] Segfault in 3.2.2 (inc nightly) but not 3.2 in mid_registrar

2021-09-28 Thread Andrew Yager
Hi, Since testing 3.2.2 we've noticed a segfault affecting registrations pretty regularly through mid_registrar. The issue occurs intermittently, but seemingly when the contact doesn't exist and needs to be created. We are currently using in-memory mid_registrar without DB backing to test;

[OpenSIPS-Users] Mid-registrar with AOR throttling - clearing registration

2021-09-28 Thread Mark Allen
We have a mid-registrar (OpenSIPS 3.1) in front of an Asterisk node. Mid-registrar saves with the 'memory only' flag. We are using AOR throttling We've had a few occasions where something has gone wrong with the registration on Asterisk so that Asterisk thinks an extension is no longer