This may happen if the machine has a dhcp address, and dhcp server delayed for a second during the machine startup. I opened a jira on that, but systemd doesn't seem to offer a reliable way to delay the FreeSWITCH startup.
it can happen if it failed to bind and startup or if the interface it's bound to goes away for some reason.
On Wednesday, July 13, 2016, Ahmed habiba <ahabiba@gmail.com> wrote:Hi,I face some issue, I have one FS instance that has been running for long time, today I was not able to connect and when I run “sofia status “ I get belowName Type Data State=================================================================================================external-ipv6 profile sip:mod_sofia@[::1]:5080 RUNNING (0)internal-ipv6 profile sip:mod_sofia@[::1]:5060 RUNNING (0)Which means that my lan IPV4 profile was not running I’m not sure about the reason but when I reload mod_sofia and run “sofia status” I get the below:Name Type Data State=================================================================================================external-ipv6 profile sip:mod_sofia@[::1]:5080 RUNNING (0)internal_lan profile sip:mod_sofia@192.168.1.7:5060 RUNNING (0)internal-ipv6 profile sip:mod_sofia@[::1]:5060 RUNNING (0)I’m not sure what could let a profile go down? your kind help will be appreciated.Thanks,Ahmed Habiba,
_________________________________________________________________________
Professional FreeSWITCH Consulting Services:
consulting@freeswitch.org
http://www.freeswitchsolutions.com
Official FreeSWITCH Sites
http://www.freeswitch.org
http://confluence.freeswitch.org
http://www.cluecon.com
FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org