[asterisk-bugs] [Asterisk 0019184]: DTMF ( RFC2833 or SIP INFO ) sent incorrectly when bridged to a DAHDI channel on remote server.

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=19184 
====================================================================== 
Reported By:                dlublink
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   19184
Category:                   Channels/chan_sip/Interoperability
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:           1.6.2.17.3 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2011-04-26 12:38 CDT
Last Modified:              2011-04-26 14:09 CDT
====================================================================== 
Summary:                    DTMF ( RFC2833 or SIP INFO ) sent incorrectly when
bridged to a DAHDI channel on remote server.
Description: 
I have two asterisk boxes. The first box dials the second box, the second
box's dialplan connects the channel to DAHDI. The first box dials DTMF but
are incorrectly transmitted ( whether sent on SIP INFO OR RFC2833 ).
====================================================================== 

---------------------------------------------------------------------- 
 (0134145) dlublink (reporter) - 2011-04-26 14:09
 https://issues.asterisk.org/view.php?id=19184#c134145 
---------------------------------------------------------------------- 
If you open the pcap files in wireshark and go into Telphony menu into
VoIPCalls. Click the call, and graph it.

Look at the number of packets sent, that is clearly an error. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-04-26 14:09 dlublink       Note Added: 0134145                          
======================================================================