<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
p
        {mso-style-priority:99;
        mso-margin-top-alt:auto;
        margin-right:0in;
        mso-margin-bottom-alt:auto;
        margin-left:0in;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";}
span.EmailStyle18
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:black;}
span.EmailStyle19
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:black;}
span.EmailStyle20
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:black;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@page Section1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
        {page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:black'>FWIW:</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:black'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:black'>I’m a major noob lurker on this list. Regardless
we’re seeing DTMF issues on all our MGCP gateways since upgrading sets to
FW 8.4.1 as well. Perhaps similar to yours, perhaps different.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:black'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:black'>I don’t have any traces or anything to back the claim up,
but it seems like when a number is pressed on the set, it ends up sending more
than one DTMF digit, which causes issues with a number of phone menus, usually</span><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'>
resulting in a disconnect or an error, depending on the menu. This issue
started occurring immediately after we did firmware upgrade to 8.4.1 (it
persists in 8.4.1 SR1), and it’s affecting at least our 7941, 7942, 7962,
7970, and 7975 (all skinny) sets. However, interestingly enough, the issue
doesn’t occur when using speakerphone—only when using the
handset. I’m not sure about when using a headset.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:black'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:black'>Interested in how this turns out and what you can dig up. My
search has been fruitless thus far.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:black'><o:p> </o:p></span></p>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:navy'>Eric
Isakson</span><span lang=EN style='color:black'> <br>
</span><span lang=EN style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:navy'>Network Engineer</span><span lang=EN style='color:black'> <br>
</span><span lang=EN style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:navy'>Information Technology Dept.</span><span lang=EN style='color:black'>
<br>
</span><span lang=EN style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:navy'>Ogden Clinic P.C.</span><span lang=EN style='color:black'> <o:p></o:p></span></p>
</div>
<p class=MsoNormal><span lang=EN style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:black'> </span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:black'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:black'><o:p> </o:p></span></p>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net] <b>On
Behalf Of </b>Scott Voll<br>
<b>Sent:</b> Thursday, October 09, 2008 14:25<br>
<b>To:</b> James Buchanan<br>
<b>Cc:</b> cisco-voip-bounces@puck.nether.net; Dave_Landsiedel@bobcat.com;
cisco voip<br>
<b>Subject:</b> Re: [cisco-voip] What would cause DTMF not to go through<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<div>
<p class=MsoNormal>more wide spread. They are G711, but thus far it's
just one location (multiple users) but they are the only ones that are using
7962 phones and firmware <a href="http://8.4.1.">8.4.1.</a> Also. I
see a bunch of bugs for DTMF but they are all related to SIP / CTI but these
users are not using either of those.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>Any more ideas?<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'>Scott<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>On Tue, Oct 7, 2008 at 12:05 PM, James Buchanan <<a
href="mailto:jbuchanan@ctiusa.com">jbuchanan@ctiusa.com</a>> wrote:<o:p></o:p></p>
<div>
<div>
<p><span style='font-size:11.0pt;color:#1F497D'>The rtp-nte is used typically
for SIP trunks. H245-alphanumeric is what you would typically use. Have you determined
this to be for one specific user or is it more widespread?</span><o:p></o:p></p>
<p><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p><b><span style='font-size:10.0pt'>From:</span></b><span style='font-size:
10.0pt'> <a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a>
[mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a>]
<b>On Behalf Of </b>Scott Voll<br>
<b>Sent:</b> Tuesday, October 07, 2008 2:01 PM<br>
<b>To:</b> <a href="mailto:Dave_Landsiedel@bobcat.com" target="_blank">Dave_Landsiedel@bobcat.com</a><br>
<b>Cc:</b> <a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a>;
cisco voip<br>
<b>Subject:</b> Re: [cisco-voip] What would cause DTMF not to go through</span><o:p></o:p></p>
</div>
<div>
<div>
<p> <o:p></o:p></p>
<div>
<div>
<p>H323<o:p></o:p></p>
</div>
<div>
<p> <o:p></o:p></p>
</div>
<div>
<p>What's the difference between <o:p></o:p></p>
</div>
<div>
<p> <o:p></o:p></p>
</div>
<div>
<p> dtmf-relay h245-alphanumeric<o:p></o:p></p>
</div>
<div>
<p> <o:p></o:p></p>
</div>
<div>
<p>and <o:p></o:p></p>
</div>
<div>
<p> <o:p></o:p></p>
</div>
<div>
<p>dtmf-relay rtp-nte h245-alphanumeric <o:p></o:p></p>
</div>
<div>
<p>??<o:p></o:p></p>
</div>
<div>
<p> <o:p></o:p></p>
</div>
<div>
<p>CMM blade with IOS 12.4(15)T4<o:p></o:p></p>
</div>
<div>
<p> <o:p></o:p></p>
</div>
<div>
<p>Thanks<o:p></o:p></p>
</div>
<div>
<p> <o:p></o:p></p>
</div>
<div>
<p style='margin-bottom:12.0pt'>Scott<o:p></o:p></p>
</div>
<div>
<p>On Tue, Oct 7, 2008 at 11:09 AM, <<a
href="mailto:Dave_Landsiedel@bobcat.com" target="_blank">Dave_Landsiedel@bobcat.com</a>>
wrote:<o:p></o:p></p>
<p><br>
<span style='font-size:10.0pt'>If using dial peer voice voip via a H323 gateway
make sure you have the following line in that dial peer.</span> <br>
<br>
<span style='font-size:10.0pt'> dtmf-relay rtp-nte h245-alphanumeric</span>
<br>
<span style='font-size:10.0pt'> <br>
</span><span style='color:#004080'>_________________________________</span> <o:p></o:p></p>
</div>
<p> <o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</div>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-SIZE: 7.5pt; FONT-FAMILY: 'Verdana','sans-serif'; mso-fareast-font-family: 'Times New Roman'"><STRONG></STRONG></SPAN> </P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-SIZE: 7.5pt; FONT-FAMILY: 'Verdana','sans-serif'; mso-fareast-font-family: 'Times New Roman'"><STRONG></STRONG></SPAN> </P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-SIZE: 7.5pt; FONT-FAMILY: 'Verdana','sans-serif'; mso-fareast-font-family: 'Times New Roman'"><STRONG></STRONG></SPAN> </P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-SIZE: 7.5pt; FONT-FAMILY: 'Verdana','sans-serif'; mso-fareast-font-family: 'Times New Roman'"><STRONG>
<HR>
</STRONG></SPAN><FONT face=Arial size=3><SPAN
style="FONT-SIZE: 7.5pt; FONT-FAMILY: 'Verdana','sans-serif'; mso-fareast-font-family: 'Times New Roman'"><STRONG>This
email is confidential and may be legally privileged. It is intended solely for
the addressee. Access to this email by anyone else, unless expressly
approved by the sender or an authorized addressee, is unauthorized. If you are
not the intended recipient, any disclosure, copying, distribution or any action
omitted or taken in reliance on it, is prohibited and may be unlawful. If
you believe that you have received this email in error, please contact the
sender, delete this email, and destroy all
copies.</STRONG></SPAN></FONT>
</body>
</html>