<div>On Tue, Dec 22, 2009 at 10:17 PM, Rafael Prado Rocchi <span dir="ltr"><<a href="mailto:prado@practis.com.br">prado@practis.com.br</a>></span> wrote:</div><div><div class="gmail_quote"><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="color:#262626">Moy,</span></p>
<p class="MsoNormal"><span style="color:#262626">I am doing a lot of testing on
the polling bug. Your latest revision (235811) fixed it apparently, but it
introduced a new bug.</span></p>
<p class="MsoNormal"><span style="color:#262626"> </span></p></div></div></blockquote></div><div><div>Hello Rafael, thanks a lot for testing, I committed but did not test myself yet :)</div><div><br></div><div>How easily can you reproduce the problem? you say "after a few R2 calls", can you try to put up a more detailed description? You loop 2 ports and then what, originate calls using manager or asterisk call files? once the call goes out in port 1 and comes in port 2, what do you do? send to echo() application? for how long? who hangs up the call and how?</div>
<div><br></div></div>-- <br>Moises Silva<br>Senior Software Engineer<br>Sangoma Technologies Inc. | 50 McIntosh Drive, Suite 120, Markham ON L3R 9T3 Canada<br>t. 1 905 474 1990 x 128 | e. <a href="mailto:moy@sangoma.com">moy@sangoma.com</a><br>
</div>