[Asterisk-Dev] [BOUNTY] NOTICE for dtmfmode is inband and codec is not ulaw or alaw

[Steve Underwood]

Hi Alex,

Its better than complicated - its impossible! :-)

RFC2833 exists *because* the low bit rate codecs cannot convey DTMF. 
Making * refuse to negotiate a low bit rate codec with in band DTMF 
makes some sense. Expecting someone to get it to work does not.

Regards,
Steve

Regards,
Steve

alex at pilosoft.com wrote:

>More properly, you should instead give bounty to fixing inband DTMF 
>detection code for non-PCM codecs. Shouldn't be that complicated.
>  
>
>-alex
>
>On Tue, 16 Mar 2004, Eric Wieling wrote:
>
>  
>
>>I am offering a $25 bounty for a patch that gets accepted into the
>>Digium Asterisk CVS before May 1 2004 that does the following:
>>
>>Print a NOTICE or WARNING on the Asterisk console if the negotiated
>>codec for a SIP call is not ulaw or alaw and the DTMF mode is inband.
>>
>>Since there can be multiple codecs for a SIP peer we don't know what
>>codec will be used until a call actually happens.  
>>
>>This is when the NOTICE or WARNING should be sent to the Asterisk
>>console.  Make it something informative like "Inband DTMF requires the
>>ULAW or ALAW codec to work correctly.  The codec for this call is BLAH. 
>>Use INFO or RFC2833 DTMF mode on the SIP gateway or phone and set
>>dtmfmode=info or dtmfmode=rfc2833 in the [sip-peer] section of sip.conf"
>>
>>Bounty will be paid via paypal or via check using first class mail.
>>
>>
>>    
>>
>
>_______________________________________________
>Asterisk-Dev mailing list
>Asterisk-Dev at lists.digium.com
>http://lists.digium.com/mailman/listinfo/asterisk-dev
>To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-dev
>
>  
>