[asterisk-bugs] [JIRA] Issue Comment Edited: (ASTERISK-20424) Erroneous Multiple DTMF Digit Detection
Rusty Newton (JIRA)
noreply at issues.asterisk.org
Sat Sep 15 16:25:27 CDT 2012
[ https://issues.asterisk.org/jira/browse/ASTERISK-20424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=197108#comment-197108 ]
Rusty Newton edited comment on ASTERISK-20424 at 9/15/12 4:24 PM:
------------------------------------------------------------------
In my case digits were repeated 3 times.
Several observations:
* The problem only manifested itself on SIP channel. OOH323 and DAHDI did not exhibit this problem.
* I was able to dial the extension with no issues, the problem started in the Voice Mail application.
For example, in the case below I entered "430#"
[2012-09-14 11:50:06] VERBOSE[32019] app_read.c: -- User entered '444333000'
Following is the excerpt from the DTMF log:
[Edit by Rusty Newton - removed inline debug and attached as annotated-dtmf-log.txt as mentioned in [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines#AsteriskIssueGuidelines-Submittingthebugreportinformationrequirements]
I believe Asterisk 1.8.16.0 introduced an issue where a longer DTMF causes a multiple digit recognition effect.
was (Author: vmikhelson):
In my case digits were repeated 3 times.
Several observations:
* The problem only manifested itself on SIP channel. OOH323 and DAHDI did not exhibit this problem.
* I was able to dial the extension with no issues, the problem started in the Voice Mail application.
For example, in the case below I entered "430#"
[2012-09-14 11:50:06] VERBOSE[32019] app_read.c: -- User entered '444333000'
Following is the excerpt from the DTMF log:
[2012-09-14 11:50:05] DTMF[32019] channel.c: DTMF begin '4' received on SIP/462-00000000
[2012-09-14 11:50:05] DTMF[32019] channel.c: DTMF begin ignored '4' on SIP/462-00000000
[2012-09-14 11:50:05] DTMF[32019] channel.c: DTMF end '4' received on SIP/462-00000000, duration 300 ms
[2012-09-14 11:50:05] DTMF[32019] channel.c: DTMF end passthrough '4' on SIP/462-00000000
[2012-09-14 11:50:05] DTMF[32019] channel.c: DTMF end '4' received on SIP/462-00000000, duration 300 ms
[2012-09-14 11:50:05] DTMF[32019] channel.c: DTMF end passthrough '4' on SIP/462-00000000
[2012-09-14 11:50:05] DTMF[32019] channel.c: DTMF end '4' received on SIP/462-00000000, duration 300 ms
[2012-09-14 11:50:05] DTMF[32019] channel.c: DTMF end passthrough '4' on SIP/462-00000000
[2012-09-14 11:50:05] DTMF[32019] channel.c: DTMF begin '3' received on SIP/462-00000000
[2012-09-14 11:50:05] DTMF[32019] channel.c: DTMF begin ignored '3' on SIP/462-00000000
[2012-09-14 11:50:06] DTMF[32019] channel.c: DTMF end '3' received on SIP/462-00000000, duration 300 ms
[2012-09-14 11:50:06] DTMF[32019] channel.c: DTMF end passthrough '3' on SIP/462-00000000
[2012-09-14 11:50:06] DTMF[32019] channel.c: DTMF end '3' received on SIP/462-00000000, duration 300 ms
[2012-09-14 11:50:06] DTMF[32019] channel.c: DTMF end passthrough '3' on SIP/462-00000000
[2012-09-14 11:50:06] DTMF[32019] channel.c: DTMF end '3' received on SIP/462-00000000, duration 300 ms
[2012-09-14 11:50:06] DTMF[32019] channel.c: DTMF end passthrough '3' on SIP/462-00000000
[2012-09-14 11:50:06] DTMF[32019] channel.c: DTMF begin '0' received on SIP/462-00000000
[2012-09-14 11:50:06] DTMF[32019] channel.c: DTMF begin ignored '0' on SIP/462-00000000
[2012-09-14 11:50:06] DTMF[32019] channel.c: DTMF end '0' received on SIP/462-00000000, duration 300 ms
[2012-09-14 11:50:06] DTMF[32019] channel.c: DTMF end passthrough '0' on SIP/462-00000000
[2012-09-14 11:50:06] DTMF[32019] channel.c: DTMF end '0' received on SIP/462-00000000, duration 300 ms
[2012-09-14 11:50:06] DTMF[32019] channel.c: DTMF end passthrough '0' on SIP/462-00000000
[2012-09-14 11:50:06] DTMF[32019] channel.c: DTMF end '0' received on SIP/462-00000000, duration 300 ms
[2012-09-14 11:50:06] DTMF[32019] channel.c: DTMF end passthrough '0' on SIP/462-00000000
[2012-09-14 11:50:06] DTMF[32019] channel.c: DTMF begin '#' received on SIP/462-00000000
[2012-09-14 11:50:06] DTMF[32019] channel.c: DTMF begin ignored '#' on SIP/462-00000000
[2012-09-14 11:50:06] DTMF[32019] channel.c: DTMF end '#' received on SIP/462-00000000, duration 300 ms
[2012-09-14 11:50:06] DTMF[32019] channel.c: DTMF end passthrough '#' on SIP/462-00000000
[2012-09-14 11:50:06] DTMF[32019] channel.c: DTMF end '#' received on SIP/462-00000000, duration 300 ms
[2012-09-14 11:50:06] DTMF[32019] channel.c: DTMF end '#' received on SIP/462-00000000, duration 300 ms
[2012-09-14 11:50:06] DTMF[32019] channel.c: DTMF begin emulation of '#' with duration 300 queued on SIP/462-00000000
[2012-09-14 11:50:06] DTMF[32019] channel.c: DTMF end '#' received on SIP/462-00000000, duration 300 ms
[2012-09-14 11:50:07] DTMF[32019] channel.c: DTMF end emulation of '#' queued on SIP/462-00000000
[2012-09-14 11:50:07] DTMF[32019] channel.c: DTMF end '#' received on SIP/462-00000000, duration 300 ms
[2012-09-14 11:50:07] DTMF[32019] channel.c: DTMF begin emulation of '#' with duration 300 queued on SIP/462-00000000
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):
[2012-09-13 14:41:25] DTMF[7934] channel.c: DTMF begin '4' received on SIP/462-0000007b
[2012-09-13 14:41:25] DTMF[7934] channel.c: DTMF begin ignored '4' on SIP/462-0000007b
[2012-09-13 14:41:25] DTMF[7934] channel.c: DTMF end '4' received on SIP/462-0000007b, duration 300 ms
[2012-09-13 14:41:25] DTMF[7934] channel.c: DTMF end passthrough '4' on SIP/462-0000007b
[2012-09-13 14:41:25] DTMF[7934] channel.c: DTMF begin '3' received on SIP/462-0000007b
[2012-09-13 14:41:25] DTMF[7934] channel.c: DTMF begin ignored '3' on SIP/462-0000007b
[2012-09-13 14:41:25] DTMF[7934] channel.c: DTMF end '3' received on SIP/462-0000007b, duration 300 ms
[2012-09-13 14:41:25] DTMF[7934] channel.c: DTMF end passthrough '3' on SIP/462-0000007b
[2012-09-13 14:41:25] DTMF[7934] channel.c: DTMF begin '0' received on SIP/462-0000007b
[2012-09-13 14:41:25] DTMF[7934] channel.c: DTMF begin ignored '0' on SIP/462-0000007b
[2012-09-13 14:41:26] DTMF[7934] channel.c: DTMF end '0' received on SIP/462-0000007b, duration 300 ms
[2012-09-13 14:41:26] DTMF[7934] channel.c: DTMF end passthrough '0' on SIP/462-0000007b
[2012-09-13 14:41:27] DTMF[7934] channel.c: DTMF begin '#' received on SIP/462-0000007b
[2012-09-13 14:41:27] DTMF[7934] channel.c: DTMF begin ignored '#' on SIP/462-0000007b
[2012-09-13 14:41:27] DTMF[7934] channel.c: DTMF end '#' received on SIP/462-0000007b, duration 300 ms
No changes in the environment, no changes to the Soft Phone settings
I did resolve the issue by switching Soft Phones, and the difference is in DTMF duration as I can see.
[2012-09-14 13:43:02] DTMF[32606] channel.c: DTMF begin '4' received on SIP/462-0000000e
[2012-09-14 13:43:02] DTMF[32606] channel.c: DTMF begin ignored '4' on SIP/462-0000000e
[2012-09-14 13:43:02] DTMF[32606] channel.c: DTMF end '4' received on SIP/462-0000000e, duration 120 ms
[2012-09-14 13:43:02] DTMF[32606] channel.c: DTMF end passthrough '4' on SIP/462-0000000e
[2012-09-14 13:43:02] DTMF[32606] channel.c: DTMF begin '3' received on SIP/462-0000000e
[2012-09-14 13:43:02] DTMF[32606] channel.c: DTMF begin ignored '3' on SIP/462-0000000e
[2012-09-14 13:43:02] DTMF[32606] channel.c: DTMF end '3' received on SIP/462-0000000e, duration 100 ms
[2012-09-14 13:43:02] DTMF[32606] channel.c: DTMF end passthrough '3' on SIP/462-0000000e
[2012-09-14 13:43:02] DTMF[32606] channel.c: DTMF begin '0' received on SIP/462-0000000e
[2012-09-14 13:43:02] DTMF[32606] channel.c: DTMF begin ignored '0' on SIP/462-0000000e
[2012-09-14 13:43:02] DTMF[32606] channel.c: DTMF end '0' received on SIP/462-0000000e, duration 160 ms
[2012-09-14 13:43:02] DTMF[32606] channel.c: DTMF end passthrough '0' on SIP/462-0000000e
[2012-09-14 13:43:03] DTMF[32606] channel.c: DTMF begin '#' received on SIP/462-0000000e
[2012-09-14 13:43:03] DTMF[32606] channel.c: DTMF begin ignored '#' on SIP/462-0000000e
[2012-09-14 13:43:03] DTMF[32606] channel.c: DTMF end '#' received on SIP/462-0000000e, duration 80 ms
I believe Asterisk 1.8.16.0 introduced an issue where a longer DTMF causes a multiple digit recognition effect.
> Erroneous Multiple DTMF Digit Detection
> ---------------------------------------
>
> Key: ASTERISK-20424
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-20424
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Applications/app_read, Channels/General
> Affects Versions: 1.8.16.0
> Environment: CentOS 5.7
> FreePBX 2.10.1.2
> Reporter: Vladimir Mikhelson
> Attachments: annotated-dtmf-log.txt, rtp-debug.txt, vm-430.pcapng
>
>
> Starting with asterisk 1.8.16.0 longer DTMF tones transmitted per RFC3822 get interpreted as double, triple, etc. digits.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the asterisk-bugs
mailing list