7 Nov
2018
7 Nov
'18
1:17 a.m.
Am Dienstag, 6. November 2018, 23:11:41 CET schrieb Kevin Olbrich:
Hi Kevin,
I like this comparison, compiler log. ;-)
But you are right, it is really verbose in the debugging log level. I am not
aware of a dedicated guide to this.
But you should be able with grep to filter the output of certain modules (look
at the prefix).
Another idea is to enable the configuration debugger module, but this will
help more if it is a cfg issue, and not a module issue. Have a look to the
module README for more details about it capabilities.
Best regards,
Henning
--
Henning Westerholt - https://skalatan.de/blog/
Kamailio services - https://skalatan.de/services
Kamailio security assessment - https://skalatan.de/de/assessment
you could
control the time when the specific not-working phone send a
REGISTER. Then you can enable the debugging for a few seconds during this
time, and then deactivate it again. This should work even on a production
server. Debugging it on a test server is of course an even better way.
even with an isolated setup (which this one currently is) I get several
hundred lines per transaction.
Comparing the debug of asterisk against kamailio, asterisk is much more
readable for me. Maybe I need more training ;-)
Is there a starter guide to kamailio.cfg debug? It very much looks like a
compiler log.