Any idea?
I have shared my tls configuration with you in my previous post, and as I said, that configuration works with kamailio 3.2.4. After silence of 4 days, do you confirm that it is a bug? If so, how can it be solved? Any suggestion?

On Thu, Nov 1, 2012 at 4:23 PM, Ramazan Yilmaz <ramazan.cs@gmail.com> wrote:
In my kamailio configuration, I already have "#!define WITH_TLS". And some more about my configuration:

listen=tls:XX.XX.XXX.XX:5061

#!ifdef WITH_TLS
enable_tls=yes
#!endif

#!ifdef WITH_TLS
loadmodule "tls.so"
#!endif

#!ifdef WITH_TLS
# ----- tls params -----
modparam("tls", "config", "/usr/local/kamailio-3.3/etc/kamailio/tls.cfg")
#!endif

And my tls.cfg is,

[server:default]
method = SSLv23
verify_certificate = no
require_certificate = no
private_key = /usr/local/kamailio-3.3/etc/kamailio/kamailio.key
certificate = /usr/local/kamailio-3.3/etc/kamailio/kamailio.pem

[client:default]
verify_certificate = yes
require_certificate = yes

I have just installed kamailio 3.2.4 on some other server to see whether the problem is with my configuration/my system or with kamailio release. I again installed Ubuntu, and I installed the requested packages via apt-get, as I had done on problematic system. I used exactly the same configuration file, except changing the domain/ip values. And it worked. Then I used the same configuration file on some other versions of Ubuntu server, and it worked again. So, it really seems as a bug in kamailio.

It seems the worker children cannot be forked for some reason at startup, so I enabled WITH_DEBUG directive and restarted the kamailio. The output is attached to this mail. I hope it helps.

Best,