Maybe you look at all debug messages. Try with debug=2 even for WITH_DEBUG enabled.
Otherwise, the cfgtrace just prints for each executed action the config file name, line and action id/name
If that is too complex for you to look at and compare with the config file logic and see where is going on a different execution path than you would expect, then probably I cannot help more.
Daniel
On 12/4/13 1:20 PM, Mark Zeman wrote:
We are using WITH_DEBUG, so we did see the cfgtraces, but they are wholly incomprehensible to us, I'm sorry to say.
On Wed 04 Dec 2013 01:11:26 PM CET, Daniel-Constantin Mierla wrote:
On 12/3/13 5:17 PM, Mark Zeman wrote:
The SIP packets are fine - we are able to establish SIP session with a secured control channel as easily as with an unsecured one. As long as the RTPProxy doesn't get involved (i.e. as long as it's IPvX-IPvX and not IPv4-IPv6) everything works! With the RTPProxy, the connection gets established (SIP still works) but RTP only comes from one side, the caller, and even that is not relayed.
It appears that Kamailio doesn't even enter the route[IPV4V6] part of its config, for example...
If the config file is not executing the lines you would expect, then enable cfgtrace for debugger module and the details about executed lines will be printed in syslog. That should help to identify which condition is not satisfied to get to what you want to be executed.
Cheers, Daniel
I will be able to send logs tomorrow, but I can show you our config, if that might help.