Maybe this is something https://cway.cisco.com/tools/CollaborationSolutionsAnalyzer/
-- Florian Krößbacher [email protected] Am 17. Mai 2018, 18:12 +0200 schrieb Lelio Fulgenzi <[email protected]>: > Awesome info! Thanks. > > My hope is to just get an idea of what’s going on. But I agree, I usually > tend to go to the TAC for more detailed help. > > > --- > Lelio Fulgenzi, B.A. | Senior Analyst > Computing and Communications Services | University of Guelph > Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON | N1G > 2W1 > 519-824-4120 Ext. 56354 | [email protected] > > www.uoguelph.ca/ccs | @UofGCCS on Instagram, Twitter and Facebook > > > From: Anthony Holloway <[email protected]> > Sent: Thursday, May 17, 2018 10:56 AM > To: Ryan Huff <[email protected]> > Cc: Lelio Fulgenzi <[email protected]>; voyp list, cisco-voip > ([email protected]) <[email protected]> > Subject: Re: [cisco-voip] what are the cool kids using to read CUCM logs > nowadays? > > I also second TranslatorX as my first stop. Make sure to have CDR enabled on > the cluster, and just dump all of the compressed logs into it, pop open the > Call List, find your call, double click it to see some good high level > details (disconnect cause, duration, codecs, dtmf, ip addresses, device > names) about the call, then generate a filter if you need to see the ladder > diagram. I don't use it for more complex log analysis, for that I sail over > to Ryan's island and ask to use his Windows ME box and fire up Notepad++. > > The find in files feature is amazing, but you will need to un-compress the > logs first (RTMT can do this for you). The highlighting is helpful, and if > you know regex, you're golden. PS Some folks in TAC have syntax highlighting > for CM traces in Notepad++, but so far they have not been willing to share it > with me. > > Which brings me to my final point. Reading CM traces is not an easy effort, > and you should give yourself a time limit, then just open a TAC case (or send > it to Daniel Pagan; the human parser). The Troubleshooting IP Telephony book > is pretty good, and there's a few nuggets on the mailing list, but really, if > you're not working in TAC, or a TAC like job function, you're swimming up > stream. You might have better luck performing controlled experiments, > swapping components in and out to isolate the root cause. > > With that said, you'll never get better at log parsing, if you're not log > parsing. So, if you're sick and twisted like Ryan and Daniel able to devote > some time to log parsing, go for it. > > On Thu, May 17, 2018 at 8:33 AM Ryan Huff <[email protected]> wrote: > > quote_type > > For the money (free) and usability; yeah, I’d go with Paul’s TranslatorX. > > Especially if your troubleshooting call behaviors because of its ability to > > organize by session ID and parse out OPTIONS messages. > > > > - Geany text editor does a good job because of its ability to highlight > > similar entities (Linux, not sure if there is a Windows port). > > > > - Notepad++ if I’m on an island and that’s all I have. > > > > Really though, anything that can parse the > > character will work in a pinch but you’ll have to deal with the default > > chronologically logged readout. Whereas something like TranslatorX has more > > purposeful filters that allow you to follow the call’s message stack a > > little easier. > > > > -Ryan- > > > > On May 17, 2018, at 09:17, Lelio Fulgenzi <[email protected]> wrote: > > > > > > I need to do some log analysis to see why a certain group of fax machines > > > are getting reorder tone when trying to dial a number. I’ve got some > > > other troubleshooting steps to do first, but I have a feeling I’m going > > > to have to take a look. > > > > > > Is it translator X still? > > > > > > --- > > > Lelio Fulgenzi, B.A. | Senior Analyst > > > Computing and Communications Services | University of Guelph > > > Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON | > > > N1G 2W1 > > > 519-824-4120 Ext. 56354 | [email protected] > > > > > > www.uoguelph.ca/ccs | @UofGCCS on Instagram, Twitter and Facebook > > > > > > <image001.png> > > > > > > _______________________________________________ > > > cisco-voip mailing list > > > [email protected] > > > https://puck.nether.net/mailman/listinfo/cisco-voip > > _______________________________________________ > > cisco-voip mailing list > > [email protected] > > https://puck.nether.net/mailman/listinfo/cisco-voip > _______________________________________________ > cisco-voip mailing list > [email protected] > https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________ cisco-voip mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-voip
