[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-10-2008 04:51 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.

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

---------------------------------------------------------------------- 
 macbrody - 01-10-08 04:51  
---------------------------------------------------------------------- 
file,eliel,

please close this issue. alex-911 (our carrier guy) has altered the config
on his side (the cisco gateways).

It may still be useful to keep this for the support records, in case other
people stumble over the same issue (not every carrier is willing to adapt
his systems for a single customer).

So the attached patch may come in handy in case someone needs an urgent
work around (we've been running our system with it for a month now).

-macbrody 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
01-10-08 04:51  macbrody       Note Added: 0076624                          
======================================================================