<html><head></head><body style="zoom: 0%;"><div dir="auto">FYI we are running other servers with thé samedi setup but codec configuration is !all, alaw and alaw on provider side -eg no g722 involved- and they don' t show those notices</div>
<div class="gmail_quote" >Le 8 janv. 2024, à 19:30, Jonas Smedegaard <<a href="mailto:jonas@jones.dk" target="_blank">jonas@jones.dk</a>> a écrit:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="blue">Hi Daniel,<br><br>Quoting Daniel via Pkg-voip-maintainers (2024-01-08 16:22:19)<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"> after upgrading from Debian11/asterisk 18.20.2 compiled from source to Debian12/Asterisk 20.5.2 from unstable, we receive lots of NOTICE logs like<br> <br> [2024-01-08 11:35:31] NOTICE[58221][C-0000028a]: translate.c:603 ast_translate: 18182 lost frame(s) 48240/30057 (alaw@8000)->(ulaw@8000)<br> [2024-01-08 11:35:31] NOTICE[58710][C-00000298]: translate.c:603 ast_translate: 1253 lost frame(s) 1254/0 (slin@16000)->(slin@8000)->(alaw@8000)<br> <br> doesn't matter IAX2 or PJSIP endpoints. We are surprised to see such notice between alaw & ulaw. Codecs used for PJSIP and IAX customers EP are<br> !all,g722,ulaw,alaw and for providers !all,ulaw,alaw<br> <br> We checked translation and tried by adding slin,slin16 on both sides, no changes. On 18.20.2 we didn't have this behaviour.<br> <br> Answer we get from asterisk community list "If you’re using the Debian package, then that includes patches which are not present in Asterisk mainline.<br> Those log messages, and some codec translation behavior, is from one of those patches."<br></blockquote><br>Thanks for your bugreport.<br><br>It is true that Debian-distributed Asterisk includes patches which may<br>indeed affect the above. But only possibly, not certainly.<br><br>If it is possible for you to try test your setup with<br>upstream-distributed Asterisk, then it would help ensure that truly what<br>you experience is a bug introduced by a Debian patch.<br><br><br> - Jonas<br></pre></blockquote></div></body></html>