Hi guys.
I want to firstly extremely apologize on behalf of Sangoma Technologies, Inc for this issue then point out what happened and finally let you know how we are going to resolve it.
Firstly this issue is related to https://issues.freepbx.org/browse/FREEPBX-15009 which is in turn related to https://issues.freepbx.org/browse/FREEPBX-14735.
Secondly what you need to know is how our QA process currently works. That is everything is merged into a single release. Our QA team then goes through and “passes” tickets by testing modules, sometimes this means there are several “fixes” or “features” in a single release. This has the potential to cause issues (as you’ve now seen).
On that a bug slipped in from 14735 which was reported in 15009 and then fixed in that ticket. However the tickets below 15009 ended up getting QA passed (because their testing was not related to this issue, however because everything is merged together the buggy code got in there) and thus merged into the code base which 15009 stayed in edge which the audio fix. We have now published 15009 as stable. This bug specifically dealt with audio addressing on PJSIP only, which broke because Asterisk does not support a media_address setting of 0.0.0.0. The fix was issued in this commit: https://github.com/FreePBX/core/commit/b5eb0cf0a2bfec10cd6775d29be37edfc5353767 which was in Core 13.0.120.3 in edge only.
So how are we going to fix this? Well we have started a new QA process as of two weeks ago (though not fully implemented) which tests each bug fix or feature request as a separate entity. This means that the QA team will be checking 1 single issue instead of a mass of issues at one time. The code they are checking won’t merge until they QA pass it. So the buggy code wouldn’t have even made it into the edge release until they pass it through.
Thank you all for you patience and understanding. I understand how frustrating this has been and perhaps our your faith in upgrading has been tainted a bit, but understand that we are trying to make this a better process.
Summary: Update to Core 13.0.120.3 which will resolve your issues.
-Andrew
Sangoma Technologies, Inc