<div dir="ltr"><div><div><div>Thanks for the reply Chris. The trunk has RFC2833 set on it, and the CUCM version is 8.6(2a).<br><br><div style="margin-left:40px"><img alt="Inline image 1" src="cid:ii_13ed1c80e4288a1e"><br>
</div><br><div style="margin-left:40px"><span style="font-family:courier new,monospace">admin:show version active</span><br><span style="font-family:courier new,monospace">Active Master Version: 8.6.2.22029-1</span><br><span style="font-family:courier new,monospace">Active Version Installed Software Options:</span><br>
<span style="font-family:courier new,monospace">No Installed Software Options Found.</span><br><span style="font-family:courier new,monospace">admin:</span><br></div> <br></div>The OOB/RFC2833 is interesting as this is exactly that scenario.<br>
<br>Thanks again.<br></div></div><div><div><div><div><br></div></div></div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, May 23, 2013 at 8:58 AM, Chris Ward (chrward) <span dir="ltr"><<a href="mailto:chrward@cisco.com" target="_blank">chrward@cisco.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div link="blue" vlink="purple" lang="EN-US">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Should have noted, the defect has to do with negotiating OOB and 2833 in the same call with a SIP trunk that has “no preference” selected as its DTMF method.
You could try and select a preference and see if it resolved it. But again, we need your version to confirm.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">+Chris<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Unity Connection TME<u></u><u></u></span></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<div>
<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 [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a>]
<b>On Behalf Of </b>Chris Ward (chrward)<br>
<b>Sent:</b> Thursday, May 23, 2013 9:50 AM<br>
<b>To:</b> Anthony Holloway; Cisco VoIP Group<br>
<b>Subject:</b> Re: [cisco-voip] DTMF Method 0<u></u><u></u></span></p>
</div>
</div><div><div class="h5">
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Anthony,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">For issues like these, the call flow and devices involved in the call flow are crucial. On a quick internal search, I found CSCuc80321 with the same error/warning.
We would need your version too.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">+Chris<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Unity Connection TME<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<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 [<a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">mailto:cisco-voip-bounces@puck.nether.net</a>]
<b>On Behalf Of </b>Anthony Holloway<br>
<b>Sent:</b> Thursday, May 23, 2013 12:26 AM<br>
<b>To:</b> Cisco VoIP Group<br>
<b>Subject:</b> [cisco-voip] DTMF Method 0<u></u><u></u></span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">All,<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><b>The smaller picture</b><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
I have the following two lines from a CCM trace I pulled:<u></u><u></u></p>
<div style="margin-left:30.0pt">
<p class="MsoNormal"><span style="font-family:"Courier New"">00:06:11.643 |//SIP/SIPCdpc(8,74,1872820)/ci=146637572/ccbId=85511580/scbId=0/star_CcUserInfoReq: Outbound DTMF method selected is 0. Digit=1 and isMTPPassingThru2833=0|5,200,21,1.12763334^[REDACTED]^RCP5143F0107</span><br>
<span style="font-family:"Courier New"">00:06:11.643 |//SIP/SIPCdpc(8,74,1872820)/ci=146637572/ccbId=85511580/scbId=0/star_CcUserInfoReq: Outbound DTMF method not supported (0)|5,200,21,1.12763334^[REDACTED]^RCP5143F0107</span><u></u><u></u></p>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<p class="MsoNormal">The log states that this method is not supported, but what is the method exactly?<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal"><b>The bigger picture</b><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">My Mobile Agent Connect Tone feature is half working, and I can see DTMF digits 1 and 2 being sent in the Agent's direction, however, the Agent is only hearing the second tone. I have confirmed this with the
above trace lines showing that the first tone fails due to unsupported reasons, also the below additional trace lines showing the second tone being sent via a different method and succeeding, and finally, a wireshark capture which only shows the digit 2 hitting
the wire as RTP-NTE (not shared).<u></u><u></u></p>
<div style="margin-left:30.0pt">
<p class="MsoNormal"><span style="font-family:"Courier New"">00:06:11.905 |//SIP/SIPCdpc(8,74,1872820)/ci=146637572/ccbId=85511580/scbId=0/star_CcUserInfoReq: Outbound DTMF method selected is 2. Digit=2 and isMTPPassingThru2833=0|5,200,21,1.12763334^[REDACTED]^RCP5143F0107</span><br>
<span style="font-family:"Courier New"">00:06:11.905 |//SIP/SIPCdpc(8,74,1872820)/ci=146637572/ccbId=85511580/scbId=0/sendDtmfVia2833: sending sipOutgoingDTMFTone Tone 2 for digit 2.|5,200,21,1.12763334^[REDACTED]^RCP5143F0107</span><u></u><u></u></p>
</div>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">If I could figure out the method number to name mapping, that would help me understand why method 0 is not supported while method 2 is.<br>
<br>
Thanks for your help.<u></u><u></u></p>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<p class="MsoNormal">Anthony Holloway<u></u><u></u></p>
</div>
</div></div></div>
</div>
</blockquote></div><br></div>