VoIP Mailing List Archives

[botelist at gmail.com]

Perhaps it is even simpler.

${conf_dir}/autoload_configs/event_socket.conf.xml

probably contains a reference to "localhost" like:
<param name="listen-ip" value="localhost"/>

which /etc/hosts probably lists as
::1 localhost ip6-localhost ip6-loopback

which apparently is disabled on your host, based on the error messages like:
"Error Creating SIP UA for profile: external-ipv6 (sip:mod_sofia@[::1]:5080;transport=udp,tcp"

Solution: change
<param name="listen-ip" value="localhost"/>
to
<param name="listen-ip" value="127.0.0.1"/>
and fs_cli should be able to reach FreeSWITCH ESL port.

You can run FreeSWITCH as a console application by omitting the "-nc" switch and see the console log messages fly by on the screen, until you get fs_cli connected.

I believe these are merely the growing pains of a new system that has not been fully configured yet. Simplify the network configuration and things will work better.

"What this country needs is a good FreeSWITCH startup guide."

John Boteler
Bote Communications



-----Original Message-----
From: FreeSWITCH-users <freeswitch-users-bounces@lists.freeswitch.org> On Behalf Of Antony Stone
Sent: Thursday, 10 March, 2022 09:24
To: FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org>
Subject: Re: [Freeswitch-users] fs_cli not connecting to fs ( newbie question )

On Wednesday 09 March 2022 at 14:47:02, GN Dev2 wrote: