On 11/10/09 12:26 PM, Henning Westerholt wrote:
Hi Henning!
Well, it's more like this. A customer sends an invite, which is really to himself (failboat). So I send it to him (directly or via a PSTN gateway, depending on the routing setup). Which causes (for example when their PBX has a forwarding) a new invite to me, new call leg. Untill one of both sides dies or is congested. That's normally not Kamailio, so that's the good news. Only thing then is the memory usage after this spike. I'm also running spike, so in the end I just send them 480's back.
Ok, i understand. So its more a temporary over load condition that you face.
Yes, exactly. And it's not really overload, the machine can easily handle it, it's not loaded at all, even if customers do "interesting" stuff. But it's just that the memory grows and never seems to shrink again.
We did an upgrade to 1.5 in the last months on some of our production systems, without any notable problems. Some other systems we've needs some more time before they can run on 1.5, especially because of the database changes you also mentioned. If you update make sure that you use the latest 1.5 version/ stable branch. 3.0 will be indeed interesting, looking forward to this.
Me too. I think I'll actually wait for 3.0.x or 3.1 and then make one big upgrade. Night maintenance is not my favourite hobby so I'll make a big step. I think the current 1.4.4 I'm running doesn't have any acute problems or crashes so it's fine. :)
Thanks for your help and explanations (and ofcourse your work on Kamailio)!
/Robin