Re: [SR-Users] Steps to next major release v4.1.0

2013-11-14 Thread Daniel-Constantin Mierla
Hello, again a short notice before happening, as nobody proposed alternatives, I am going to create the dedicated branch for release series 4.1 later today. Cheers, Daniel On 11/12/13 9:18 PM, Daniel-Constantin Mierla wrote: Hello, I am planning to make the branch for 4.1 on Thursday. Afte

Re: [SR-Users] Steps to next major release v4.1.0

2013-11-12 Thread Peter Dunkley
The missing features are: - Ability to handle indeterminately large incoming MSRP SEND requests and use TCP windowing for MSRP congestion control (so not using the fixed size TCP receive buffers currently in Kamailio). The way to do this is for Kamailio to chunk the large incoming MSR

Re: [SR-Users] Steps to next major release v4.1.0

2013-11-12 Thread Daniel-Constantin Mierla
Mohammed, perhaps a better approach is to ask what missing feature are you looking for. IIRC, the open part was related to delivery of reports. But msrp module is ready for usage since couple of releases ago. Cheers, Daniel On 11/12/13 11:00 PM, Peter Dunkley wrote: No. There has been no d

Re: [SR-Users] Steps to next major release v4.1.0

2013-11-12 Thread Peter Dunkley
No. There has been no development done on this module for several months. I can't speak for any of the other developers, but I don't have any plans to work on this unless there is a specific demand for it from a customer. Regards, Peter On 12 November 2013 21:40, mohammed alyaseen wrote: >

Re: [SR-Users] Steps to next major release v4.1.0

2013-11-12 Thread mohammed alyaseen
Hello,  Is the new release 4.1.0 with completed MSRP module? thanks, Medo Daniel-Constantin Mierla schrieb am 21:39 Dienstag, 12.November 2013: Hello, I am planning to make the branch for 4.1 on Thursday. Afterwards, the master can get code for new features and fixes will have to be ba

Re: [SR-Users] Steps to next major release v4.1.0

2013-11-12 Thread Daniel-Constantin Mierla
Hello, I am planning to make the branch for 4.1 on Thursday. Afterwards, the master can get code for new features and fixes will have to be backported from master to 4.1 branch (and older, when it is the case). If anyone is considering alternatives, then reply here with the options. Cheers,

[SR-Users] Steps to next major release v4.1.0

2013-11-07 Thread Daniel-Constantin Mierla
Hello, it's now one month since we froze the development for release of v4.1.0. No critical issues in on the table for this particular version, so perhaps next week is time to create a dedicated branch for it, to be named in GIT as 4.1, and open development for v4.2. If all goes fine for one