Dear Daniel,
Thank you for your answer. I find the case that memleak happen after only
this case: prepaid call sip-gsm timeout when enable cnxcc, other case
memleak does not happen.
Test scenario:
1. A calls B
2. A is playing ringback tone and B is playing ringing tone
3. Ethernet from Kamailio to
Hello,
4.1 is compiled with memory debug on, set:
memlog=0
children=2
in kamailio.cfg, restart and do some calls. Then stop kamailio and send
the messages from syslog at the moment of shutting down kamailio. Used
memory chunks should be there and maybe we can spot the leak.
Another point, are y
Hello,
there is no indication yet where is the leak, so you have to upgrade
core and all modules you are using.
If you configured with 4GB of memory, then there is a leak. You say you
have your own customized modules, you should investigate your changes
first to see if there are leaks.
There are
Hello Daniel,
Thank you so much for your answer
I want to ask you something before upgrade kamailio, currently we are
config shared memory size is 4GB, and normal kamailio only use 12-14 MB. We
are changed some module for our purpose like using cnxcc (using for
prepaid) and alias_db module for cal
Hello,
upgrade to kamailio 4.1.8, because there are fixes since 4.1.5. Same
config and database structure are used in all 4.1.x releases, therefore
you just need to deploy the new version and restart.
Also, be sure you have allocated sufficient shared memory (-m command
line parameter), by defaul
Hi everyone,
I am using Kamailio-4.1.5. Sometime kamailio was crash because memory leak.
Log when out of mem
May 2 09:49:00 vnpsip01 /usr/local/sbin/kamailio[30821]: ERROR: tm
[t_lookup.c:1472]: t_newtran(): ERROR: t_newtran: new_t failed
May 2 09:49:00 vnpsip01 /usr/local/sbin/kamailio[30821]
