<div dir="ltr"><div><div>Hi, <br><br></div>I'm facing a "strange" problem with DTMF, on a FS server I'm using (Version 1.5.8b git fe2a4d6 2014-02-14 00:03:11Z 64bit).<br></div>For some calls going through FS, when customers send DTMF tones (using RFC2833), I see those logs :<br><br><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">2014-11-14 15:47:48.516849 [DEBUG] switch_rtp.c:5683 RTP RECV DTMF 1:742<br>2014-11-14 15:47:48.516849 [DEBUG] switch_channel.c:489 RECV DTMF 1:742<br>2014-11-14 15:47:49.056857 [DEBUG] switch_rtp.c:5683 RTP RECV DTMF C:640<br>2014-11-14 15:47:49.056857 [DEBUG] switch_channel.c:489 RECV DTMF C:640<br>2014-11-14 15:47:49.356848 [DEBUG] switch_rtp.c:5683 RTP RECV DTMF 2:661<br>2014-11-14 15:47:49.356848 [DEBUG] switch_channel.c:489 RECV DTMF 2:661<br>2014-11-14 15:47:49.696846 [DEBUG] switch_rtp.c:5683 RTP RECV DTMF 3:665<br>2014-11-14 15:47:49.696846 [DEBUG] switch_channel.c:489 RECV DTMF 3:665<br>2014-11-14 15:47:50.256872 [DEBUG] switch_rtp.c:5683 RTP RECV DTMF 4:745<br>2014-11-14 15:47:50.256872 [DEBUG] switch_channel.c:489 RECV DTMF 4:745<br>2014-11-14 15:47:50.796855 [DEBUG] switch_rtp.c:5683 RTP RECV DTMF 5:741<br>2014-11-14 15:47:50.796855 [DEBUG] switch_channel.c:489 RECV DTMF 5:741<br>2014-11-14 15:47:51.236850 [DEBUG] switch_rtp.c:5683 RTP RECV DTMF 6:664<br>2014-11-14 15:47:51.236850 [DEBUG] switch_channel.c:489 RECV DTMF 6:664<br></blockquote><div><div><br></div><div>Here, the customer tried to send "123456". So, I don't know why this "C" character has been sent, and I'm sure the customer didn't send this, because there's no "C" touch on his phone's keypad...<br></div><div>And this "C" results in a double "1" received on the IVR server (hosted on another server than FS).<br></div><div>(Ex : 123456 => 1C23456 => 1123456)<br></div><div><br></div><div>It doesn't happen everytime, but for around 80% of calls... So it's really a problem for us...<br><br></div><div>I looked at PCAPs for concerned calls, and saw that DTMF tones are only sent with RFC2833, not with SIP INFO nor InBand. <br></div><div>I first thought that digits may be received simultaneously with RFC2833 and InBand but definitely not.<br><br></div><div>Do you think what could be the cause of that ? I don't use "start_dtmf" in my diaplans, I already saw in other ML topics that this may cause double digit problems<span style="font-size:9pt;font-family:"Courier New";color:black;background:none repeat scroll 0% 0% white">.<br></span></div><div><span style="font-size:9pt;font-family:"Courier New";color:black;background:none repeat scroll 0% 0% white"><br></span></div><div>Is there a way to ask freeswitch to only handle 0-9*# characters ? Or any idea, I'll be glad to try anything that can help us !<br><br>Thanks for help,<br><br>Kevin<span style="font-size:9pt;font-family:"Courier New";color:black;background:none repeat scroll 0% 0% white"><br><br><br></span></div><div><span style="font-size:9pt;font-family:"Courier New";color:black;background:none repeat scroll 0% 0% white"><br></span></div><div><div><div><div><div class="gmail_signature"><b><div><span style="font-weight:normal">Bien cordialement, </span></div><div><span style="font-weight:normal">Best Regards, </span></div><div><span style="font-weight:normal"><br></span></div></b><b>Kevin MATHY</b> |<b> </b>Ingénieur VoIP<br><div><div><b><br></b></div></div></div></div>
</div></div></div></div></div>
<br>
<img src="http://www.hexanet.fr/sites/files/hexanet/files/utilities/signature_hexanet.gif">