I've had a similar problem. In my case solution was setting up static ip, instead of DHCP-static binding. It looks like freeswich managed to start before DHCP-lease was received, so freeswitch does not have any ip to bind to when it starts. вс, 29 сент. 2019 г. в 12:38, William Colls <william@williamcollsassoc.ca>:
Freeswitch 1.10.1, debian 10.0
I am getting the following error message when I try to start freeswitch:
2019-09-29 04:10:46.557595 [ERR] sofia.c:3245 Error Creating SIP UA for profile: internal (sip:mod_sofia@192.168.51.116:5060;transport=udp,tcp) The likely causes for this are: 1) Another application is already listening on the specified address. 2) The IP the profile is attempting to bind to is not local to this system.
A port scan tells me that no other process is listening to 5060, and $${local_ip_v4} is set to the correct value (192.168.51.116).
What else should I look for/at to resolve the issue?
This only started yesterday, and I am not aware of changing anything that might be related. But obviously something did get changed.
Thank you for your time and suggestions.
William
_________________________________________________________________________
The FreeSWITCH project is sponsored by SignalWire https://signalwire.com Enhance your FreeSWITCH install with disruptive priced SMS and PSTN services. Build your next product on our scalable cloud platform.
Join our online community to chat in real time https://signalwire.community
Professional FreeSWITCH Services sales@freeswitch.com https://freeswitch.com
Official FreeSWITCH Sites https://freeswitch.com/oss https://freeswitch.org/confluence https://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 https://freeswitch.com