<br><br><div class="gmail_quote">On Mon, May 2, 2011 at 1:14 PM, Eric Beard <span dir="ltr"><<a href="mailto:eric@loopfx.com">eric@loopfx.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div lang="EN-US" link="blue" vlink="purple"><div><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">So, we finally figured this out. The NIC in that machine is faulty. We switched over from the add-in Intel NIC (which runs flawlessly for us in dozens of other machines) to the cheap onboard NIC and everything runs great. I hate it when things are just sort of broken, and not completely broken – makes it hard to see where the problem really is.</span></p>
</div></div></blockquote><div><br></div><div>Thanks for the followup. This is a great example of a "problem with FreeSWITCH" that really isn't a problem with FreeSWITCH. :) I think I will bookmark this thread for future reference for when someone says, "I'd like to report a bug in FreeSWITCH..." This is also validation of the rule of thumb we have for people who have FS in production: HAVE A SPARE MACHINE FOR TESTING!!! </div>
<div><br></div><div>Nice work, Eric. Keep on FreeSWITCHin'!</div><div>-MC</div></div>