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. Thanks Carlos
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@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Carlos Fererro Sent: Sunday, August 30, 2015 12:33 PM To: freeswitch-users@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. Thanks Carlos
Hi Ken, 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? Thanks On Tue, Sep 1, 2015 at 8:47 AM, Ken Rice <krice@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@lists.freeswitch.org [mailto: freeswitch-users-bounces@lists.freeswitch.org] *On Behalf Of *Carlos Fererro *Sent:* Sunday, August 30, 2015 12:33 PM *To:* freeswitch-users@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.
Thanks
Carlos
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.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 http://www.freeswitch.org
I suggest you traceroute to 127.0.0.1 On Tue, Sep 1, 2015 at 12:41 PM, Carlos Fererro <carlos4fsint@gmail.com> wrote:
Hi Ken,
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?
Thanks
On Tue, Sep 1, 2015 at 8:47 AM, Ken Rice <krice@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@lists.freeswitch.org [mailto: freeswitch-users-bounces@lists.freeswitch.org] *On Behalf Of *Carlos Fererro *Sent:* Sunday, August 30, 2015 12:33 PM *To:* freeswitch-users@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.
Thanks
Carlos
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.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 http://www.freeswitch.org
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.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 http://www.freeswitch.org
And what would be the purpose of that? On Tue, Sep 1, 2015 at 9:43 AM, Russell Treleaven <rtreleaven@bunnykick.ca> wrote:
I suggest you traceroute to 127.0.0.1
On Tue, Sep 1, 2015 at 12:41 PM, Carlos Fererro <carlos4fsint@gmail.com> wrote:
Hi Ken,
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?
Thanks
On Tue, Sep 1, 2015 at 8:47 AM, Ken Rice <krice@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@lists.freeswitch.org [mailto: freeswitch-users-bounces@lists.freeswitch.org] *On Behalf Of *Carlos Fererro *Sent:* Sunday, August 30, 2015 12:33 PM *To:* freeswitch-users@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.
Thanks
Carlos
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.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 http://www.freeswitch.org
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.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 http://www.freeswitch.org
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.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 http://www.freeswitch.org
you would see the 127.0.0.1 exists on all machines and hopefully bind your server to an route-able address On Tue, Sep 1, 2015 at 12:49 PM, Carlos Fererro <carlos4fsint@gmail.com> wrote:
And what would be the purpose of that?
On Tue, Sep 1, 2015 at 9:43 AM, Russell Treleaven <rtreleaven@bunnykick.ca
wrote:
I suggest you traceroute to 127.0.0.1
On Tue, Sep 1, 2015 at 12:41 PM, Carlos Fererro <carlos4fsint@gmail.com> wrote:
Hi Ken,
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?
Thanks
On Tue, Sep 1, 2015 at 8:47 AM, Ken Rice <krice@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@lists.freeswitch.org [mailto: freeswitch-users-bounces@lists.freeswitch.org] *On Behalf Of *Carlos Fererro *Sent:* Sunday, August 30, 2015 12:33 PM *To:* freeswitch-users@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.
Thanks
Carlos
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.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 http://www.freeswitch.org
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.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 http://www.freeswitch.org
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.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 http://www.freeswitch.org
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.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 http://www.freeswitch.org
Carlos, It's the same thing for default MySQL setup on Debian. It only bind to localhost to in order bind it to another address you need to change it in my.cnf. So freeswitch ESL by default listen to localhost (127.0.0.1). Go ahead and update your config. Sent from my iPhone
On Sep 1, 2015, at 12:54 PM, Russell Treleaven <rtreleaven@bunnykick.ca> wrote:
you would see the 127.0.0.1 exists on all machines and hopefully bind your server to an route-able address
On Tue, Sep 1, 2015 at 12:49 PM, Carlos Fererro <carlos4fsint@gmail.com> wrote: And what would be the purpose of that?
On Tue, Sep 1, 2015 at 9:43 AM, Russell Treleaven <rtreleaven@bunnykick.ca> wrote: I suggest you traceroute to 127.0.0.1
On Tue, Sep 1, 2015 at 12:41 PM, Carlos Fererro <carlos4fsint@gmail.com> wrote: Hi Ken,
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?
Thanks
On Tue, Sep 1, 2015 at 8:47 AM, Ken Rice <krice@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@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Carlos Fererro Sent: Sunday, August 30, 2015 12:33 PM To: freeswitch-users@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.
Thanks
Carlos
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.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 http://www.freeswitch.org
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.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 http://www.freeswitch.org
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.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 http://www.freeswitch.org
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.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 http://www.freeswitch.org
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.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 http://www.freeswitch.org
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@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Carlos Fererro Sent: Tuesday, September 1, 2015 11:42 AM To: FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org> Subject: Re: [Freeswitch-users] Python based Event Socket Library doesn't connect to remote FreeSWITCH Hi Ken, 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? Thanks On Tue, Sep 1, 2015 at 8:47 AM, Ken Rice <krice@freeswitch.org <mailto:krice@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@lists.freeswitch.org <mailto:freeswitch-users-bounces@lists.freeswitch.org> [mailto:freeswitch-users-bounces@lists.freeswitch.org <mailto:freeswitch-users-bounces@lists.freeswitch.org> ] On Behalf Of Carlos Fererro Sent: Sunday, August 30, 2015 12:33 PM To: freeswitch-users@lists.freeswitch.org <mailto:freeswitch-users@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. Thanks Carlos _________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org <mailto:consulting@freeswitch.org> http://www.freeswitchsolutions.com Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org <mailto:FreeSWITCH-users@lists.freeswitch.org> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
Very sorry for not replying fast enough. Yes, your suggestion was correct. Once I changed the config to bind to the externally accessible IP I was able to connect from the remote client. Thank you very much again. On Tue, Sep 1, 2015 at 10:03 AM, Ken Rice <krice@freeswitch.org> wrote:
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@lists.freeswitch.org [mailto: freeswitch-users-bounces@lists.freeswitch.org] *On Behalf Of *Carlos Fererro *Sent:* Tuesday, September 1, 2015 11:42 AM *To:* FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org> *Subject:* Re: [Freeswitch-users] Python based Event Socket Library doesn't connect to remote FreeSWITCH
Hi Ken,
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?
Thanks
On Tue, Sep 1, 2015 at 8:47 AM, Ken Rice <krice@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@lists.freeswitch.org [mailto: freeswitch-users-bounces@lists.freeswitch.org] *On Behalf Of *Carlos Fererro *Sent:* Sunday, August 30, 2015 12:33 PM *To:* freeswitch-users@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.
Thanks
Carlos
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.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 http://www.freeswitch.org
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.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 http://www.freeswitch.org
externally accessible IP
Please ensure you've changed the password to something secure and firewalled it so only your own servers/clients can connect to it. That socket doesn't just expose debugging information about your switch, it also allows the client to create calls (see call fraud), shutdown your freeswitch server (denial of service) and execute system commands. You need to be very careful about who can access it. Hence why it's localhost-only by default. On 1 September 2015 at 18:58, Carlos Fererro <carlos4fsint@gmail.com> wrote:
Very sorry for not replying fast enough. Yes, your suggestion was correct. Once I changed the config to bind to the externally accessible IP I was able to connect from the remote client.
Thank you very much again.
On Tue, Sep 1, 2015 at 10:03 AM, Ken Rice <krice@freeswitch.org> wrote:
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@lists.freeswitch.org [mailto: freeswitch-users-bounces@lists.freeswitch.org] *On Behalf Of *Carlos Fererro *Sent:* Tuesday, September 1, 2015 11:42 AM *To:* FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org> *Subject:* Re: [Freeswitch-users] Python based Event Socket Library doesn't connect to remote FreeSWITCH
Hi Ken,
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?
Thanks
On Tue, Sep 1, 2015 at 8:47 AM, Ken Rice <krice@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@lists.freeswitch.org [mailto: freeswitch-users-bounces@lists.freeswitch.org] *On Behalf Of *Carlos Fererro *Sent:* Sunday, August 30, 2015 12:33 PM *To:* freeswitch-users@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.
Thanks
Carlos
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.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 http://www.freeswitch.org
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.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 http://www.freeswitch.org
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.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 http://www.freeswitch.org
participants (5)
-
acheraime＠gmail.com
-
Carlos Fererro
-
Ken Rice
-
Russell Treleaven
-
Steven Ayre