To: sr-users@lists.sip-router.org <mailto:sr-users@lists.sip-router.org>
Subject: Re: [SR-Users] Regd. MAX_LDG_LOCKS
Message-ID: <52ef28c1.5010...@evaristesys.com
<mailto:52ef28c1.5010...@evaristesys.com>>
Content-Type: text/plain; charset=windows-1252; format=flowed
On 0
Hello,
it is not a really necessary to increase the value of the locks. For
better performances you can do it, but again, it is not a must.
Cheers,
Daniel
On 04/02/14 06:50, Shankar wrote:
Hi,
Can someone clarify here please?
Regards,
Shankar
*From:*Shankar [mailto:shankar...@plintron.c
Hi,
Can someone clarify here please?
Regards,
Shankar
From: Shankar [mailto:shankar...@plintron.com]
Sent: Monday, February 03, 2014 10:53 AM
To: 'SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - Users
Mailing List'
Subject: Regd. MAX_LDG_LOCKS
Hello,
Can anyone
Hi Alex,
We set the hash size to 32 MB and found that the hash size is not the same
as configured one. At the max it was taking 64KB.
Regards,
Shankar
Date: Mon, 03 Feb 2014 00:27:29 -0500
From: Alex Balashov
To: sr-users@lists.sip-router.org
Subject: Re: [SR-Users] Regd
On 02/03/2014 12:22 AM, Shankar wrote:
Also we found that in ‘dialog.c’ the variable dlg_hash_size should be
‘unsigned int’. Hope this will be taken care in next release of Kamailio.
How did you arrive at that conclusion?
--
Alex Balashov - Principal
Evariste Systems LLC
235 E Ponce de Leon A
Hello,
Can anyone brief about MAX_LDG_LOCKS in dlg_hash.c?
Should I increase the value of MAX_LDG_LOCKS (hardcoded to 2048) if the hash
size is increased?
Also we found that in 'dialog.c' the variable dlg_hash_size should be
'unsigned int'. Hope this will be taken care in next release
