[asterisk-bugs] [Asterisk 0012245]: [patch] Support for RFC2833 DTMF for dumb SIP proxies

Asterisk Bug Tracker noreply at bugs.digium.com
Mon Dec 8 12:47:39 CST 2008


A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12245 
====================================================================== 
Reported By:                bamby
Assigned To:                otherwiseguy
====================================================================== 
Project:                    Asterisk
Issue ID:                   12245
Category:                   Channels/NewFeature
Reproducibility:            always
Severity:                   feature
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.4.18 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-03-18 03:25 CDT
Last Modified:              2008-12-08 12:47 CST
====================================================================== 
Summary:                    [patch] Support for RFC2833 DTMF for dumb SIP
proxies
Description: 
My recent upgrade from asterisk 1.2 to 1.4 brought in a problem.

Let me describe my setup. Calls from Asterisk are coming through the dumb
SIP proxy that doesn't announce the support for the RFC2833 telephone-event
but relays all the RTP packets regardless of RTP payload type so remote
IVRs can receive the DTMFs.

The Asterisk 1.4 handles this situation more correctly than 1.2, it drops
the telephone-events if peer didn't announce support for them in SDP. But
the problem is that this dumb SIP proxy cannot be neither avoided nor
fixed.

I've added a couple of configuration options that helps to recover the
previous behavior and also allows an administrator to choose the payload
type value for the telephone-event payload.

I believe I'm not alone with this problem so IMO this feature would be
helpful for some people.
====================================================================== 

---------------------------------------------------------------------- 
 (0095965) otherwiseguy (administrator) - 2008-12-08 12:47
 http://bugs.digium.com/view.php?id=12245#c95965 
---------------------------------------------------------------------- 
The problem is, I don't think anyone else has or will run into the problem.
 Whatever "dumb sip proxy" is there, is clearly doing something wrong by
stripping out the ability of the phones on the other side and the vendor
needs to fix it.  The possibility of more than one vendor making this
mistake seems pretty small to me. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-12-08 12:47 otherwiseguy   Note Added: 0095965                          
======================================================================




More information about the asterisk-bugs mailing list