01-09-2019 12:47 AM
I am using Translator X for analyzing "debug ccsip all" command output
Unable to find any thing on Translator X other hand when i open same logs in notepad++ sip messages are found
I configured syslog on my machine
conf Ter
logging (syslog server IP)
service timestamp debug datetime localtime
service log datetime local time
logging facility local3
logging trap debugging
Solved! Go to Solution.
01-11-2019 10:51 PM
Dear Vijay,
After some struggle i was finally able to get the correct output in Tranlator.
The problem is the Prefix each message has from the syslog, we need to remove the same so that TranslatorX can correclty parse the data.
I have used the column mode of Notepad++ to delete the preceding data
STEP 1 :- Open file in Notepad++ and make sure Word Wrap is Turned Off
STEP :-2
Use Column Mode Continue holding “Shift” and “Alt” while using the “Down” and “Right” arrow keys on your keyboard to select the text as desired. https://www.technipages.com/notepad-column-mode
Finally Open the modified file in Translator. Now As the Millisecond parameter is absent the Messages might be out of sequence
Finally If you think issue is resolved then rate & mark answer as correct.
Thanks,
Haris
01-10-2019 06:17 AM
Can you send or attach your ccsip all debug here?
01-11-2019 07:05 AM
01-11-2019 07:17 AM
You will need to run your debug with msec-level timestamps in order for them to be imported into TranslatorX. If there are additional problems after that, let us know and we'll give it a look.
01-10-2019 07:08 AM
I've run into issues with SIP debugs not importing into TranslatorX when the timestamps are not set correctly. Are these on your router?
service timestamps debug datetime localtime msec
service timestamps log datetime localtime msec
01-10-2019 09:57 PM
01-11-2019 04:08 AM - edited 01-11-2019 06:03 AM
You are missing the "msec" on the end of the commands you showed in your earlier post. What little documentation there is for TranslatorX says that is a requirement. (And it's how I've made it work.)
01-11-2019 07:30 PM
01-10-2019 08:03 AM
You are mentioning syslog. I'd expect your syslog to prefix/handle/format the messages in a way that TranslatorX doesn't handle.
Try pulling the log from either the buffer or monitor, verify that it is correctly handled by TranslatorX and modify the syslog-configuration as needed.
01-11-2019 04:58 AM
01-11-2019 09:47 AM
I am able to see the SIP Messages in TranslatorX. My version is 11.5 So upgrade your TranaslatorX.
Also here you can see that TranslatorX is unable to process the file properly this is probably due to Milliseconds value missing. Please regenerate the logs with milliseconds timestamps.
01-11-2019 07:25 PM
Hello Harris,
Thanks for replay..Will ad mesc parameter next time onward while collecting sip debug on syslogs .
i exactly see the same what screen you share on TranslatorX ..but why Node/Interface ..Remote Device IP are not not displayed here ..
01-11-2019 10:51 PM
Dear Vijay,
After some struggle i was finally able to get the correct output in Tranlator.
The problem is the Prefix each message has from the syslog, we need to remove the same so that TranslatorX can correclty parse the data.
I have used the column mode of Notepad++ to delete the preceding data
STEP 1 :- Open file in Notepad++ and make sure Word Wrap is Turned Off
STEP :-2
Use Column Mode Continue holding “Shift” and “Alt” while using the “Down” and “Right” arrow keys on your keyboard to select the text as desired. https://www.technipages.com/notepad-column-mode
Finally Open the modified file in Translator. Now As the Millisecond parameter is absent the Messages might be out of sequence
Finally If you think issue is resolved then rate & mark answer as correct.
Thanks,
Haris
01-13-2019 09:19 PM
Thanks, Harris....
This is what output i tried for long time ...
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide