<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt">A 404 from the cluster would normally indicate that the number is not found within the CUCM cluster itself.<br><br>Enable <span class="content">Detailed
</span>level tracing for CCM on all concerned servers and initiate a few test calls until you get the issue. Then stop the tracing and collect the files via RTMT. This may be service impacting depending on the volume of calls and end points on the respective servers.<br><br>I can't recall off the top of my head whether an unregistered IP phone would also give a 404 error message if there is no call forward unregister number to redirect it to voicemail but that might be worth checking.<br><br>Have a look at the traces and let us know if you require any help deciphering it.<br><div><br></div> <div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"> <div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"> <div dir="ltr"> <hr size="1"> <font face="Arial" size="2"> <b><span style="font-weight:bold;">From:</span></b> "Heim, Dennis" <Dennis.Heim@wwt.com><br> <b><span style="font-weight:
bold;">To:</span></b> "Zoltan.Kelemen@Emerson.com" <Zoltan.Kelemen@Emerson.com>; "cisco-voip@puck.nether.net" <cisco-voip@puck.nether.net> <br> <b><span style="font-weight: bold;">Sent:</span></b> Monday, April 15, 2013 5:28 PM<br> <b><span style="font-weight: bold;">Subject:</span></b> Re: [cisco-voip] How to trace failed calls on the CUCM?<br> </font> </div> <div class="y_msg_container"><br>
<div id="yiv275743443"><style><!--
#yiv275743443
_filtered #yiv275743443 {font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;}
_filtered #yiv275743443 {font-family:Tahoma;panose-1:2 11 6 4 3 5 4 4 2 4;}
#yiv275743443
#yiv275743443 p.yiv275743443MsoNormal, #yiv275743443 li.yiv275743443MsoNormal, #yiv275743443 div.yiv275743443MsoNormal
{margin:0in;margin-bottom:.0001pt;font-size:11.0pt;font-family:"Calibri", "sans-serif";}
#yiv275743443 a:link, #yiv275743443 span.yiv275743443MsoHyperlink
{color:blue;text-decoration:underline;}
#yiv275743443 a:visited, #yiv275743443 span.yiv275743443MsoHyperlinkFollowed
{color:purple;text-decoration:underline;}
#yiv275743443 p.yiv275743443MsoAcetate, #yiv275743443 li.yiv275743443MsoAcetate, #yiv275743443 div.yiv275743443MsoAcetate
{margin:0in;margin-bottom:.0001pt;font-size:8.0pt;font-family:"Tahoma", "sans-serif";}
#yiv275743443 span.yiv275743443BalloonTextChar
{font-family:"Tahoma", "sans-serif";}
#yiv275743443 span.yiv275743443EmailStyle19
{font-family:"Calibri", "sans-serif";color:windowtext;}
#yiv275743443 span.yiv275743443EmailStyle20
{font-family:"Calibri", "sans-serif";color:#1F497D;}
#yiv275743443 .yiv275743443MsoChpDefault
{font-size:10.0pt;}
_filtered #yiv275743443 {margin:1.0in 1.0in 1.0in 1.0in;}
#yiv275743443 div.yiv275743443WordSection1
{}
--></style><div><div class="yiv275743443WordSection1"><div class="yiv275743443MsoNormal"><span style="color:#1F497D;">Can your cube actually reach your cucm nodes?</span></div><div class="yiv275743443MsoNormal"><span style="color:#1F497D;"> </span></div><div><div class="yiv275743443MsoNormal"><b><span style="color:black;">Dennis Heim | </span></b><b><span style="font-size:10.0pt;font-family:"Arial", "sans-serif";color:black;">Sr. Unified Collaboration Team Lead</span></b><b><span style="color:black;"></span></b></div><div class="yiv275743443MsoNormal"><span style="color:black;">World Wide Technology | 314.212.1814 | <a rel="nofollow" ymailto="mailto:dennis.heim@wwt.com" target="_blank" href="mailto:dennis.heim@wwt.com">dennis.heim@wwt.com</a><b></b></span></div><div class="yiv275743443MsoNormal"><span style="color:black;">“Creating Impact, Ignition & Scalability”</span></div></div><div class="yiv275743443MsoNormal"><span
style="color:#1F497D;"> </span></div><div><div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in;"><div class="yiv275743443MsoNormal"><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:cisco-voip-bounces@puck.nether.net] <b>On Behalf Of </b>Zoltan.Kelemen@Emerson.com<br><b>Sent:</b> Monday, April 15, 2013 11:18 AM<br><b>To:</b> cisco-voip@puck.nether.net<br><b>Subject:</b> [cisco-voip] How to trace failed calls on the CUCM?</span></div></div></div><div class="yiv275743443MsoNormal"> </div><div class="yiv275743443MsoNormal">Hi,</div><div class="yiv275743443MsoNormal"> </div><div class="yiv275743443MsoNormal">I’m trying to trace the reason some calls fail on my CUCM cluster, inbound from a SIP trunk. </div><div class="yiv275743443MsoNormal">
</div><div class="yiv275743443MsoNormal">The CUBE says it gets 404 from the cluster, but doing a DNA trace on the cluster says that call from the trunk should be routed.</div><div class="yiv275743443MsoNormal">I was trying to locate the call with a session trace using RTMT, but I can’t find the call. It just does not seem to appear in the list of calls (they may be for completed calls only?).</div><div class="yiv275743443MsoNormal"> </div><div class="yiv275743443MsoNormal">Any ideas would be welcome. </div><div class="yiv275743443MsoNormal"> </div><div class="yiv275743443MsoNormal">Thanks,</div><div class="yiv275743443MsoNormal"> </div><div class="yiv275743443MsoNormal"><b><span style="font-family:"Arial", "sans-serif";color:#0F245F;">Zoltan Kelemen</span></b><b><span style="font-size:10.0pt;font-family:"Arial", "sans-serif";color:#0F245F;"><br></span></b><span
style="font-size:10.0pt;font-family:"Arial", "sans-serif";color:#666666;">Emerson</span><span style="color:#1F497D;"></span></div><div class="yiv275743443MsoNormal"> </div></div></div></div><br>_______________________________________________<br>cisco-voip mailing list<br><a ymailto="mailto:cisco-voip@puck.nether.net" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br><br><br></div> </div> </div> </div></body></html>