<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: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=iso-8859-1">
<meta name="Generator" content="Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-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;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle24
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle25
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle26
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></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="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">Hi Chris,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Turning on rel1xx in CUCM gets CUCM to send a PRACK to the SIP 183, but still doesn't fix the dtmf problem. With or without PRACK enabled, both the Invite and Session Progress have the "Allow-Events: kpml" header.
Also, I have early offer configured in CUCM, and RTP is set up after the 100/183 exchange so the gateway in theory should be able to subscribe to kpml at that point.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">It's only been one number so far and I have a workaround by having a specific dial-peer to use sip-notify so maybe I'll wait and see if I get more problem reports before opening a TAC case.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Eric<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></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""> Chris Ward (chrward) [mailto:chrward@cisco.com]
<br>
<b>Sent:</b> 24 October 2012 7:58 AM<br>
<b>To:</b> Eric Pedersen; cisco-voip@puck.nether.net<br>
<b>Subject:</b> RE: no DTMF to a specific number<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">According to the bug it could be. But as you said, it’s just one number and in production so it’s something to test carefully.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<div>
<p class="MsoNormal"><span style="color:#1F497D">+Chris</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Unity Connection TME</span><o:p></o:p></p>
</div>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></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""> Eric Pedersen [<a href="mailto:PedersenE@bennettjones.com">mailto:PedersenE@bennettjones.com</a>]
<br>
<b>Sent:</b> Tuesday, October 23, 2012 6:18 PM<br>
<b>To:</b> Chris Ward (chrward); <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<b>Subject:</b> RE: no DTMF to a specific number</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">We're running 15.1(4)M4. I don't have any configuration for reliable responses though so the gateway doesn't send a PRACK. Do you think that's the problem? I can try turning on rel1xx in CUCM.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></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""> Chris Ward (chrward) [<a href="mailto:chrward@cisco.com">mailto:chrward@cisco.com</a>]
<br>
<b>Sent:</b> 23 October 2012 3:25 PM<br>
<b>To:</b> Eric Pedersen; <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<b>Subject:</b> RE: no DTMF to a specific number</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">12.5 = 15.X I believe…</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<div>
<p class="MsoNormal"><span style="color:#1F497D">+Chris</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Unity Connection TME</span><o:p></o:p></p>
</div>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></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"">
<a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a> [<a href="mailto:cisco-voip-bounces@puck.nether.net">mailto:cisco-voip-bounces@puck.nether.net</a>]
<b>On Behalf Of </b>Chris Ward (chrward)<br>
<b>Sent:</b> Tuesday, October 23, 2012 5:23 PM<br>
<b>To:</b> Eric Pedersen; <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<b>Subject:</b> Re: [cisco-voip] no DTMF to a specific number</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Did some quick topic searching and found a thread that suggests the fix for CSCsm15480 should enable KPML before connected state.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Looks like “</span><span style="font-size:13.5pt;color:black">12.4(15)XL04 or 12.4(15)T08</span><span style="color:#1F497D">” or anything 12.5 and up should have the fix. What IOS are you running on your GW?</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<div>
<p class="MsoNormal"><span style="color:#1F497D">+Chris</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Unity Connection TME</span><o:p></o:p></p>
</div>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></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"">
<a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a> [<a href="mailto:cisco-voip-bounces@puck.nether.net">mailto:cisco-voip-bounces@puck.nether.net</a>]
<b>On Behalf Of </b>Eric Pedersen<br>
<b>Sent:</b> Tuesday, October 23, 2012 4:52 PM<br>
<b>To:</b> <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<b>Subject:</b> [cisco-voip] no DTMF to a specific number</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-CA">CUCM 8.6 <- SIP-> GW(IOS 15.1) <- PRI -> PSTN</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-CA"> </span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-CA">I'm having a strange DTMF relay problem with a specific destination: when we call this number, their IVR answers but DTMF doesn't work. I ran an ISDN debug, and I see that their IVR audio starts after we receive an ISDN
PROGRESS message without ever receiving an ISDN CONNECT message. At this point the gateway has only sent a SIP 183 Session Progress message to CUCM, not a SIP 200. I have the gateway configured to use KPML for DTMF relay, but the gateway doesn't subscribe
to kpml until after sending SIP 200. </span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-CA"> </span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-CA">I set up a specific incoming dial-peer for this number with dtmf-relay sip-notify and that works fine, but I'd rather not do a one-off configuration for this, and kpml seems to work fine with every other call.
</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-CA"> </span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-CA">Has anyone seen anything like this? It seems to me like this is a configuration problem on their end, but it works calling from my cell phone.</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-CA"> </span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-CA">FYI, this is what the ISDN message sequence looks like for the problematic call:</span><o:p></o:p></p>
<p class="MsoNormal">715102: Oct 23 13:34:51.065 MDT: ISDN Se0/0/1:23 Q931: Sending SETUP callref = 0x5559 callID = 0xD360 switch = primary-dms100 interface = User
<o:p></o:p></p>
<p class="MsoNormal">715103: Oct 23 13:34:51.065 MDT: ISDN Se0/0/1:23 Q931: TX -> SETUP pd = 8 callref = 0x5559
<o:p></o:p></p>
<p class="MsoNormal">715104: Oct 23 13:34:51.193 MDT: ISDN Se0/0/1:23 Q931: RX <- CALL_PROC pd = 8 callref = 0xD559
<o:p></o:p></p>
<p class="MsoNormal"><b>715105: Oct 23 13:34:52.541 MDT: ISDN Se0/0/1:23 Q931: RX <- PROGRESS pd = 8 callref = 0xD559
</b><o:p></o:p></p>
<p class="MsoNormal"><b><span style="font-family:Wingdings">ß</span> IVR STARTS </b>
<b><span style="font-family:Wingdings">à</span></b><o:p></o:p></p>
<p class="MsoNormal">715133: Oct 23 13:35:26.633 MDT: ISDN Se0/0/1:23 Q931: TX -> DISCONNECT pd = 8 callref = 0x5559
<o:p></o:p></p>
<p class="MsoNormal">715134: Oct 23 13:35:26.693 MDT: ISDN Se0/0/1:23 Q931: RX <- RELEASE pd = 8 callref = 0xD559<o:p></o:p></p>
<p class="MsoNormal">715135: Oct 23 13:35:26.693 MDT: ISDN Se0/0/1:23 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x5559<o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-CA"> </span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-CA">A call to a working IVR looks like:</span><o:p></o:p></p>
<p class="MsoNormal">714989: Oct 23 13:33:07.677 MDT: ISDN Se0/0/1:23 Q931: Sending SETUP callref = 0x554F callID = 0xD356 switch = primary-dms100 interface = User
<o:p></o:p></p>
<p class="MsoNormal">714990: Oct 23 13:33:07.677 MDT: ISDN Se0/0/1:23 Q931: TX -> SETUP pd = 8 callref = 0x554F
<o:p></o:p></p>
<p class="MsoNormal">714991: Oct 23 13:33:07.793 MDT: ISDN Se0/0/1:23 Q931: RX <- CALL_PROC pd = 8 callref = 0xD54F
<o:p></o:p></p>
<p class="MsoNormal">714995: Oct 23 13:33:10.341 MDT: ISDN Se0/0/1:23 Q931: RX <- ALERTING pd = 8 callref = 0xD54F
<o:p></o:p></p>
<p class="MsoNormal"><b>714996: Oct 23 13:33:10.541 MDT: ISDN Se0/0/1:23 Q931: RX <- CONNECT pd = 8 callref = 0xD54F</b><o:p></o:p></p>
<p class="MsoNormal"><b>714998: Oct 23 13:33:10.541 MDT: ISDN Se0/0/1:23 Q931: TX -> CONNECT_ACK pd = 8 callref = 0x554F</b><o:p></o:p></p>
<p class="MsoNormal"><b><span style="font-family:Wingdings">ß</span> IVR STARTS </b>
<b><span style="font-family:Wingdings">à</span></b><o:p></o:p></p>
<p class="MsoNormal">715007: Oct 23 13:33:15.629 MDT: ISDN Se0/0/1:23 Q931: TX -> DISCONNECT pd = 8 callref = 0x554F
<o:p></o:p></p>
<p class="MsoNormal">715008: Oct 23 13:33:15.689 MDT: ISDN Se0/0/1:23 Q931: RX <- RELEASE pd = 8 callref = 0xD54F<o:p></o:p></p>
<p class="MsoNormal">715009: Oct 23 13:33:15.693 MDT: ISDN Se0/0/1:23 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x554F<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Regards,<o:p></o:p></p>
<p class="MsoNormal">Eric<o:p></o:p></p>
<pre>The contents of this message may contain confidential and/or privileged<o:p></o:p></pre>
<pre>subject matter. If this message has been received in error, please contact<o:p></o:p></pre>
<pre>the sender and delete all copies. Like other forms of communication,<o:p></o:p></pre>
<pre>e-mail communications may be vulnerable to interception by unauthorized<o:p></o:p></pre>
<pre>parties. If you do not wish us to communicate with you by e-mail, please<o:p></o:p></pre>
<pre>notify us at your earliest convenience. In the absence of such<o:p></o:p></pre>
<pre>notification, your consent is assumed. Should you choose to allow us to<o:p></o:p></pre>
<pre>communicate by e-mail, we will not take any additional security measures<o:p></o:p></pre>
<pre>(such as encryption) unless specifically requested.<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>The contents of this message may contain confidential and/or privileged<o:p></o:p></pre>
<pre>subject matter. If this message has been received in error, please contact<o:p></o:p></pre>
<pre>the sender and delete all copies. Like other forms of communication,<o:p></o:p></pre>
<pre>e-mail communications may be vulnerable to interception by unauthorized<o:p></o:p></pre>
<pre>parties. If you do not wish us to communicate with you by e-mail, please<o:p></o:p></pre>
<pre>notify us at your earliest convenience. In the absence of such<o:p></o:p></pre>
<pre>notification, your consent is assumed. Should you choose to allow us to<o:p></o:p></pre>
<pre>communicate by e-mail, we will not take any additional security measures<o:p></o:p></pre>
<pre>(such as encryption) unless specifically requested.<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
</div>
</body>
</html>
<pre>The contents of this message may contain confidential and/or privileged
subject matter. If this message has been received in error, please contact
the sender and delete all copies. Like other forms of communication,
e-mail communications may be vulnerable to interception by unauthorized
parties. If you do not wish us to communicate with you by e-mail, please
notify us at your earliest convenience. In the absence of such
notification, your consent is assumed. Should you choose to allow us to
communicate by e-mail, we will not take any additional security measures
(such as encryption) unless specifically requested.