<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<div class="moz-cite-prefix">On 9/14/2012 6:04 PM, Alec Davis wrote:<br>
</div>
<blockquote cite="mid:C97840E0D9FF4916943BEA9ED5682F67@homealec"
type="cite">
<blockquote type="cite">
<pre wrap="">-----Original Message-----
From: <a class="moz-txt-link-abbreviated" href="mailto:asterisk-users-bounces@lists.digium.com">asterisk-users-bounces@lists.digium.com</a>
[<a class="moz-txt-link-freetext" href="mailto:asterisk-users-bounces@lists.digium.com">mailto:asterisk-users-bounces@lists.digium.com</a>] On Behalf Of Vieri
Sent: Saturday, 15 September 2012 8:45 a.m.
To: <a class="moz-txt-link-abbreviated" href="mailto:asterisk-users@lists.digium.com">asterisk-users@lists.digium.com</a>
Subject: [asterisk-users] DTMF digits falsely detected
Hi,
I have a context that basically does:
Wait(1)
Background(message)
WaitExten(10)
_6XXXXXX,1,DoSomething
The problem is that when I reach this context and press some
digits (eg. 6566604) then I can see in the log that Asterisk
reads 6655666.
So it's actually reading the digits twice.
How can I avoid this?
Incoming channel type is ISDN (mISDN).
</pre>
</blockquote>
<pre wrap="">
Are you saying every digit twice, or some digits twice.
Where is the call originating from, GSM cell phone or landline?
Which version of asterisk are you using?
Alec Davis
</pre>
</blockquote>
Hi,<br>
<br>
Started seeing similar abnormality today after the 1.8.16.0 upgrade.<br>
<br>
In my case digits were repeated 3 times.<br>
<br>
Several observations:<br>
<ul>
<li>The problem only manifested itself on SIP channel. OOH323 and
DAHDI did not exhibit this problem.</li>
<li>I was able to dial the extension with no issues, the problem
started in the Voice Mail application.<br>
</li>
</ul>
For example, in the case below I entered "430#"<br>
<br>
[2012-09-14 11:50:06] VERBOSE[32019] app_read.c: -- User entered
'444333000'<br>
<br>
Following is the excerpt from the DTMF log:<br>
<br>
[2012-09-14 11:50:05] DTMF[32019] channel.c: DTMF begin '4' received
on SIP/462-00000000<br>
[2012-09-14 11:50:05] DTMF[32019] channel.c: DTMF begin ignored '4'
on SIP/462-00000000<br>
[2012-09-14 11:50:05] DTMF[32019] channel.c: DTMF end '4' received
on SIP/462-00000000, duration 300 ms<br>
[2012-09-14 11:50:05] DTMF[32019] channel.c: DTMF end passthrough
'4' on SIP/462-00000000<br>
[2012-09-14 11:50:05] DTMF[32019] channel.c: DTMF end '4' received
on SIP/462-00000000, duration 300 ms<br>
[2012-09-14 11:50:05] DTMF[32019] channel.c: DTMF end passthrough
'4' on SIP/462-00000000<br>
[2012-09-14 11:50:05] DTMF[32019] channel.c: DTMF end '4' received
on SIP/462-00000000, duration 300 ms<br>
[2012-09-14 11:50:05] DTMF[32019] channel.c: DTMF end passthrough
'4' on SIP/462-00000000<br>
[2012-09-14 11:50:05] DTMF[32019] channel.c: DTMF begin '3' received
on SIP/462-00000000<br>
[2012-09-14 11:50:05] DTMF[32019] channel.c: DTMF begin ignored '3'
on SIP/462-00000000<br>
[2012-09-14 11:50:06] DTMF[32019] channel.c: DTMF end '3' received
on SIP/462-00000000, duration 300 ms<br>
[2012-09-14 11:50:06] DTMF[32019] channel.c: DTMF end passthrough
'3' on SIP/462-00000000<br>
[2012-09-14 11:50:06] DTMF[32019] channel.c: DTMF end '3' received
on SIP/462-00000000, duration 300 ms<br>
[2012-09-14 11:50:06] DTMF[32019] channel.c: DTMF end passthrough
'3' on SIP/462-00000000<br>
[2012-09-14 11:50:06] DTMF[32019] channel.c: DTMF end '3' received
on SIP/462-00000000, duration 300 ms<br>
[2012-09-14 11:50:06] DTMF[32019] channel.c: DTMF end passthrough
'3' on SIP/462-00000000<br>
[2012-09-14 11:50:06] DTMF[32019] channel.c: DTMF begin '0' received
on SIP/462-00000000<br>
[2012-09-14 11:50:06] DTMF[32019] channel.c: DTMF begin ignored '0'
on SIP/462-00000000<br>
[2012-09-14 11:50:06] DTMF[32019] channel.c: DTMF end '0' received
on SIP/462-00000000, duration 300 ms<br>
[2012-09-14 11:50:06] DTMF[32019] channel.c: DTMF end passthrough
'0' on SIP/462-00000000<br>
[2012-09-14 11:50:06] DTMF[32019] channel.c: DTMF end '0' received
on SIP/462-00000000, duration 300 ms<br>
[2012-09-14 11:50:06] DTMF[32019] channel.c: DTMF end passthrough
'0' on SIP/462-00000000<br>
[2012-09-14 11:50:06] DTMF[32019] channel.c: DTMF end '0' received
on SIP/462-00000000, duration 300 ms<br>
[2012-09-14 11:50:06] DTMF[32019] channel.c: DTMF end passthrough
'0' on SIP/462-00000000<br>
[2012-09-14 11:50:06] DTMF[32019] channel.c: DTMF begin '#' received
on SIP/462-00000000<br>
[2012-09-14 11:50:06] DTMF[32019] channel.c: DTMF begin ignored '#'
on SIP/462-00000000<br>
[2012-09-14 11:50:06] DTMF[32019] channel.c: DTMF end '#' received
on SIP/462-00000000, duration 300 ms<br>
[2012-09-14 11:50:06] DTMF[32019] channel.c: DTMF end passthrough
'#' on SIP/462-00000000<br>
[2012-09-14 11:50:06] DTMF[32019] channel.c: DTMF end '#' received
on SIP/462-00000000, duration 300 ms<br>
[2012-09-14 11:50:06] DTMF[32019] channel.c: DTMF end '#' received
on SIP/462-00000000, duration 300 ms<br>
[2012-09-14 11:50:06] DTMF[32019] channel.c: DTMF begin emulation of
'#' with duration 300 queued on SIP/462-00000000<br>
[2012-09-14 11:50:06] DTMF[32019] channel.c: DTMF end '#' received
on SIP/462-00000000, duration 300 ms<br>
[2012-09-14 11:50:07] DTMF[32019] channel.c: DTMF end emulation of
'#' queued on SIP/462-00000000<br>
[2012-09-14 11:50:07] DTMF[32019] channel.c: DTMF end '#' received
on SIP/462-00000000, duration 300 ms<br>
[2012-09-14 11:50:07] DTMF[32019] channel.c: DTMF begin emulation of
'#' with duration 300 queued on SIP/462-00000000<br>
<br>
As a comparison here is an excerpt from the DTMF log of a similar
call from the same extension before the upgrade (Asterisk 1.8.15.1):<br>
<br>
[2012-09-13 14:41:25] DTMF[7934] channel.c: DTMF begin '4' received
on SIP/462-0000007b<br>
[2012-09-13 14:41:25] DTMF[7934] channel.c: DTMF begin ignored '4'
on SIP/462-0000007b<br>
[2012-09-13 14:41:25] DTMF[7934] channel.c: DTMF end '4' received on
SIP/462-0000007b, duration 300 ms<br>
[2012-09-13 14:41:25] DTMF[7934] channel.c: DTMF end passthrough '4'
on SIP/462-0000007b<br>
[2012-09-13 14:41:25] DTMF[7934] channel.c: DTMF begin '3' received
on SIP/462-0000007b<br>
[2012-09-13 14:41:25] DTMF[7934] channel.c: DTMF begin ignored '3'
on SIP/462-0000007b<br>
[2012-09-13 14:41:25] DTMF[7934] channel.c: DTMF end '3' received on
SIP/462-0000007b, duration 300 ms<br>
[2012-09-13 14:41:25] DTMF[7934] channel.c: DTMF end passthrough '3'
on SIP/462-0000007b<br>
[2012-09-13 14:41:25] DTMF[7934] channel.c: DTMF begin '0' received
on SIP/462-0000007b<br>
[2012-09-13 14:41:25] DTMF[7934] channel.c: DTMF begin ignored '0'
on SIP/462-0000007b<br>
[2012-09-13 14:41:26] DTMF[7934] channel.c: DTMF end '0' received on
SIP/462-0000007b, duration 300 ms<br>
[2012-09-13 14:41:26] DTMF[7934] channel.c: DTMF end passthrough '0'
on SIP/462-0000007b<br>
[2012-09-13 14:41:27] DTMF[7934] channel.c: DTMF begin '#' received
on SIP/462-0000007b<br>
[2012-09-13 14:41:27] DTMF[7934] channel.c: DTMF begin ignored '#'
on SIP/462-0000007b<br>
[2012-09-13 14:41:27] DTMF[7934] channel.c: DTMF end '#' received on
SIP/462-0000007b, duration 300 ms<br>
<br>
No changes in the environment, no changes to the Soft Phone settings<br>
<br>
I did resolve the issue by switching Soft Phones, and the difference
is in DTMF duration as I can see.<br>
<br>
[2012-09-14 13:43:02] DTMF[32606] channel.c: DTMF begin '4' received
on SIP/462-0000000e<br>
[2012-09-14 13:43:02] DTMF[32606] channel.c: DTMF begin ignored '4'
on SIP/462-0000000e<br>
[2012-09-14 13:43:02] DTMF[32606] channel.c: DTMF end '4' received
on SIP/462-0000000e, duration 120 ms<br>
[2012-09-14 13:43:02] DTMF[32606] channel.c: DTMF end passthrough
'4' on SIP/462-0000000e<br>
[2012-09-14 13:43:02] DTMF[32606] channel.c: DTMF begin '3' received
on SIP/462-0000000e<br>
[2012-09-14 13:43:02] DTMF[32606] channel.c: DTMF begin ignored '3'
on SIP/462-0000000e<br>
[2012-09-14 13:43:02] DTMF[32606] channel.c: DTMF end '3' received
on SIP/462-0000000e, duration 100 ms<br>
[2012-09-14 13:43:02] DTMF[32606] channel.c: DTMF end passthrough
'3' on SIP/462-0000000e<br>
[2012-09-14 13:43:02] DTMF[32606] channel.c: DTMF begin '0' received
on SIP/462-0000000e<br>
[2012-09-14 13:43:02] DTMF[32606] channel.c: DTMF begin ignored '0'
on SIP/462-0000000e<br>
[2012-09-14 13:43:02] DTMF[32606] channel.c: DTMF end '0' received
on SIP/462-0000000e, duration 160 ms<br>
[2012-09-14 13:43:02] DTMF[32606] channel.c: DTMF end passthrough
'0' on SIP/462-0000000e<br>
[2012-09-14 13:43:03] DTMF[32606] channel.c: DTMF begin '#' received
on SIP/462-0000000e<br>
[2012-09-14 13:43:03] DTMF[32606] channel.c: DTMF begin ignored '#'
on SIP/462-0000000e<br>
[2012-09-14 13:43:03] DTMF[32606] channel.c: DTMF end '#' received
on SIP/462-0000000e, duration 80 ms<br>
<br>
<br>
I believe Asterisk 1.8.16.0 introduced an issue where a longer DTMF
causes a multiple digit recognition effect.<br>
<br>
-Vladimir<br>
<br>
<br>
</body>
</html>