On Wednesday 07 October 2015 19:54:43 Daniel-Constantin Mierla wrote:
Can you add log_prefix to print the callid, message type (request/reply) and cseq header with each log message? That should reveal what sip message is processed when such case happens.
Will do.
I will look also at the code, maybe the stats are not decreased in such case. If the transactions are staying in memory, then the share memory usage is going to increase as well. Have you observed share memory evolution?
Yes, the (shared) memory used shows the same trend as tm.current/number of dialogs. See attachment. Interesting is the spike in usage a couple of hours before the problems appear. I'll try to see what the cause was.