|Subject:||Re: [External]Re: Getting OSIP_TRACE logs in a file|
|Date:||Mon, 4 Jan 2021 01:14:53 +0100|
I found osip_trace_initialize_func wherein I can provide my own callback function.
This way I can log logs to my application log file.
Le jeu. 31 déc. 2020 à 18:56, Kumar, Puneet (Puneet) <email@example.com> a écrit :
Happy New Year!!
I just linked “-losipparser2” to my C++ application.
I am getting these output in my console (docker logs)
<osip_messa: 352> Final CRLF is missing
I am not sure for which header this complain is generated, any way to get more generic info so that problem header & message is printed in logs.
A sip message needs to end with CRLFCRLF (twice CLRF). So the log means the sip message wasn't complete.
How can I redirect these logs to a file?
Also will file rollover to a new file when its size is up to its limit.
There are API to create a file with osip, but very limited and not performant, so the easiest is to use syslog and syslog rules.
The only way to have rollover is also to use syslog.
Best to all for 2021!
|[Prev in Thread]||Current Thread||[Next in Thread]|