<span style="font-family: Arial, Helvetica, sans-serif; font-size: 10pt">I am trying to get Broadvox to do a live call trap with me so we can see what asterisk is sending out that they don't like. Does anyone have any idea of setttings I could try while I have them working with me that would bring the DTMF back in line with the 1.6.2.11 build. <br />
<br />
<div id="divSignature"></div>
<span style="font-family: arial, helvetica, sans-serif; font-size: 10pt;">Also note: We have reproduced this with Grandstream GXP, SNOM and Linksys phones. Our Unidata WPU-7700 test phone seems to work. This is the exact same behavior as what we had under 1.6.1.20<br />
<div id="divSignature"></div>
<br />
<span style="font-family: arial, helvetica, sans-serif; font-size: 10pt;">Hi all.<br />
<br />
I moved to asterisk version 1.6.2.11 to fix an issue that 1.6.1.20 had with properly sending in-call rfc2833 DTMF with Level 3 and Broadvox. 1.6.2.11 worked grate with the DTMF but I needed the call pickup fix in 1.6.2.12-rc1. Now the in-call DTMF issues is back. What changed between these version with DTMF handling that would cause issues. What we are seeing is that when you dial 22 we are only getting a single 2 and some times other keys are lost as well. This did not happen with 1.6.2.11.<br />
<br />
Any ideas?<br />
Bryant<br />
</span><br />
</span><br /></span>