Hi Rajesh,
The only overhead added by "log_level = 4" are the extra logs
themselves. And, yes, DEBUG mode is quite verbose and could lead to a
lot of output, easily filling up entire GB within just a few hours.
As with all such questions, the only correct answer is: "it depends".
For
HI Liviu,
Thanks for the reply. Yes opensips does start under root with that param set,
But it doesn't appear to be using the spoofed socket that I configured to do
the ping, Still trying to use whats in the usrloc Socket info.
On Tuesday, 15 May 2018, 10:47:16 AM GMT+5:30, Liviu Chircu
Even more, you can instruct OpenSIPS to listen all existing (at startup)
IPs:
listen= udp:*:5060
NOTE that this approach does not cope with IP changes during runtime!
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
OpenSIPS Summit 2018
Hi Schneur,
Let me know if after fixing your compiling you still experience this crash.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
OpenSIPS Summit 2018
http://www.opensips.org/events/Summit-2018Amsterdam
On 05/06/2018 06:53 PM, Schneur
Hi,
First of all, carefully read the logs you get as they provide *a lot* of
useful hints.
The key log is "SSL3_GET_CLIENT_CERTIFICATE:no certificate returned" -
that means the other party did not presented a SSL ceritificate, while
your TLS setup for that domain do require one (see the
Hi,
I was actually able to isolate this to the siptrace module and then I
remembered this thread [1] from February. Was this issue ever resolved? It
looks like it was reported in 2.3.2, but we are still seeing it in 2.3.3.
[1] -
Hi,
We have recently upgraded to OpenSIPs 2.3.3 and after deploying to our
production environment we have found a significant memory leak. The leak is
being reported by OpenSIPS’ statistics only; the used memory of the machine
itself is not increasing.
I believe I have been able to reproduce
