Hello Vanesa,<div><br></div><div><div class="gmail_quote">On Fri, Dec 11, 2009 at 11:41 AM, vanesa estrada <span dir="ltr"><<a href="mailto:lady_vane69@hotmail.com" target="_blank">lady_vane69@hotmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
They said its R2, i looked my old pbx config and i saw these coments by the person that used to give us support, i dont know if this help</div></blockquote></div><div><br></div><div>It certainly helps, at least helps me :-)</div>
<div><br></div><div>The problem is that at that point, openr2 does not expect more MF tones, but still we get an F tone, may be is the progress tone sent by the telco immediately which openr2 may miss detect as an F.</div>
<div><br></div><div>I created a code branch to try to get your telco working. I committed a small fix. Please try this branch:</div><div><br></div><div>svn co <a href="http://openr2.googlecode.com/svn/branches/release-1-bestel">http://openr2.googlecode.com/svn/branches/release-1-bestel</a></div>
<div><br></div><div>Recompile, re-install openr2 and try again. Be sure to re-configure and re-install Asterisk (if testing with Asterisk).</div><div><br></div><div>The r2test application is mostly for development and debugging when the Asterisk code is not stable, but at this point I feel very confident about the R2 Asterisk code so you may want to try to test with Asterisk if that is easier for you. Besides, Asterisk has enabled more R2 features that r2test (which has fallen a bit outdated), for example, call files may or may not work well on r2test, try Asterisk enabling mfcr2_call_files=yes and mfcr2_logdir=bestel, then you will find protocol dump files for each incoming or outgoing call in /var/log/asterisk/mfcr2/bestel</div>
<br>-- <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" target="_blank">moy@sangoma.com</a><br>
</div>