[Freeswitch-users] TLS initialization failures
jason at jasonjgw.net
Tue Apr 28 21:22:19 PDT 2009
I know this isn't the place to report bugs; unfortunately, the Jira Web
interface isn't working for me due to accessibility issues. (If there is an
alternative way to submit reports that could be efficiently handled by the
developers, let me know).
A few weeks ago I reported problems with the initialization of multiple SIP
profiles for which TLS was enabled. At the time, I suspected the underlying
cause was an attempt to bind to port 5061 under IPv4 and IPv6 separately.
It turns out, however, that even if the TLS ports in all of the profiles are
distinct, one or more of the profiles often fails to start when FreeSWITCH is
first loaded. Running sofia profile start <profile-name> thereafter always
succeeds; thus I suspect a subtle timing problem. I am having trouble
reproducing this with the Sofia debugging variables enabled.
I also have a core file that was generated when FreeSWITCH crashed while
attempting to initialize TLS during startup. I can supply a backtrace if this
would help. The segfault is not reliably reproducable, but it has happened
more than once, most recently under rev. 13081, for which I kept the core
I am running Debian Sid. A colleague with Fedora 10 has also been able to
reproduce the TLS initialization bug.
More information about the FreeSWITCH-users