Good afternoon!

Can you please tell us how the Kamailio works with shared memory. The fact is that there was an accident in which Kamailio reported an error - little common memory. This happened a day later as I added the dialplan module. After that, I began to monitor the values: used_size real_used_size max_used_size free And I saw that I can not properly assess. I note that the server does not process calls, it is idle. After the server is started, the indicators are as follows: used_size: 63 real_used_size: 146 max_used_size: 146 free 106 After rebooting the module (for example, drouting, in which the data has not changed): used_size: 63 real_used_size: 193 max_used_size: 231 free 62 I found, a description, the reasons for the increase in memory after rebooting the modules, I quote "As suggested by Daniel, for carrierroute reload, we need the same amount of memory as it used to be. Block when reloading the table. " But why: 1. after increasing the memory the server frees only real_used_size 2. That that is specified as real_used_size on my observations can not be released in current of several days (probably weeks). 3.If in this state again to reboot the module (the same one that led to an increase in memory), the memory does not increase. Question: during what time should kamailio release the memory specified as real_used_size? Also what is considered as real_used_size?

-- View this message in context: http://sip-router.1086192.n5.nabble.com/Kamailio-428-memory-usage-tp161327.h... Sent from the Users mailing list archive at Nabble.com.