[asterisk-bugs] [Asterisk 0015642]: [patch] Fix for Sonus DTMF issues

Asterisk Bug Tracker noreply at bugs.digium.com
Fri Jul 9 11:39:05 CDT 2010


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15642 
====================================================================== 
Reported By:                jasonshugart
Assigned To:                twilson
====================================================================== 
Project:                    Asterisk
Issue ID:                   15642
Category:                   Core/RTP
Reproducibility:            always
Severity:                   feature
Priority:                   normal
Status:                     ready for testing
Target Version:             1.6.2.10
Asterisk Version:           SVN 
JIRA:                       SWP-406 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-08-03 12:28 CDT
Last Modified:              2010-07-09 11:39 CDT
====================================================================== 
Summary:                    [patch] Fix for Sonus DTMF issues
Description: 
In some cases when Asterisk sends DTMF to Sonus platforms as RFC2833, Sonus
will not recognize the DTMF.  Several articles have identified the problem
as being the gap in the audio prior to the DTMF packets being sent.  This
patch sends a single G.711 ulaw packet prior to the rfc2833 packets.  In
our testing across with two carriers (Level3 and 360 Networks) this patch
fixed our DTMF issues.  The rtp.c file seems very similar for the 1.4
branch, so minor changes could also be applied there.  I added an option to
the rtp.conf file to enable this fix, called rtpfixdtmf.  Attached are both
the rtp.c fix, and the rtp.conf change.
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
has duplicate       0016625 RFC2833 DTMF is not passed correctly wh...
====================================================================== 

---------------------------------------------------------------------- 
 (0124396) eeman (reporter) - 2010-07-09 11:39
 https://issues.asterisk.org/view.php?id=15642#c124396 
---------------------------------------------------------------------- 
I have some more updated information which really seems to confuse things
more.

my original test handset was an analog phone connected to a TDM800 fxs
port .. with this device (where asterisk creates the rfc2833) I experience
100% failure to detect all 9 digits correctly. In almost every test
multiple digits are missing. The same device on the same pbx calling out to
the asterisk 1.6.26.3 gateway works without issue to both the test macro
and the PSTN.

I then conducted the same test from a polycom 501 running firmware 3.1.2,
upstairs and had less than 5% failure. Basically out of 20 tests only 1
failure and that was losing a single digit. 

I repeated the test once more with a linksys ATA 2102 with firmware 5.2.5
and had more failures, but still only missing 1 digit per 9 digit
sequence.

so when the original source is an FXS port on dahdi hardware the failure
rate is very very high. When the source is an older model polycom the
failure rate is considerably lower (but still not acceptable)

I just ran the test using a Polycom 550 firmware 3.2.2 and out of 10 tests
I experienced zero errors. In that scenario it went

polycom550 -> [asterisk 1.4.26.3] -> [asterisk 1.6.2.10-rc1] -> BroadVox
SONUS -> PSTN 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-07-09 11:39 eeman          Note Added: 0124396                          
======================================================================




More information about the asterisk-bugs mailing list