Yes. I think we had a similar problem in ,I think, two situations.

1)      The file system database can get messed up.

a.       Stop FS

b.      You can clear then via rm /export/Apps/freeswitch/var/lib/freeswitch/db/*

c.       Restart FS

2)      If there is an error in the configuration files.

a.       Take a look at /export/Apps/freeswitch/var/log/freeswitch/freeswitch.xml.fsxml to see if there are any errors in XML.

You can get more details of start problem via:

                journalctl -xn

                systemctl status freeswitch.service

                if you do not get enough details, try starting FS directly and you might get more details via:

                /…/bin/freeswitch

Got a weird issue where FS isn’t starting up correctly. Looking at the logs, it appears just to be attempting to restart SIP profiles (and failing), and that’s about it. There’s no socket for fs_cli, and a simple ‘systemctl restart’ fixes it. Anyone had something like this? I’ve tried fixing it with systemd after / requires, but it hasn’t helped.