Thanks for your suggestions, I finally found my problem.
I used a xml file for the SIPp were no branch parameter was included in the VIA header (which is not RFC compliant). With such messages the Kamailio 3.x.x seems to have problems whereas Kamailio 1.5.0 is doing fine. I will protect my Kamailio against such messages.
On 02.03.2012 17:32, Klaus Darilion wrote:
Or check if it is a memory leak and fix it ;-)
On 02.03.2012 15:31, davy van de moere wrote:
You can attempt to give Kamailio more memory to use, by adding the options -M and -m . If you have enough memory a -M 10240 and -m 1024, should give you more transaction capabilities.
Op 2 maart 2012 13:26 schreef Klaus Darilion <klaus.mailinglists@pernau.at mailto:klaus.mailinglists@pernau.at> het volgende:
See http://kamailio.org/dokuwiki/__doku.php/troubleshooting:__memoryhttp://kamailio.org/dokuwiki/doku.php/troubleshooting:memory how to debug memory problems.
Using "top" does not reveal memory problems, as Kamailio allocates the defined memory (shared + private per process) during startup. Thus, the system memory consumptions should be constant (except some modules use libraries which use system memory, eg. postgres library) regards Klaus On 02.03.2012 13:01, Martin Tichatschek wrote: rio consists of two SIPp servers (a UAC and a UAS) and the Kamailio in the middle proxying the SIP traffic. The UAC sends 300 calls per second (INVITE, 100, 180, 200,ACK) and releases t
_________________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-usersmailing list sr-users@lists.sip-router.org mailto:sr-users@lists.sip-router.org http://lists.sip-router.org/__cgi-bin/mailman/listinfo/sr-__users http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users