[Freeswitch-users] Getting 503 when starting automatically via systemd

[freeswitch.opencode at spamgourmet.com]

I'm using Arch Linux (specifically Arch Linux ARM on a Raspberry Pi Zero). I'm successfully done a make and install for freeswitch 1.6.6 and when I run it manually (freeswitch -nonat), it works fine. Also, when I start it manually via systemd (systemctl start freeswitch), it still works fine.

However, when I enable freeswitch.service to start automatically and reboot, the freeswitch log shows 503 errors trying to register out to my gateway, and my internal client (an Obi200) gets a 503 when trying to register in to FreeSWITCH as well; this keeps happening repeatedly (waiting 30 seconds and then failing again). However, if I restart the service (systemctl restart freeswitch), connectivity then starts working.

Would the 503 be what's reported up if there's no network connectivity either way?

I'm using the Debian systemd *freeswitch.service file (with very minor tweaks for my configuration on Arch Linux). Has anyone encountered this problem before (on Debian, Arch Linux, or elsewhere)? The overall .service file is very similar to sshd.service, which doesn't have connection problems, so my guess is there's something specific to FreeSWITCH going on. If this is Arch Linux-specific and I ask in their forums, is there anything different about how FreeSWITCH handles connectivity (perhaps caching some kind of handle) that would help point things in the right direction?

Thanks,

David