Hello,

iirc, not yet in 4.0, but it will. Doing it for 3.3 has to be analyzed, not sure if would be just simple backport and then it might be better just to upgrade to 4.0 instead of making 3.3 unstable.

Cheers, Daniel

On 8/2/13 10:27 AM, Charles Chance wrote:

Hi Daniel,

Sorry if I missed it already, but did the fix to clear early state dialogs get backported in the end?

Cheers,

Charles

On 2 Aug 2013 09:17, "Daniel-Constantin Mierla" <miconda@gmail.com mailto:miconda@gmail.com> wrote:

Hello,

I am considering to package soon a new version out of branch 3.3.
If anyone has spotted fixes that should be backported to that
branch, reply here. I'm not sure yet of an exact date, but should
be rather soon, being just a patch update.

A new release out of branch 4.0 will be done short after this one.

Cheers,
Daniel

-- 
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda <http://twitter.com/#%21/miconda> -
http://www.linkedin.com/in/miconda


_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
list
sr-users@lists.sip-router.org <mailto:sr-users@lists.sip-router.org>
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

www.sipcentric.com http://www.sipcentric.com/

Follow us on twitter @sipcentric http://twitter.com/sipcentric

Sipcentric Ltd. Company registered in England & Wales no. 7365592. Registered office: Unit 10 iBIC, Birmingham Science Park, Holt Court South, Birmingham B7 4EJ.

Am Freitag, 2. August 2013, 10:42:54 schrieb Daniel-Constantin Mierla:

...

there was a request to set branch = 0 (syn_branches stuff..) as default because there were some errors. This was fixed from me in master in commit 6287caecc. I was not sure if this is the right kind of fix in a stable branches, as it changes default behaviour. What do you think?

I think is not necessary because there is the option to set it 0 via config parameter. Changing the default behavior might get troubles to those just looking for a smooth update. Those that already had troubles, they most probably fixed already with the config option.

Hi Daniel,

I was thinking about people that might not know about this issue and this parameter. But you're right, this was only reported a few times on the list in the time after this change has been done, so better not break something for people. In the new version released from master it will be correct then.

Henning