Hi Saul,<br>It is indeed harmless. But the problem is I wish to keep my debug at 3 to be informed about some warnings and errors and this error in syslog just fills it up while I miss any important log messages. <br>Thanks for your reply and efforts.<br>
<br>--- Jayesh<br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi,<br>
<br>
On Nov 16, 2011, at 9:41 AM, Jayesh Nambiar wrote:<br>
<br>
> Hi All,<br>
> I am referring to the post pasted below:<br>
> <a href="http://lists.opensips.org/pipermail/users/2011-October/019440.html" target="_blank">http://lists.opensips.org/pipermail/users/2011-October/019440.html</a><br>
><br>
> Is there any suggested fix for this problem temporary or permanent since I faced the same problem when put into production on high load but could not reproduce the problem in the test environment. I would like to upgrade to 1.7 stable version to use some upgraded features but mediaproxy still remains a critical part of my configuration.<br>
><br>
> Thanks for any information on the topic above.<br>
><br>
<br>
I expect to have a fix ready shortly.<br>
<br>
Btw, does the bug affect the core functionality of your proxy? I was under the impression that the error was harmless, yet ugly.<br>
<br>
<br>
Regards,<br>
<br>
--<br>
Sa?l Ibarra Corretg?<br>
AG Projects<br>
<br></blockquote></div>