[Home]

Summary:ASTERISK-17766: Outbound DTMF issues
Reporter:John Knight (Cbeyond) (cbeyond_jknight)Labels:
Date Opened:2011-04-28 09:34:25Date Closed:2011-07-26 14:47:20
Priority:MajorRegression?No
Status:Closed/CompleteComponents:PBX/General
Versions:1.4.41 Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) CCS_BT_0000019_DTMFissue_vanilla_1.4.41.pcap
Description:DTMF will get misinterpreted frequently or pass along incorrect values when using a build of Asterisk 1.4.41 on outbound calls.

We have tried dialing our office pbx (running Asterisk 1.4.39) and Bank of America to test the outbound DTMF functionality.

Asterisk is running on Gentoo in an OpenVZ container environment running CentOS.  We are not able to reproduce with this issue with releases we have used in the past (1.4.39, 1.4.35 or 1.4.26) in the same environment.

****** ADDITIONAL INFORMATION ******

We have opened a ticket on our bug tracker tracking this issue:

http://bugtracker.aretta.net/view.php?id=19
Comments:By: John Knight (Cbeyond) (cbeyond_jknight) 2011-04-28 09:36:02

Attaching "CCS_BT_0000019_DTMFissue_vanilla_1.4.41.pcap".

This is a trace of vanilla Asterisk 1.4.41 from Digium reproducing the issue by

1) dialing 14044782200 and attempting to dial '207' at the IVR prompt to dial extension 207.
2) dialing 18002884408 and attempting to dial '1' at the IVR prompt to choose English option from IVR.

By: John Knight (Cbeyond) (cbeyond_jknight) 2011-04-28 09:41:37

Additional information:

Trunk is using "dtmfmode=rfc2833" for dtmf mode.

Call is being placed from a Polycom 550.

By: Russell Bryant (russell) 2011-07-26 14:47:14.532-0500

Per the Asterisk maintenance timeline page at http://www.asterisk.org/asterisk-versions maintenance (bug) support for the 1.4 and 1.6.x branches has ended. For continued maintenance support please move to the 1.8 branch which is a long term support (LTS) branch. For more information about branch support, please see https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions

If this is still an issue, please open a new issue so it can be re-triaged appropriately. Thanks!