<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">Negative feed back in the form of bashing. I’ve had bad experiences before trying to do nice things.<div><br></div><div> I don’t mind things to be fixed modified or changed or if it broke.<div>I know there is going to be things people find and that info is great to make it better. </div><div><br></div><div>Hope that makes sense?</div><div><br></div><div>To answer your question if it is working correctly it does both.</div><div>It will copy the complete sdl file if it finds a match in it It will create a new file with just the detected lines in it for the call. And it will also create a file for each server that was involved </div><div><br></div><div><br><br><div id="AppleMailSignature"><div><br></div>Kent</div><div><br>On Mar 31, 2018, at 19:00, Anthony Holloway <<a href="mailto:avholloway+cisco-voip@gmail.com">avholloway+cisco-voip@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr">What did you mean by, don't bother with negative feedback?<div><br></div><div>Does your solution just copy the SDL files which contain lines pertaining to the call, or does it strip out the lines pertaining to the call and create a whole new log file containing just that call?<br><br><div class="gmail_quote"><div dir="ltr">On Fri, Mar 30, 2018 at 10:29 PM Kent Roberts <<a href="mailto:kent@fredf.org">kent@fredf.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word;line-break:after-white-space"><div>Hi all. </div><div><br></div><div>So I am one of the few people that have worked with CUCM since Cisco started with CallManager, back in 2000’s. As such, there is one thing that I have always hated, and that was reading the logs cause there is just soooooo much stuff there.</div><div><br></div><div>I wrote a set of scrips a couple years ago, that is designed to parse the RTMT logs from CUCM and return only data based on the call.</div><div><br></div><div>After a few people begging for a copy of it, I decided to make it a real program.</div><div><br></div><div>If you find it useful, please contribute to my tax deductible non-profit. (Facebook has an easy donation program. <a href="Https://www.facebook.com/projecttesn" target="_blank">Https://www.facebook.com/projecttesn</a>)</div><div><br></div><div><br></div><div>If you have Ideas for other stuff you would like to see let me know, I will see what I can do.</div><div><br></div><div><br></div><div>So the program works or should work like the following. (It is beta right now, as I am trying to make it self contained instead of scrips)</div><div><br></div><div>Put in the ANI or DNIS. (Right now I know the extension on cucm works, not sure about the other side yet). Or the SIP ID. (This might be hit or miss at the moment)</div><div><br></div><div>Push the button to start. Select the location of the RTMT files. (Gz’s are ok, it will unpack them) </div><div><br></div><div>It will create a -output on the end of the path you provide with the data.</div><div><br></div><div>It will collect the calllog files, and put the revenant data into a file. Once it finds matches it will start to assemble the data into a file, and copy the SDL files that are tied to it.</div><div><br></div><div>The goal is to get only the data related to the call provided, so tracking down what went on is much easier.</div><div><br></div><div>Once complete, you can or should be able to load the file with translatorx and have a smaller file to work with.</div><div><br></div><div>Find it here. Please note, I have restricted the running time, as it will need some updates. Please feel free to help me make it better. If its negative feedback, please don’t bother.</div><br><div><a href="http://www.projecttesn.org/ckrparse4rtmt.exe" target="_blank">http://www.projecttesn.org/ckrparse4rtmt.exe</a></div><div><br></div><div>FYI. This is running with a test CERT, and right now not signed, so windows defender may pop up and Symantec will have a cow…. Put should not be any worries.</div></div>_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" rel="noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
</blockquote></div></div></div>
</div></blockquote></div></div></body></html>