[Freeswitch-users] Python based Event Socket Library doesn't connect to remote FreeSWITCH
krice at freeswitch.org
Tue Sep 1 21:03:39 MSD 2015
Ok lets try this again
By default FreeSWITCH mod_event_socket is the module that provides the TCP based interface for ESL on the FreeSWITCH side. By default this _only_ listens on 127.0.0.1 which is the Loopback interface and is only accessible via the destination address of 127.0.0.1 or localhost which is only accessible from the same machine running that host.
If you want to connect to if from a different machine you need to adjust the config for mod_event_socket and bind it to an interface (or IP) that is accessible from the LAN
From: freeswitch-users-bounces at lists.freeswitch.org [mailto:freeswitch-users-bounces at lists.freeswitch.org] On Behalf Of Carlos Fererro
Sent: Tuesday, September 1, 2015 11:42 AM
To: FreeSWITCH Users Help <freeswitch-users at lists.freeswitch.org>
Subject: Re: [Freeswitch-users] Python based Event Socket Library doesn't connect to remote FreeSWITCH
thank you very much for you reply. No, I didn't change any configuration in the event sockel xml file to make eventsocket bind to anything other then localhost. And why should I? There are no multiple NIC cards or anything like that.
Simple configuration: two machines behind the same router - FS runs on 192.168.1.102 and client runs on 192.168.1.103. No firewalls and traffic doesn't go outside the router. Event socket client won't get connected to the FS. Problem I have is 100% reproducible.
BTW, on Mac client can't connect to the FS even if client and FS do run on the same machine.
Any suggestions to try?
On Tue, Sep 1, 2015 at 8:47 AM, Ken Rice <krice at freeswitch.org <mailto:krice at freeswitch.org> > wrote:
Did you make the eventsocket on the freeswitch server bind to something other than localhost which is its default configuration?
If you do this you should also ensure that this connection is firewalled off and not passed over the public internet as there is absolutely no encryption on this connection and the password is passed in the clear
From: freeswitch-users-bounces at lists.freeswitch.org <mailto:freeswitch-users-bounces at lists.freeswitch.org> [mailto:freeswitch-users-bounces at lists.freeswitch.org <mailto:freeswitch-users-bounces at lists.freeswitch.org> ] On Behalf Of Carlos Fererro
Sent: Sunday, August 30, 2015 12:33 PM
To: freeswitch-users at lists.freeswitch.org <mailto:freeswitch-users at lists.freeswitch.org>
Subject: [Freeswitch-users] Python based Event Socket Library doesn't connect to remote FreeSWITCH
To all Event Socket Library FreeSWITCH gurus!
Python implementation of the Event Socket Library doesn't seem to work with FreeSWITCH running on remote host. Only "localhost" or "127.0.0.1" has to be specified as the first parameter to the ESLconnection constructor to let client to successfully connect to the FreeSWITCH. Event if FreeSWITCH is running on the SAME machine (not even remote host) as the client and the "host" is specified with the IP address of the machine in the ESLconnection - no valid connection is getting established.
I am pretty sure that such a fundamental thing can't not to work and I am just missing something simple. Any help is greatly appreciated.
Professional FreeSWITCH Consulting Services:
consulting at freeswitch.org <mailto:consulting at freeswitch.org>
Official FreeSWITCH Sites
FreeSWITCH-users mailing list
FreeSWITCH-users at lists.freeswitch.org <mailto:FreeSWITCH-users at lists.freeswitch.org>
-------------- next part --------------
An HTML attachment was scrubbed...
Join us at ClueCon 2016 Aug 8-12, 2016
More information about the FreeSWITCH-users