[cisco-voip] How to trace failed calls on the CUCM?

[Zoltan.Kelemen at Emerson.com]

Well, I’m experimenting with some LCR (TEHO) here, so the number should not be on the cluster as such, although there is a translation pattern in a partition reachable by the SIP trunk’s CSS.
Also, Dialed number Analyzer tells me this should work in theory. Called number is routed as expected.

The CUBE can reach the cluster, calls going to phones registered to the cluster work fine.

Thanks for the tip though, I’ll up the detail level for the traces and see what turns up.

Regards,

Zoltan Kelemen
ETS & Information Security
Implementation Engineering
w: +40 374 132356 | m: +40 757 039093

From: Rhodium [mailto:rhodium_uk at yahoo.co.uk]
Sent: Monday, April 15, 2013 9:59 PM
To: Heim, Dennis; Kelemen, Zoltan [CORP/RO]; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] How to trace failed calls on the CUCM?

A 404 from the cluster would normally indicate that the number is not found within the CUCM cluster itself.

Enable Detailed 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.

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.

Have a look at the traces and let us know if you require any help deciphering it.

________________________________
From: "Heim, Dennis" <Dennis.Heim at wwt.com<mailto:Dennis.Heim at wwt.com>>
To: "Zoltan.Kelemen at Emerson.com<mailto:Zoltan.Kelemen at Emerson.com>" <Zoltan.Kelemen at Emerson.com<mailto:Zoltan.Kelemen at Emerson.com>>; "cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>" <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Sent: Monday, April 15, 2013 5:28 PM
Subject: Re: [cisco-voip] How to trace failed calls on the CUCM?

Can your cube actually reach your cucm nodes?

Dennis Heim | Sr. Unified Collaboration Team Lead
World Wide Technology | 314.212.1814 | dennis.heim at wwt.com<mailto:dennis.heim at wwt.com>
“Creating Impact, Ignition & Scalability”

From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Zoltan.Kelemen at Emerson.com<mailto:Zoltan.Kelemen at Emerson.com>
Sent: Monday, April 15, 2013 11:18 AM
To: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: [cisco-voip] How to trace failed calls on the CUCM?

Hi,

I’m trying to trace the reason some calls fail on my CUCM cluster, inbound from a SIP trunk.

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.
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?).

Any ideas would be welcome.

Thanks,

Zoltan Kelemen
Emerson


_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20130416/313e0167/attachment.html>