Re: [External]Re: Getting OSIP_TRACE logs in a file

[Aymeric Moizard]

Hi!

Sure: you can use this API, but it's not very flexible.

If you have syslog support, it will allow you much better control and performance!

As you prefer!

Regards,

Aymeric

Le dim. 3 janv. 2021 à 14:28, Kumar, Puneet (Puneet) <puneetkumar@avaya.com> a écrit :

Thanks Aymeric,

 

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.

 

Correct?

 

Thanks,

Puneet

 

From: Aymeric Moizard <amoizard@gmail.com>
Sent: Friday, January 1, 2021 1:28 AM
To: Kumar, Puneet (Puneet) <puneetkumar@avaya.com>
Cc: osip-dev@gnu.org
Subject: [External]Re: Getting OSIP_TRACE logs in a file

 

[External Sender]

 

Le jeu. 31 déc. 2020 à 18:56, Kumar, Puneet (Puneet) <puneetkumar@avaya.com> a écrit :

Hi All,

Hi!

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!

Aymeric

 

Thanks,

Puneet