<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.3.2">
</HEAD>
<BODY>
At this point I don't think the issue is the duration.. Hard-coding it at 800ms is funky but it should work for my purposes.<BR>
<BR>
My working theory at this point is that this construction of 6 RTP packets in rtp.c is causing my Grandstream to freak out. I don't know this for sure, it's just my current theory.<BR>
<BR>
in ast_rtp_senddigit, why are the RTP packets being sent in this way? 6 "ON" followed by 6 "OFF" packets for each DTMF digit?<BR>
<BR>
Bryan<BR>
<BR>
<BR>
On Sat, 2005-05-21 at 16:48 +0200, Andreas Sikkema wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">On Sat, 2005-05-21 at 09:50, Olle E. Johansson wrote:</FONT>
<FONT COLOR="#000000">> I don't think Asterisk handles the duration of the DTMF very well.</FONT>
<FONT COLOR="#000000">> In chan_sip the duration is hard coded in the source code for INFO DTMF.</FONT>
<FONT COLOR="#000000">The interface for passing dtmf from chan_sip to "the application" and</FONT>
<FONT COLOR="#000000">back to whatever channel the destination is on doesn't provide a</FONT>
<FONT COLOR="#000000">parameter for length. I suspect every channel has a hardcoded dtmf</FONT>
<FONT COLOR="#000000">length...</FONT>
</PRE>
</BLOCKQUOTE>
</BODY>
</HTML>