New Post on freeswitch.org from Kathleen<br>
check it out at http://ift.tt/19qOGWv<br>
FreeSWITCH Week in Review (Master Branch) March 21st-27th<br><p>Hello, again. This passed week in the FreeSWITCH master branch we had 18 commits. The features for this week include: support for mute in mod_verto and support for filtering on file:func to mod_logfile mapping.</p>
<p>Join us on Wednesdays at 12:00 CT for some more FreeSWITCH fun! And head over to <a href="https://freeswitch.com/">freeswitch.com</a> to learn more about FreeSWITCH support.</p>
<p>New features that were added:</p>
<ul>
<li>
<a href="http://ift.tt/19qOGWz">FS-7401</a> Add support for mute in mod_verto</li>
<li>
<a href="http://ift.tt/1DlAwDQ">FS-7402</a> Add support for filtering on file:func to mod_logfile mapping</li>
</ul><p>Improvements in build system, cross platform support, and packaging:</p>
<ul>
<li>
<a href="http://ift.tt/19qOJBv">FS-7383</a> Fixed a memory leak causing building Freeswitch with clang AddressSanitizer enabled to fail</li>
<li>
<a href="http://ift.tt/1Gl1nRp">FS-7149</a> The Windows portion of the update to use flite-2.0.0-release</li>
</ul><p>The following bugs were squashed:</p>
<ul>
<li>
<a href="http://ift.tt/1Gep0Hk">FS-7300</a> Fixed mod_rayo to properly handle errors in mod_unimrcp</li>
<li>
<a href="http://ift.tt/1DlAz2d">FS-7385</a> Fixed a segfault caused by an invalid contact URI and instead fail the call with 502 bad gateway if the outbound leg returns a redirect with an invalid URI.</li>
<li>
<a href="http://ift.tt/1yzQC5V">FS-6954</a> Detect when we have T.38 in nomedia or proxy media mode and apply same fixups as in media mode.</li>
<li>
<a href="http://ift.tt/19qOJBD">FS-7391</a> Corrected currency for mod_say_de it&rsquo;s now &ldquo;Ein Euro und Ein Cent&rdquo; rather than &ldquo;Eins Euro und Eins Cent&rdquo;</li>
<li>
<a href="http://ift.tt/1DlAz2h">FS-7396</a> Fix for WebRTC call setup hang when Chrome 42 includes IPv6 ICE candidate</li>
<li>
<a href="http://ift.tt/19qOJBG">FS-7386</a> Allows auto-adjust to fix media endpoints after receiving a 183 then a 200 from a different media endpoint, like in the case of proxy forking scenarios</li>
</ul><br>