<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Thanks.</p>
<p> I think we assumed the CERT branch was more in line with how the
RHEL Kernel was maintained, where any major bugs were backported,
but new features weren't added. Thanks for your clarification
that this branch is really just maintained "as requested by
commercial customers".<br>
</p>
<p>We'll be switching back to the mainline Asterisk 16 branch. <br>
</p>
<p><br>
</p>
<p>On Mon, Oct 4, 2021 at 8:02 PM Kevin Harwell <kharwell at
sangoma.com> wrote:<br>
</p>
<p>> On Mon, Oct 4, 2021 at 4:36 PM Steve Sether <ssether at
usinternet.com><br>
> wrote:<br>
><br>
>><br>
>> We're running Asterisk certified/16.8-cert5<br>
>><br>
>> I looked through the changelog for the cert versions 6 -
11, but didn't<br>
>> see this fix ported to this branch. Did I miss
something, or has this fix<br>
>> just not been back-ported yet?<br>
>><br>
> You did not miss anything. The patch for that issue is not in
Certified<br>
> Asterisk 16.8, cert5 or even cert11 (currently released
version).<br>
><br>
<br>
And to provide clarification, it won't be backported unless a
commercial<br>
customer requests it or encounters the specific issue. If you are
a<br>
commercial customer you would need to contact Sangoma support and
go<br>
through the normal process to have it done. If you are not then
you would<br>
need to either switch away from certified, or backport the change
yourself.<br>
</p>
<div class="moz-signature">-- <br>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>