<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">if it is inband dtmf and you don't turn on the dtmf detector, we wont look for or touch the tones.<div><br></div><div><br><div><div>On Aug 16, 2010, at 8:56 AM, Dennis wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>phillip, it seems that we have somehow the same problem, but we have<br>an additional strange behavior.<br><br>we used wireshark on the incoming network-card and on the outgoing<br>side. there we see two strange things, we can not figure out:<br><br>1.) on the incoming side, we receive the in-band tone from the cirpack<br>with a tiny gap, but fs recognizes them as 2 tones.<br>in wireshark it look something like this: | ||||||||<br>as i said, fs sees this as two tones.<br><br>2.) fs sends the tone above to the outgoing side as two tones, but<br>seems to cut the first ms of the second part.<br>in wireshark it looks something like this: | |||<br><br><br>i feel, that we have to find out the following:<br><br>1.) why does the tone already have a gap, when we receive it?<br><br>2.) why does fs not leave the tone untouched? something happens with<br>the tone, while passing fs. is there a setting to avoid this?<br><br>3.) why is there no easy way to completely delete dtmf tones, if it is<br>possible with vuvuzela-noise? ;-)<br><font class="Apple-style-span" color="#000000"><font class="Apple-style-span" color="#144FAE"><br></font></font></div></blockquote></div></div></body></html>