[asterisk-bugs] [Asterisk 0011489]: [patch] During call setup signalling asterisk does not offer telephone-event (rfc2833) anymore

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=11489 
====================================================================== 
Reported By:                macbrody
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   11489
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   block
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.4.15  
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!): 94191 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             12-07-2007 07:36 CST
Last Modified:              01-07-2008 05:31 CST
====================================================================== 
Summary:                    [patch] During call setup signalling asterisk does
not offer telephone-event (rfc2833) anymore
Description: 
What happened:
As of asterisk-1.4.15 (tested trunk too) asterisk, when
connected to a peer via sip trunk does not recognize dtmf
anymore (same config worked with 1.4.13).

What I found:
During signalling negotiation at call setup in the sdp body,
asterisk does not offer the rtpmap: telephone-event anymore,
even if I configure dtmfmode=rfc2833.

Therefore the other end will not send any rfc2833 specific rtp events.

====================================================================== 

---------------------------------------------------------------------- 
 alex-911 - 01-07-08 05:31  
---------------------------------------------------------------------- 
this issue could be solved by an appropriate configuration on the cisco
media gateways. when the gateway sends "a=rtpmap:99 telephone-event/8000",
DTMF is recognized. I have tested this against 1.4.17.
@macbrody: pls test against your provider. it should work now ;) 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
01-07-08 05:31  alex-911       Note Added: 0076390                          
======================================================================