[OpenSIPS-Users] [RELEASE] OpenSIPS 2.2.7, 2.3.4 and 2.4.1 minor releases

Răzvan Crainea razvan at opensips.org
Thu May 17 09:10:19 EDT 2018


Perfect, thanks! You will get updates on the ticket when this is done.

On 05/17/2018 04:10 PM, Esty, Ryan wrote:
> Răzvan,
> 
> This is the in your tracking software https://github.com/OpenSIPS/opensips/issues/1364.
> 
> Ryan Esty
> Senior Software Engineer
> NEC Enterprise Communication Technologies (Cheshire)
> 203-718-6268
> 
> 
> -----Original Message-----
> From: Users [mailto:users-bounces at lists.opensips.org] On Behalf Of Razvan Crainea
> Sent: Thursday, May 17, 2018 9:00 AM
> To: users at lists.opensips.org
> Subject: Re: [OpenSIPS-Users] [RELEASE] OpenSIPS 2.2.7, 2.3.4 and 2.4.1 minor releases
> 
> Hi, Ryan!
> 
> I think you are right, rtcp-mux-require might not be accepted by the current code of rtpengine. Please open an issue on our ticketing system [1] to keep track of this issue as well.
> 
> [1] https://github.com/OpenSIPS/opensips/issues
> 
> Best regards,
> Răzvan
> 
> On 05/17/2018 03:27 PM, Esty, Ryan wrote:
>> Bogdan-Andrei,
>>
>> I was going to look into this a little more before reporting it but I'm having issues trying to get rtcp-mux-require to be sent down to rtpengine. From what I can tell I need this to work with chrome's webrtc. Since this is crunch time I didn't want a potential bug not being covered. I'm using 2.3.3 and it could be that rtcp-mux-require isn't part of that version. From what I can tell so far if I put in rtcp-mux-require rtpengine kicks it back. When I do a rtcp-mux=require rtpengine doesn't complain but the latter doesn't match the documentation nor do I think works.
>>
>> Ryan Esty
>>
>> -----Original Message-----
>> From: Users [mailto:users-bounces at lists.opensips.org] On Behalf Of
>> Bogdan-Andrei Iancu
>> Sent: Thursday, May 17, 2018 6:40 AM
>> To: users at lists.opensips.org; developensips <Devel at lists.opensips.org>
>> Subject: [OpenSIPS-Users] [RELEASE] OpenSIPS 2.2.7, 2.3.4 and 2.4.1
>> minor releases
>>
>> Greetings!
>>
>> A new cycle is about to be complete: OpenSIPS is tortured all over the worlds; this produces feedback and reports; and this translates into more fix, in a better stability of the released OpenSIPS versions.
>>
>> Shortly, it's time for a new set of minor releases, to officially
>> incorporate all the fixes in the last months/weeks: OpenSIPS 2.2.7,
>> 2.3.4 and 2.4.1
>>
>> The new releases are due next week, on Wednesday, May 24th 2018.
>>
>> If you have any pending GitHub issues/mailing list bug threads concerning the mentioned branches, this would be a good time to bump them!
>>
>> Thank you for your contributions to this project!
>>
>> Best regards,
>>
>> --
>> Bogdan-Andrei Iancu
>>
>> OpenSIPS Founder and Developer
>>      http://www.opensips-solutions.com
>> OpenSIPS Summit 2018
>>      http://www.opensips.org/events/Summit-2018Amsterdam
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
> 
> --
> Răzvan Crainea
> OpenSIPS Core Developer
>     http://www.opensips-solutions.com
> 
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> 

-- 
Răzvan Crainea
OpenSIPS Core Developer
   http://www.opensips-solutions.com



More information about the Users mailing list