<div><div class="gmail_quote">On Wed, Dec 28, 2011 at 4:29 PM, Kevin P. Fleming <span dir="ltr"><<a href="mailto:kpfleming@digium.com" target="_blank">kpfleming@digium.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>On 12/28/2011 03:20 PM, Bruce B wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi everyone,<br>
<br>
Can this bug be fixed? Apparently the offending code is what is<br>
mentioned below by Danny Nicholas.<br>
</blockquote>
<br></div>
This is incorrect. The code posted below is what generates the warning message, but it (correctly) generates the message when a frame is written to a channel in a format that the channel is not expecting.<br>
<br>
Something is causing these frames to be sent; that is the real cause of this bug. Other than the warning messages, though, I haven't seen anyone report an actual *problem* (one-way audio, no audio, bad audio, etc.). If the only problem is some annoying warning messages, and calls are otherwise successful, this is not going to be a high priority to get fixed.<br>
<br></blockquote>It's filling up the logs for sure leading to much confusion while looking through. Each call generates like 100 lines of this error. I have seen some BUSY calls and assuming it's the same problem but I can't confirm yet. <br>
<br><div>Regards, </div></div>
</div>