Hi Saul, 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 might miss any important log messages. Thanks for your reply and efforts.
--- Jayesh Hi, >**>* On Nov 16, 2011, at 9:41 AM, Jayesh Nambiar wrote:*>**>* > Hi All,*>* > I >am referring to the post pasted below:*>* > >http://lists.opensips.org/pipermail/users/2011-October/019440.html*>* >*>* > >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.*>* >*>* > Thanks for any >information on the topic above.*>* >*>**>* I expect to have a fix ready >shortly.*>**>* Btw, does the bug affect the core functionality of your proxy? >I was under*>* the impression that the error was harmless, yet ugly.*>**>**>* >Regards,*>**>* --*>* Sa?l Ibarra Corretg?*>* AG Projects*>**>
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
