On 7/16/07, <b class="gmail_sendername">The Asterisk Development Team</b> <<a href="mailto:asteriskteam@digium.com">asteriskteam@digium.com</a>> wrote:<div><span class="gmail_quote"></span><div> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
fix various known issues. See the ChangeLog included in the releases<br>for a full list of changes. The ChangeLogs are also available<br>separately on the ftp site.<br></blockquote></div><br>Is there any more information available on this change?
<br><br>2007-07-13 08:22 +0000 [r2733-2736] Tzafrir Cohen <<a href="mailto:tzafrir.cohen@xorcom.com">tzafrir.cohen@xorcom.com</a>><br><br> * Fix a digit mapping bug with hardware dtmf detection (r4357)<br>
<br>I assume those revision numbers (4xxx) in the changelog are from
another SVN repo - I was trying to figure out what exactly had changed,
but the large number of files changed across 3 revs makes it a bit tough to
isolate.<br>
<br>I'm fighting with a DTMF problem right now where directly dialed SIP->Zap (PRI) calls produce doubled-up DTMF on the other side (not every digit, but just one causes the remote IVR to go into fits). The problem first appeared when we moved from
1.2.x to * 1.4.4/Zaptel 1.4.3. I haven't had much time to investigate - it happens whether the SIP agent connected to * is using inband, rfc2833 or info and across Grandstream, Aastra and Polycom units.<br><br>Interestingly, if I send the SIP phone into DISA() pointing at it's own context, I get no DTMF problems on the remote side.
<br><br>Thanks<br clear="all"><br>-- <br>j.