<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.2668" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><FONT face=Tahoma size=2><B>From:</B>
asterisk-dev-bounces@lists.digium.com
[mailto:asterisk-dev-bounces@lists.digium.com] <B>On Behalf Of </B>Bryan
Field-Elliot<BR></FONT>After working diligently with techs from two separate ATA
manufacturers, we're pretty convinced that the process of sending RFC2833 DTMF
digits outbound, from Asterisk to an ATA, is broken.<BR><BR>Note that I'm not
saying that the code in Asterisk -- ast_rtp_senddigit() -- is necessarily
broken. We have one vendor claiming it is, and another saying that they don't
handle inbound RFC2833 well in the first place.<BR><BR>What I'd really like, is
to apply a patch so that, instead of calling ast_rtp_senddigit, we instead
generate and send an inband DTMF tone (for a duration of, say,
250ms).<BR><BR><SPAN class=432141218-23062005><FONT face=Arial color=#0000ff
size=2> </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=432141218-23062005><FONT face=Arial
color=#0000ff size=2>Why not set the ATA to use info, and asterisk to
inband, it should have the same affect. </FONT></SPAN></DIV></BODY></HTML>