[asterisk-bugs] [Asterisk 0011489]: 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!): 91736 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             12-07-2007 07:36 CST
Last Modified:              12-12-2007 09:46 CST
====================================================================== 
Summary:                    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.

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

---------------------------------------------------------------------- 
 eliel - 12-12-07 09:46  
---------------------------------------------------------------------- 
dtmfmode=rfc2833 is checked against endpoint capabilities, so if endpoint
tries to use rfc2833 and we only accept sip info (bacause it is setted on
the .conf), there will be no agreement in the negotiation, that is the use
we give to dtmfmode, not to force the negotiation just to accept what the
endpoint has to offer.

I think we already support cisco incompatibilities so (or at least I have
seen if (cisco) {} code), the best way would be to support X-NSE, but this
should be discussed on the mailing list. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
12-12-07 09:46  eliel          Note Added: 0075265                          
======================================================================