[asterisk-bugs] [Asterisk 0011049]: implementation of application/dtmf for SIP INFO

noreply at bugs.digium.com noreply at bugs.digium.com
Wed Nov 14 02:26:38 CST 2007


A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=11049 
====================================================================== 
Reported By:                sergee
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   11049
Category:                   Channels/chan_sip/Interoperability
Reproducibility:            N/A
Severity:                   feature
Priority:                   normal
Status:                     new
Asterisk Version:            SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 86631 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             10-22-2007 08:27 CDT
Last Modified:              11-14-2007 02:26 CST
====================================================================== 
Summary:                    implementation of application/dtmf for SIP INFO
Description: 
Currently Asterisk treats only application/dtmf-relay payload of SIP info
messages. There are some devices software which works only with
"application/dtmf" payload and doesn't support "application/dtmf-relay".
This patch implements support for "application/dtmf".
To engage it use dtmfmode=shortinfo in your sip.conf
====================================================================== 

---------------------------------------------------------------------- 
 oej - 11-14-07 02:26  
---------------------------------------------------------------------- 
As said on IRC, don't duplicate all this code. It makes chan_sip too
complicated and hard to manage. You should propably just check the value
before transmitting, to decide which of the two application/ headers to use
and accept both on incoming.

This is buggy, but neither application/dtmf-relay or application/dtmf is a
standard. At least, if they implement a non-standard implementation, they
should follow the non-standard reference document on Cisco's web site...
:-)

Please try again! /O

PS. Thanks for the comment on the new function though :-) 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
11-14-07 02:26  oej            Note Added: 0073628                          
======================================================================




More information about the asterisk-bugs mailing list