I've read the ipv6(7) manual page now.
Unfortunately
echo 1 > /proc/sys/net/ipv6/bindv6only
doesn't solve the problem as the manual page suggests it should:
___
Freeswitch-users mailing list
Freeswitch-users@lists.freeswitch.org
http://lists.freeswitc
Jason White wrote:
> It looks like an operating system issue to me.
Furthermore, the following message on linux-kernel appears relevant.
http://linux.derkeiler.com/Mailing-Lists/Kernel/2005-03/3988.htm
>From what I have been able to ascertain, Red Hat/Fedora kernels don't seem to
give rise to th
Here's a log.
OS: Debian Sid, kernel 2.6.26.
This happens when FreeSWITCH is started during the boot process from the init
scripts, as well as subsequently if it is shut down and restarted.
Sometimes it is the internal profile that fails, rather than internal-ipv6, as
here.
tport_tls_init_mast
You didn't include enough info ...
Distro, OS or sofia log...
It could be many things... socket lingering is my best guess.
/b
On Mar 23, 2009, at 1:31 AM, Jason White wrote:
> I have TLS enabled in my internal and internal-ipv6 profiles as per
> the stock
> configuration.
>
> When FreeSWIT
I have TLS enabled in my internal and internal-ipv6 profiles as per the stock
configuration.
When FreeSWITCH is started, sometimes either of the profiles fails to
initialize, with an "Unable to create SIP UA for profile" error in the log. If
I then start the profile manually
sofia profile start
f
