<br><br><div class="gmail_quote">On Mon, Aug 16, 2010 at 5:56 AM, Dennis <span dir="ltr"><<a href="mailto:odermann@googlemail.com">odermann@googlemail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
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></blockquote><div>That would probably be better answered by looking at the sending side. I would capture the packets leaving the sending side to see what they look like. <br>
<br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<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? </blockquote><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
3.) why is there no easy way to completely delete dtmf tones, if it is<br>
possible with vuvuzela-noise? ;-)<br></blockquote><div>I'll defer to those more knowledgeable than I on these other two questions...<br>-MC<br></div></div><br>