Pulling Trace Logs to identify call loops

[shikamarunara]

I need to create some trace logs for a call loop that is happening between two clusters via non-gatekeeper controlled Intercluster trunk.  Can anyone recommend a best trace is best for this?  This is on CUCM 8.0.

[clileikis · Accepted solution]

Hi there,

You will want to enable Detailed Call Manager SDI traces on both clusters which will give you all of the information regarding inbound and outbound call signaling between both clusters.

HTH,

Chris

[shikamarunara]

Thanks, Chris.

[jmoneste · Accepted solution]

Additionally after you download the traces then use Triple combo and drag the files to the program. Tick the DA (Digit Analysis) and you will see only the calls made. If you see something like this:

Calling 9721252154 called 7894

Calling 9721252154 called 7894

Calling 9721252154 called 7894

Calling 9721252154 called 7894

Calling 9721252154 called 7894

Calling 9721252154 called 7894

Calling 9721252154 called 7894

Then that is the loop. You have identified the calling and called number. Then turn on (if not already) the DNA feature and place the calling and called number on it. It will tell you the devices hit therefore you will be able to make the changes to stop the llop

Triple combo tool.

http://www.employees.org/~tiryaki/tc/

[shikamarunara]

Thank you, Jonathan.  I had already seen people recommend Tripple Combo while working through this issue, I appreciate the feedback.  I'm new to pulling SDI traces, can you tell me where I can find them under the Trace configuration? 

[jmoneste · Accepted solution]

Sure,

Please keep this guide handy to use. This is the same for all Linux versions.

http://www.cisco.com/en/US/partner/products/sw/voicesw/ps556/products_tech_note09186a0080094e89.shtml#calm

This guide explains as well how to collect the traces as well.

[shikamarunara]

Thank you, Jonathan.  This is very helpful.

[shikamarunara]

Jonathan/Chris,

     Thank you very much for your help.  As it turns out, we are using an ICT between two clusters to facilitate a migration.  We have duplicate route patterns on both clusters since the dial plans will temporarily overlap.  Well, as it turns out, the SDI trace revealed that a caller on one side misdialed a number going to the other side, the route patterns created a loop.  Tripple Combo made reading the traces super easy and solved my problem.  Thanks again!

[jmoneste · Accepted solution]

A pleasure sir.