Problems with fs_cli on OS X 10.6.4
Okay, so I managed to get FS working the other day and I even managed to test a call and test my voicemail. All seemed to be working smoothly until, because of the rain here, my power went out and I had to reboot my computer. I logged in through the terminal, set up FS in background went to fs_cli and I get this error message: [ERROR] libs/esl/fs_cli.c:1206 main() Error Connecting [Socket Connection Error] I managed to figure out that in the file "fs_cli.c" on line 1206 you find the code for displaying this error message. The problem is that I don't know why this error message is occurring. Does anyone have any helpful hints as to what I should look at to resolve this problem? I even tried going to the git tree and make current, but that gave me problems that forced me to turn off mod_spandsp and mod_skyopen in the modules.conf, which I had running earlier. Any thoughts? PeterS PS I am not sure if this is of any help, but in addition to the error line above, it also posted this info: Usage: fs_cli [-H <host>] [-P <port>] [-p <secret>] [-d <level>] [-x command] [profile] -?,-h --help Usage Information -H, --host=hostname Host to connect -P, --port=port Port to connect (1 - 65535) -u, --user=user@domain user@domain -p, --password=password Password -x, --execute=command Execute Command and Exit -l, --loglevel=command Log Level -q, --quiet Disable logging -r, --retry Retry connection on failure -R, --reconnect Reconnect if disconnected -d, --debug=level Debug Level (0 - 7)
Hi, Did you start FreeSWITCH before? fs_cli is only used to connect to the console of a running FreeSWITCH instance. If you did, try starting it without the -nc switch, it should stay in the foreground and tell you whats wrong, if you have a console you can also check that mod_event_socket is properly loaded (load mod_event_socket) Mathieu Rene Avant-Garde Solutions Inc Office: + 1 (514) 664-1044 x100 Cell: +1 (514) 664-1044 x200 mrene@avgs.ca On 2010-10-06, at 8:23 PM, Peter Schrock wrote:
Okay, so I managed to get FS working the other day and I even managed to test a call and test my voicemail. All seemed to be working smoothly until, because of the rain here, my power went out and I had to reboot my computer. I logged in through the terminal, set up FS in background went to fs_cli and I get this error message: [ERROR] libs/esl/fs_cli.c:1206 main() Error Connecting [Socket Connection Error] I managed to figure out that in the file "fs_cli.c" on line 1206 you find the code for displaying this error message. The problem is that I don't know why this error message is occurring. Does anyone have any helpful hints as to what I should look at to resolve this problem? I even tried going to the git tree and make current, but that gave me problems that forced me to turn off mod_spandsp and mod_skyopen in the modules.conf, which I had running earlier. Any thoughts?
PeterS
PS I am not sure if this is of any help, but in addition to the error line above, it also posted this info: Usage: fs_cli [-H <host>] [-P <port>] [-p <secret>] [-d <level>] [-x command] [profile]
-?,-h --help Usage Information -H, --host=hostname Host to connect -P, --port=port Port to connect (1 - 65535) -u, --user=user@domain user@domain -p, --password=password Password -x, --execute=command Execute Command and Exit -l, --loglevel=command Log Level -q, --quiet Disable logging -r, --retry Retry connection on failure -R, --reconnect Reconnect if disconnected -d, --debug=level Debug Level (0 - 7)
_______________________________________________ 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
In answer to your first question, yes. I guess my next question would be, if I don't need fs_cli, then what is it for? I guess I am assuming to access FS when it is running in background. What would be the difference between running it in the foreground vs background? Also, I ran FS without -nc and it showed that mod_event_socket loaded successfully. So why won't it with fs_cli? PeterS On Wed, Oct 6, 2010 at 5:29 PM, Mathieu Rene <mrene_lists@avgs.ca> wrote:
Hi,
Did you start FreeSWITCH before? fs_cli is only used to connect to the console of a running FreeSWITCH instance.
If you did, try starting it without the -nc switch, it should stay in the foreground and tell you whats wrong, if you have a console you can also check that mod_event_socket is properly loaded (load mod_event_socket)
Mathieu Rene Avant-Garde Solutions Inc Office: + 1 (514) 664-1044 x100 Cell: +1 (514) 664-1044 x200 mrene@avgs.ca
On 2010-10-06, at 8:23 PM, Peter Schrock wrote:
Okay, so I managed to get FS working the other day and I even managed to test a call and test my voicemail. All seemed to be working smoothly until, because of the rain here, my power went out and I had to reboot my computer. I logged in through the terminal, set up FS in background went to fs_cliand I get this error message: [ERROR] libs/esl/fs_cli.c:1206 main() Error Connecting [Socket Connection Error] I managed to figure out that in the file "fs_cli.c" on line 1206 you find the code for displaying this error message. The problem is that I don't know why this error message is occurring. Does anyone have any helpful hints as to what I should look at to resolve this problem? I even tried going to the git tree and make current, but that gave me problems that forced me to turn off mod_spandsp and mod_skyopen in the modules.conf, which I had running earlier. Any thoughts?
PeterS
PS I am not sure if this is of any help, but in addition to the error line above, it also posted this info: Usage: fs_cli [-H <host>] [-P <port>] [-p <secret>] [-d <level>] [-x command] [profile]
-?,-h --help Usage Information -H, --host=hostname Host to connect -P, --port=port Port to connect (1 - 65535) -u, --user=user@domain user@domain -p, --password=password Password -x, --execute=command Execute Command and Exit -l, --loglevel=command Log Level -q, --quiet Disable logging -r, --retry Retry connection on failure -R, --reconnect Reconnect if disconnected -d, --debug=level Debug Level (0 - 7)
_______________________________________________ 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
_______________________________________________ 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
Did you copy fs_cli.conf to /etc and make sure its parameters agreed with those in the config for mod_esl? Peter Schrock <peter.schrock@gmail.com> wrote:
In answer to your first question, yes. I guess my next question would be, if I don't need fs_cli, then what is it for? I guess I am assuming to access FS when it is running in background. What would be the difference between running it in the foreground vs background? Also, I ran FS without -nc and it showed that mod_event_socket loaded successfully. So why won't it with fs_cli?
PeterS
On Wed, Oct 6, 2010 at 5:29 PM, Mathieu Rene <mrene_lists@avgs.ca> wrote:
Hi,
Did you start FreeSWITCH before? fs_cli is only used to connect to the console of a running FreeSWITCH instance.
If you did, try starting it without the -nc switch, it should stay in the foreground and tell you whats wrong, if you have a console you can also check that mod_event_socket is properly loaded (load mod_event_socket)
Mathieu Rene Avant-Garde Solutions Inc Office: + 1 (514) 664-1044 x100 Cell: +1 (514) 664-1044 x200 mrene@avgs.ca
On 2010-10-06, at 8:23 PM, Peter Schrock wrote:
Okay, so I managed to get FS working the other day and I even managed to test a call and test my voicemail. All seemed to be working smoothly until, because of the rain here, my power went out and I had to reboot my computer. I logged in through the terminal, set up FS in background went to fs_cliand I get this error message: [ERROR] libs/esl/fs_cli.c:1206 main() Error Connecting [Socket Connection Error] I managed to figure out that in the file "fs_cli.c" on line 1206 you find the code for displaying this error message. The problem is that I don't know why this error message is occurring. Does anyone have any helpful hints as to what I should look at to resolve this problem? I even tried going to the git tree and make current, but that gave me problems that forced me to turn off mod_spandsp and mod_skyopen in the modules.conf, which I had running earlier. Any thoughts?
PeterS
PS I am not sure if this is of any help, but in addition to the error line above, it also posted this info: Usage: fs_cli [-H <host>] [-P <port>] [-p <secret>] [-d <level>] [-x command] [profile]
-?,-h --help Usage Information -H, --host=hostname Host to connect -P, --port=port Port to connect (1 - 65535) -u, --user=user@domain user@domain -p, --password=password Password -x, --execute=command Execute Command and Exit -l, --loglevel=command Log Level -q, --quiet Disable logging -r, --retry Retry connection on failure -R, --reconnect Reconnect if disconnected -d, --debug=level Debug Level (0 - 7)
_______________________________________________ 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
_______________________________________________ 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
---------------------------------------------------- Alternatives:
---------------------------------------------------- _______________________________________________ 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
-- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici covici@ccs.covici.com
fs_cli is a tool to connect to a running instance of FS, on the same computer, or another computer. It communicates with FS using the mod_event_socket loaded within FS. The server socket in FS listens for requests on port 8021 by default, this can be changed in event_socket.conf.xml /Peter Från: freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] För Peter Schrock Skickat: den 7 oktober 2010 07:55 Till: FreeSWITCH Users Help Ämne: Re: [Freeswitch-users] Problems with fs_cli on OS X 10.6.4 In answer to your first question, yes. I guess my next question would be, if I don't need fs_cli, then what is it for? I guess I am assuming to access FS when it is running in background. What would be the difference between running it in the foreground vs background? Also, I ran FS without -nc and it showed that mod_event_socket loaded successfully. So why won't it with fs_cli? PeterS On Wed, Oct 6, 2010 at 5:29 PM, Mathieu Rene <mrene_lists@avgs.ca<mailto:mrene_lists@avgs.ca>> wrote: Hi, Did you start FreeSWITCH before? fs_cli is only used to connect to the console of a running FreeSWITCH instance. If you did, try starting it without the -nc switch, it should stay in the foreground and tell you whats wrong, if you have a console you can also check that mod_event_socket is properly loaded (load mod_event_socket) Mathieu Rene Avant-Garde Solutions Inc Office: + 1 (514) 664-1044 x100 Cell: +1 (514) 664-1044 x200 mrene@avgs.ca<mailto:mrene@avgs.ca> On 2010-10-06, at 8:23 PM, Peter Schrock wrote: Okay, so I managed to get FS working the other day and I even managed to test a call and test my voicemail. All seemed to be working smoothly until, because of the rain here, my power went out and I had to reboot my computer. I logged in through the terminal, set up FS in background went to fs_cli and I get this error message: [ERROR] libs/esl/fs_cli.c:1206 main() Error Connecting [Socket Connection Error] I managed to figure out that in the file "fs_cli.c" on line 1206 you find the code for displaying this error message. The problem is that I don't know why this error message is occurring. Does anyone have any helpful hints as to what I should look at to resolve this problem? I even tried going to the git tree and make current, but that gave me problems that forced me to turn off mod_spandsp and mod_skyopen in the modules.conf, which I had running earlier. Any thoughts? PeterS PS I am not sure if this is of any help, but in addition to the error line above, it also posted this info: Usage: fs_cli [-H <host>] [-P <port>] [-p <secret>] [-d <level>] [-x command] [profile] -?,-h --help Usage Information -H, --host=hostname Host to connect -P, --port=port Port to connect (1 - 65535) -u, --user=user@domain user@domain -p, --password=password Password -x, --execute=command Execute Command and Exit -l, --loglevel=command Log Level -q, --quiet Disable logging -r, --retry Retry connection on failure -R, --reconnect Reconnect if disconnected -d, --debug=level Debug Level (0 - 7) _______________________________________________ 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 _______________________________________________ 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 !DSPAM:4cad626f32932643394250!
John Covici, To make sure I understand correctly, do you me the copy found in: /usr/local/freeswitch/libs/esl or somewhere else? Also, is there a wiki that discusses how to make those parameters agreeable? Peter Olsson, Thanks for clarifying that. I guess my question now would be (cause I am trying to use the book as much as possible to help me understand FS) is why would the book be insistent on using fs_cli and how many people actually use it. Is there a wiki discussing how to manage the mod_event_socket so that fs_cli will function the way it should instead popping up errors like it has been. Also, in general, if one were to set up FS in background mode, how do you stop it from being in background mode? PeterS On Wed, Oct 6, 2010 at 11:14 PM, Peter Olsson < peter.olsson@visionutveckling.se> wrote:
fs_cli is a tool to connect to a running instance of FS, on the same computer, or another computer. It communicates with FS using the mod_event_socket loaded within FS. The server socket in FS listens for requests on port 8021 by default, this can be changed in event_socket.conf.xml
/Peter
*Från:* freeswitch-users-bounces@lists.freeswitch.org [mailto: freeswitch-users-bounces@lists.freeswitch.org] *För *Peter Schrock *Skickat:* den 7 oktober 2010 07:55 *Till:* FreeSWITCH Users Help *Ämne:* Re: [Freeswitch-users] Problems with fs_cli on OS X 10.6.4
In answer to your first question, yes. I guess my next question would be, if I don't need fs_cli, then what is it for? I guess I am assuming to access FS when it is running in background. What would be the difference between running it in the foreground vs background?
Also, I ran FS without -nc and it showed that mod_event_socket loaded successfully. So why won't it with fs_cli?
PeterS
On Wed, Oct 6, 2010 at 5:29 PM, Mathieu Rene <mrene_lists@avgs.ca> wrote:
Hi,
Did you start FreeSWITCH before? fs_cli is only used to connect to the console of a running FreeSWITCH instance.
If you did, try starting it without the -nc switch, it should stay in the foreground and tell you whats wrong, if you have a console you can also check that mod_event_socket is properly loaded (load mod_event_socket)
Mathieu Rene
Avant-Garde Solutions Inc
Office: + 1 (514) 664-1044 x100
Cell: +1 (514) 664-1044 x200
mrene@avgs.ca
On 2010-10-06, at 8:23 PM, Peter Schrock wrote:
Okay, so I managed to get FS working the other day and I even managed to test a call and test my voicemail. All seemed to be working smoothly until, because of the rain here, my power went out and I had to reboot my computer. I logged in through the terminal, set up FS in background went to fs_cliand I get this error message:
[ERROR] libs/esl/fs_cli.c:1206 main() Error Connecting [Socket Connection Error]
I managed to figure out that in the file "fs_cli.c" on line 1206 you find the code for displaying this error message. The problem is that I don't know why this error message is occurring. Does anyone have any helpful hints as to what I should look at to resolve this problem?
I even tried going to the git tree and make current, but that gave me problems that forced me to turn off mod_spandsp and mod_skyopen in the modules.conf, which I had running earlier. Any thoughts?
PeterS
PS
I am not sure if this is of any help, but in addition to the error line above, it also posted this info:
Usage: fs_cli [-H <host>] [-P <port>] [-p <secret>] [-d <level>] [-x command] [profile]
-?,-h --help Usage Information
-H, --host=hostname Host to connect
-P, --port=port Port to connect (1 - 65535)
-u, --user=user@domain user@domain
-p, --password=password Password
-x, --execute=command Execute Command and Exit
-l, --loglevel=command Log Level
-q, --quiet Disable logging
-r, --retry Retry connection on failure
-R, --reconnect Reconnect if disconnected
-d, --debug=level Debug Level (0 - 7)
_______________________________________________ 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
_______________________________________________ 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
!DSPAM:4cad626f32932643394250!
_______________________________________________ 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
Yep, that is the file and you can look in the configs for mod_esl and make sure the port, password, etc. match. Peter Schrock <peter.schrock@gmail.com> wrote:
John Covici,
To make sure I understand correctly, do you me the copy found in: /usr/local/freeswitch/libs/esl or somewhere else? Also, is there a wiki that discusses how to make those parameters agreeable?
Peter Olsson, Thanks for clarifying that. I guess my question now would be (cause I am trying to use the book as much as possible to help me understand FS) is why would the book be insistent on using fs_cli and how many people actually use it. Is there a wiki discussing how to manage the mod_event_socket so that fs_cli will function the way it should instead popping up errors like it has been.
Also, in general, if one were to set up FS in background mode, how do you stop it from being in background mode?
PeterS
On Wed, Oct 6, 2010 at 11:14 PM, Peter Olsson < peter.olsson@visionutveckling.se> wrote:
fs_cli is a tool to connect to a running instance of FS, on the same computer, or another computer. It communicates with FS using the mod_event_socket loaded within FS. The server socket in FS listens for requests on port 8021 by default, this can be changed in event_socket.conf.xml
/Peter
*Från:* freeswitch-users-bounces@lists.freeswitch.org [mailto: freeswitch-users-bounces@lists.freeswitch.org] *För *Peter Schrock *Skickat:* den 7 oktober 2010 07:55 *Till:* FreeSWITCH Users Help *Ämne:* Re: [Freeswitch-users] Problems with fs_cli on OS X 10.6.4
In answer to your first question, yes. I guess my next question would be, if I don't need fs_cli, then what is it for? I guess I am assuming to access FS when it is running in background. What would be the difference between running it in the foreground vs background?
Also, I ran FS without -nc and it showed that mod_event_socket loaded successfully. So why won't it with fs_cli?
PeterS
On Wed, Oct 6, 2010 at 5:29 PM, Mathieu Rene <mrene_lists@avgs.ca> wrote:
Hi,
Did you start FreeSWITCH before? fs_cli is only used to connect to the console of a running FreeSWITCH instance.
If you did, try starting it without the -nc switch, it should stay in the foreground and tell you whats wrong, if you have a console you can also check that mod_event_socket is properly loaded (load mod_event_socket)
Mathieu Rene
Avant-Garde Solutions Inc
Office: + 1 (514) 664-1044 x100
Cell: +1 (514) 664-1044 x200
mrene@avgs.ca
On 2010-10-06, at 8:23 PM, Peter Schrock wrote:
Okay, so I managed to get FS working the other day and I even managed to test a call and test my voicemail. All seemed to be working smoothly until, because of the rain here, my power went out and I had to reboot my computer. I logged in through the terminal, set up FS in background went to fs_cliand I get this error message:
[ERROR] libs/esl/fs_cli.c:1206 main() Error Connecting [Socket Connection Error]
I managed to figure out that in the file "fs_cli.c" on line 1206 you find the code for displaying this error message. The problem is that I don't know why this error message is occurring. Does anyone have any helpful hints as to what I should look at to resolve this problem?
I even tried going to the git tree and make current, but that gave me problems that forced me to turn off mod_spandsp and mod_skyopen in the modules.conf, which I had running earlier. Any thoughts?
PeterS
PS
I am not sure if this is of any help, but in addition to the error line above, it also posted this info:
Usage: fs_cli [-H <host>] [-P <port>] [-p <secret>] [-d <level>] [-x command] [profile]
-?,-h --help Usage Information
-H, --host=hostname Host to connect
-P, --port=port Port to connect (1 - 65535)
-u, --user=user@domain user@domain
-p, --password=password Password
-x, --execute=command Execute Command and Exit
-l, --loglevel=command Log Level
-q, --quiet Disable logging
-r, --retry Retry connection on failure
-R, --reconnect Reconnect if disconnected
-d, --debug=level Debug Level (0 - 7)
_______________________________________________ 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
_______________________________________________ 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
!DSPAM:4cad626f32932643394250!
_______________________________________________ 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
---------------------------------------------------- Alternatives:
---------------------------------------------------- _______________________________________________ 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
-- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici covici@ccs.covici.com
I'm pretty sure that fs_cli is used by everyone who uses FS, since we want the FreeSWITCH process itself to run in background. I'm not really getting the problem here. Install FS with default config, start FS in background, then run fs_cli to connect to the running instance - is it really that hard? If running in background, you can stop with "freeswitch -stop" or "fs_cli -x shutdown" /Peter Från: freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] För Peter Schrock Skickat: den 7 oktober 2010 21:41 Till: FreeSWITCH Users Help Ämne: Re: [Freeswitch-users] Problems with fs_cli on OS X 10.6.4 John Covici, To make sure I understand correctly, do you me the copy found in: /usr/local/freeswitch/libs/esl or somewhere else? Also, is there a wiki that discusses how to make those parameters agreeable? Peter Olsson, Thanks for clarifying that. I guess my question now would be (cause I am trying to use the book as much as possible to help me understand FS) is why would the book be insistent on using fs_cli and how many people actually use it. Is there a wiki discussing how to manage the mod_event_socket so that fs_cli will function the way it should instead popping up errors like it has been. Also, in general, if one were to set up FS in background mode, how do you stop it from being in background mode? PeterS On Wed, Oct 6, 2010 at 11:14 PM, Peter Olsson <peter.olsson@visionutveckling.se<mailto:peter.olsson@visionutveckling.se>> wrote: fs_cli is a tool to connect to a running instance of FS, on the same computer, or another computer. It communicates with FS using the mod_event_socket loaded within FS. The server socket in FS listens for requests on port 8021 by default, this can be changed in event_socket.conf.xml /Peter Från: 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>] För Peter Schrock Skickat: den 7 oktober 2010 07:55 Till: FreeSWITCH Users Help Ämne: Re: [Freeswitch-users] Problems with fs_cli on OS X 10.6.4 In answer to your first question, yes. I guess my next question would be, if I don't need fs_cli, then what is it for? I guess I am assuming to access FS when it is running in background. What would be the difference between running it in the foreground vs background? Also, I ran FS without -nc and it showed that mod_event_socket loaded successfully. So why won't it with fs_cli? PeterS On Wed, Oct 6, 2010 at 5:29 PM, Mathieu Rene <mrene_lists@avgs.ca<mailto:mrene_lists@avgs.ca>> wrote: Hi, Did you start FreeSWITCH before? fs_cli is only used to connect to the console of a running FreeSWITCH instance. If you did, try starting it without the -nc switch, it should stay in the foreground and tell you whats wrong, if you have a console you can also check that mod_event_socket is properly loaded (load mod_event_socket) Mathieu Rene Avant-Garde Solutions Inc Office: + 1 (514) 664-1044 x100 Cell: +1 (514) 664-1044 x200 mrene@avgs.ca<mailto:mrene@avgs.ca> On 2010-10-06, at 8:23 PM, Peter Schrock wrote: Okay, so I managed to get FS working the other day and I even managed to test a call and test my voicemail. All seemed to be working smoothly until, because of the rain here, my power went out and I had to reboot my computer. I logged in through the terminal, set up FS in background went to fs_cli and I get this error message: [ERROR] libs/esl/fs_cli.c:1206 main() Error Connecting [Socket Connection Error] I managed to figure out that in the file "fs_cli.c" on line 1206 you find the code for displaying this error message. The problem is that I don't know why this error message is occurring. Does anyone have any helpful hints as to what I should look at to resolve this problem? I even tried going to the git tree and make current, but that gave me problems that forced me to turn off mod_spandsp and mod_skyopen in the modules.conf, which I had running earlier. Any thoughts? PeterS PS I am not sure if this is of any help, but in addition to the error line above, it also posted this info: Usage: fs_cli [-H <host>] [-P <port>] [-p <secret>] [-d <level>] [-x command] [profile] -?,-h --help Usage Information -H, --host=hostname Host to connect -P, --port=port Port to connect (1 - 65535) -u, --user=user@domain user@domain -p, --password=password Password -x, --execute=command Execute Command and Exit -l, --loglevel=command Log Level -q, --quiet Disable logging -r, --retry Retry connection on failure -R, --reconnect Reconnect if disconnected -d, --debug=level Debug Level (0 - 7) _______________________________________________ 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 _______________________________________________ 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 _______________________________________________ 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 !DSPAM:4cae242c32931240012030!
Did you check if the FreeSWITCH process is running? Regards HASSAN On 2010-10-08, Peter Olsson <peter.olsson@visionutveckling.se> wrote:
I'm pretty sure that fs_cli is used by everyone who uses FS, since we want the FreeSWITCH process itself to run in background.
I'm not really getting the problem here. Install FS with default config, start FS in background, then run fs_cli to connect to the running instance - is it really that hard?
If running in background, you can stop with "freeswitch -stop" or "fs_cli -x shutdown"
/Peter
Från: freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] För Peter Schrock Skickat: den 7 oktober 2010 21:41 Till: FreeSWITCH Users Help Ämne: Re: [Freeswitch-users] Problems with fs_cli on OS X 10.6.4
John Covici,
To make sure I understand correctly, do you me the copy found in: /usr/local/freeswitch/libs/esl or somewhere else? Also, is there a wiki that discusses how to make those parameters agreeable?
Peter Olsson, Thanks for clarifying that. I guess my question now would be (cause I am trying to use the book as much as possible to help me understand FS) is why would the book be insistent on using fs_cli and how many people actually use it. Is there a wiki discussing how to manage the mod_event_socket so that fs_cli will function the way it should instead popping up errors like it has been.
Also, in general, if one were to set up FS in background mode, how do you stop it from being in background mode?
PeterS On Wed, Oct 6, 2010 at 11:14 PM, Peter Olsson <peter.olsson@visionutveckling.se<mailto:peter.olsson@visionutveckling.se>> wrote: fs_cli is a tool to connect to a running instance of FS, on the same computer, or another computer. It communicates with FS using the mod_event_socket loaded within FS. The server socket in FS listens for requests on port 8021 by default, this can be changed in event_socket.conf.xml
/Peter
Från: 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>] För Peter Schrock Skickat: den 7 oktober 2010 07:55 Till: FreeSWITCH Users Help Ämne: Re: [Freeswitch-users] Problems with fs_cli on OS X 10.6.4
In answer to your first question, yes. I guess my next question would be, if I don't need fs_cli, then what is it for? I guess I am assuming to access FS when it is running in background. What would be the difference between running it in the foreground vs background? Also, I ran FS without -nc and it showed that mod_event_socket loaded successfully. So why won't it with fs_cli?
PeterS On Wed, Oct 6, 2010 at 5:29 PM, Mathieu Rene <mrene_lists@avgs.ca<mailto:mrene_lists@avgs.ca>> wrote: Hi,
Did you start FreeSWITCH before? fs_cli is only used to connect to the console of a running FreeSWITCH instance.
If you did, try starting it without the -nc switch, it should stay in the foreground and tell you whats wrong, if you have a console you can also check that mod_event_socket is properly loaded (load mod_event_socket)
Mathieu Rene Avant-Garde Solutions Inc Office: + 1 (514) 664-1044 x100 Cell: +1 (514) 664-1044 x200 mrene@avgs.ca<mailto:mrene@avgs.ca>
On 2010-10-06, at 8:23 PM, Peter Schrock wrote:
Okay, so I managed to get FS working the other day and I even managed to test a call and test my voicemail. All seemed to be working smoothly until, because of the rain here, my power went out and I had to reboot my computer. I logged in through the terminal, set up FS in background went to fs_cli and I get this error message: [ERROR] libs/esl/fs_cli.c:1206 main() Error Connecting [Socket Connection Error] I managed to figure out that in the file "fs_cli.c" on line 1206 you find the code for displaying this error message. The problem is that I don't know why this error message is occurring. Does anyone have any helpful hints as to what I should look at to resolve this problem? I even tried going to the git tree and make current, but that gave me problems that forced me to turn off mod_spandsp and mod_skyopen in the modules.conf, which I had running earlier. Any thoughts?
PeterS
PS I am not sure if this is of any help, but in addition to the error line above, it also posted this info: Usage: fs_cli [-H <host>] [-P <port>] [-p <secret>] [-d <level>] [-x command] [profile]
-?,-h --help Usage Information -H, --host=hostname Host to connect -P, --port=port Port to connect (1 - 65535) -u, --user=user@domain user@domain -p, --password=password Password -x, --execute=command Execute Command and Exit -l, --loglevel=command Log Level -q, --quiet Disable logging -r, --retry Retry connection on failure -R, --reconnect Reconnect if disconnected -d, --debug=level Debug Level (0 - 7)
_______________________________________________ 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
_______________________________________________ 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
_______________________________________________ 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
!DSPAM:4cae242c32931240012030!
-- Sent from my mobile device
You know, I am asking myself the same question. "Is it really that hard?" Of course, I wouldn't be asking unless I was having issues now, would I. As annoyed as you sound in this email, so am I that, as you have indirectly stated, this basic function should just work. However it is not and that is why I am asking for help. Thanks for the answered question on how to shutdown in the background. PeterS On Oct 8, 2010, at 12:22 AM, Peter Olsson <peter.olsson@visionutveckling.se> wrote: I’m pretty sure that fs_cli is used by everyone who uses FS, since we want the FreeSWITCH process itself to run in background. I’m not really getting the problem here. Install FS with default config, start FS in background, then run fs_cli to connect to the running instance – is it really that hard? If running in background, you can stop with “freeswitch –stop” or “fs_cli –x shutdown” /Peter *Från:* freeswitch-users-bounces@lists.freeswitch.org [mailto: freeswitch-users-bounces@lists.freeswitch.org] *För *Peter Schrock *Skickat:* den 7 oktober 2010 21:41 *Till:* FreeSWITCH Users Help *Ämne:* Re: [Freeswitch-users] Problems with fs_cli on OS X 10.6.4 John Covici, To make sure I understand correctly, do you me the copy found in: /usr/local/freeswitch/libs/esl or somewhere else? Also, is there a wiki that discusses how to make those parameters agreeable? Peter Olsson, Thanks for clarifying that. I guess my question now would be (cause I am trying to use the book as much as possible to help me understand FS) is why would the book be insistent on using fs_cli and how many people actually use it. Is there a wiki discussing how to manage the mod_event_socket so that fs_cli will function the way it should instead popping up errors like it has been. Also, in general, if one were to set up FS in background mode, how do you stop it from being in background mode? PeterS On Wed, Oct 6, 2010 at 11:14 PM, Peter Olsson < peter.olsson@visionutveckling.se> wrote: fs_cli is a tool to connect to a running instance of FS, on the same computer, or another computer. It communicates with FS using the mod_event_socket loaded within FS. The server socket in FS listens for requests on port 8021 by default, this can be changed in event_socket.conf.xml /Peter *Från:* freeswitch-users-bounces@lists.freeswitch.org [mailto: freeswitch-users-bounces@lists.freeswitch.org] *För *Peter Schrock *Skickat:* den 7 oktober 2010 07:55 *Till:* FreeSWITCH Users Help *Ämne:* Re: [Freeswitch-users] Problems with fs_cli on OS X 10.6.4 In answer to your first question, yes. I guess my next question would be, if I don't need fs_cli, then what is it for? I guess I am assuming to access FS when it is running in background. What would be the difference between running it in the foreground vs background? Also, I ran FS without -nc and it showed that mod_event_socket loaded successfully. So why won't it with fs_cli? PeterS On Wed, Oct 6, 2010 at 5:29 PM, Mathieu Rene <mrene_lists@avgs.ca> wrote: Hi, Did you start FreeSWITCH before? fs_cli is only used to connect to the console of a running FreeSWITCH instance. If you did, try starting it without the -nc switch, it should stay in the foreground and tell you whats wrong, if you have a console you can also check that mod_event_socket is properly loaded (load mod_event_socket) Mathieu Rene Avant-Garde Solutions Inc Office: + 1 (514) 664-1044 x100 Cell: +1 (514) 664-1044 x200 mrene@avgs.ca On 2010-10-06, at 8:23 PM, Peter Schrock wrote: Okay, so I managed to get FS working the other day and I even managed to test a call and test my voicemail. All seemed to be working smoothly until, because of the rain here, my power went out and I had to reboot my computer. I logged in through the terminal, set up FS in background went to fs_cli and I get this error message: [ERROR] libs/esl/fs_cli.c:1206 main() Error Connecting [Socket Connection Error] I managed to figure out that in the file "fs_cli.c" on line 1206 you find the code for displaying this error message. The problem is that I don't know why this error message is occurring. Does anyone have any helpful hints as to what I should look at to resolve this problem? I even tried going to the git tree and make current, but that gave me problems that forced me to turn off mod_spandsp and mod_skyopen in the modules.conf, which I had running earlier. Any thoughts? PeterS PS I am not sure if this is of any help, but in addition to the error line above, it also posted this info: Usage: fs_cli [-H <host>] [-P <port>] [-p <secret>] [-d <level>] [-x command] [profile] -?,-h --help Usage Information -H, --host=hostname Host to connect -P, --port=port Port to connect (1 - 65535) -u, --user=user@domain user@domain -p, --password=password Password -x, --execute=command Execute Command and Exit -l, --loglevel=command Log Level -q, --quiet Disable logging -r, --retry Retry connection on failure -R, --reconnect Reconnect if disconnected -d, --debug=level Debug Level (0 - 7) _______________________________________________ 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 _______________________________________________ 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 _______________________________________________ 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 !DSPAM:4cae242c32931240012030! _______________________________________________ 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
1. Check FS is running 2. Check the port you're connecting to matches the one in event_socket.conf.xml 3. Check that event_socket.conf.xml binding to the same IP you're connecting to (e.g. 0.0.0.0 if you're connecting from a remote machine, since the default 127.0.0.1 won't work then) 4. Use netstat on the FS server to verify FreeSWITCH is actually listening on the port you're trying to connect to (I've had a syntax error in the config file make the module fail to load in the past which left FS running but with no ESL socket). (If the module fails to load there'll also be an error in the log file). 5. Check a firewall isn't blocking access to the port -Steve On 7 October 2010 01:23, Peter Schrock <peter.schrock@gmail.com> wrote:
Okay, so I managed to get FS working the other day and I even managed to test a call and test my voicemail. All seemed to be working smoothly until, because of the rain here, my power went out and I had to reboot my computer. I logged in through the terminal, set up FS in background went to fs_cli and I get this error message: [ERROR] libs/esl/fs_cli.c:1206 main() Error Connecting [Socket Connection Error] I managed to figure out that in the file "fs_cli.c" on line 1206 you find the code for displaying this error message. The problem is that I don't know why this error message is occurring. Does anyone have any helpful hints as to what I should look at to resolve this problem? I even tried going to the git tree and make current, but that gave me problems that forced me to turn off mod_spandsp and mod_skyopen in the modules.conf, which I had running earlier. Any thoughts? PeterS PS I am not sure if this is of any help, but in addition to the error line above, it also posted this info: Usage: fs_cli [-H <host>] [-P <port>] [-p <secret>] [-d <level>] [-x command] [profile] -?,-h --help Usage Information -H, --host=hostname Host to connect -P, --port=port Port to connect (1 - 65535) -u, --user=user@domain user@domain -p, --password=password Password -x, --execute=command Execute Command and Exit -l, --loglevel=command Log Level -q, --quiet Disable logging -r, --retry Retry connection on failure -R, --reconnect Reconnect if disconnected -d, --debug=level Debug Level (0 - 7)
_______________________________________________ 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
Thanks Steve, I will check on this and see if this works. PeterS On Oct 8, 2010, at 5:10 AM, Steven Ayre <steveayre@gmail.com> wrote:
1. Check FS is running 2. Check the port you're connecting to matches the one in event_socket.conf.xml 3. Check that event_socket.conf.xml binding to the same IP you're connecting to (e.g. 0.0.0.0 if you're connecting from a remote machine, since the default 127.0.0.1 won't work then) 4. Use netstat on the FS server to verify FreeSWITCH is actually listening on the port you're trying to connect to (I've had a syntax error in the config file make the module fail to load in the past which left FS running but with no ESL socket). (If the module fails to load there'll also be an error in the log file). 5. Check a firewall isn't blocking access to the port
-Steve
On 7 October 2010 01:23, Peter Schrock <peter.schrock@gmail.com> wrote:
Okay, so I managed to get FS working the other day and I even managed to test a call and test my voicemail. All seemed to be working smoothly until, because of the rain here, my power went out and I had to reboot my computer. I logged in through the terminal, set up FS in background went to fs_cli and I get this error message: [ERROR] libs/esl/fs_cli.c:1206 main() Error Connecting [Socket Connection Error] I managed to figure out that in the file "fs_cli.c" on line 1206 you find the code for displaying this error message. The problem is that I don't know why this error message is occurring. Does anyone have any helpful hints as to what I should look at to resolve this problem? I even tried going to the git tree and make current, but that gave me problems that forced me to turn off mod_spandsp and mod_skyopen in the modules.conf, which I had running earlier. Any thoughts? PeterS PS I am not sure if this is of any help, but in addition to the error line above, it also posted this info: Usage: fs_cli [-H <host>] [-P <port>] [-p <secret>] [-d <level>] [-x command] [profile] -?,-h --help Usage Information -H, --host=hostname Host to connect -P, --port=port Port to connect (1 - 65535) -u, --user=user@domain user@domain -p, --password=password Password -x, --execute=command Execute Command and Exit -l, --loglevel=command Log Level -q, --quiet Disable logging -r, --retry Retry connection on failure -R, --reconnect Reconnect if disconnected -d, --debug=level Debug Level (0 - 7)
_______________________________________________ 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
_______________________________________________ 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
just to make sure what am I comparing event_socket.conf.xml to? I have found that it is set up with the default settings but am not sure how or to what I am suppose to fix. I understand that I am comparing it to FS, but I am wondering if there is some kind of file that I am looking for to compare the two. PeterS On Fri, Oct 8, 2010 at 4:56 AM, Steven Ayre <steveayre@gmail.com> wrote:
1. Check FS is running 2. Check the port you're connecting to matches the one in event_socket.conf.xml 3. Check that event_socket.conf.xml binding to the same IP you're connecting to (e.g. 0.0.0.0 if you're connecting from a remote machine, since the default 127.0.0.1 won't work then) 4. Use netstat on the FS server to verify FreeSWITCH is actually listening on the port you're trying to connect to (I've had a syntax error in the config file make the module fail to load in the past which left FS running but with no ESL socket). (If the module fails to load there'll also be an error in the log file). 5. Check a firewall isn't blocking access to the port
-Steve
On 7 October 2010 01:23, Peter Schrock <peter.schrock@gmail.com> wrote:
Okay, so I managed to get FS working the other day and I even managed to test a call and test my voicemail. All seemed to be working smoothly until, because of the rain here, my power went out and I had to reboot my computer. I logged in through the terminal, set up FS in background went to fs_cli and I get this error message: [ERROR] libs/esl/fs_cli.c:1206 main() Error Connecting [Socket Connection Error] I managed to figure out that in the file "fs_cli.c" on line 1206 you find the code for displaying this error message. The problem is that I don't know why this error message is occurring. Does anyone have any helpful hints as to what I should look at to resolve this problem? I even tried going to the git tree and make current, but that gave me problems that forced me to turn off mod_spandsp and mod_skyopen in the modules.conf, which I had running earlier. Any thoughts? PeterS PS I am not sure if this is of any help, but in addition to the error line above, it also posted this info: Usage: fs_cli [-H <host>] [-P <port>] [-p <secret>] [-d <level>] [-x command] [profile] -?,-h --help Usage Information -H, --host=hostname Host to connect -P, --port=port Port to connect (1 - 65535) -u, --user=user@domain user@domain -p, --password=password Password -x, --execute=command Execute Command and Exit -l, --loglevel=command Log Level -q, --quiet Disable logging -r, --retry Retry connection on failure -R, --reconnect Reconnect if disconnected -d, --debug=level Debug Level (0 - 7)
_______________________________________________ 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
_______________________________________________ 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
That file lists the port that FS listens on for event socket connections. Run a "netstat -nlp | grep <port>" to check which IP that port is being listened on. Then you can use command line switches for fs_cli to force it to connect on that IP/port. Regards HASSAN On 2010-10-12, Peter Schrock <peter.schrock@gmail.com> wrote:
just to make sure what am I comparing event_socket.conf.xml to? I have found that it is set up with the default settings but am not sure how or to what I am suppose to fix. I understand that I am comparing it to FS, but I am wondering if there is some kind of file that I am looking for to compare the two.
PeterS
On Fri, Oct 8, 2010 at 4:56 AM, Steven Ayre <steveayre@gmail.com> wrote:
1. Check FS is running 2. Check the port you're connecting to matches the one in event_socket.conf.xml 3. Check that event_socket.conf.xml binding to the same IP you're connecting to (e.g. 0.0.0.0 if you're connecting from a remote machine, since the default 127.0.0.1 won't work then) 4. Use netstat on the FS server to verify FreeSWITCH is actually listening on the port you're trying to connect to (I've had a syntax error in the config file make the module fail to load in the past which left FS running but with no ESL socket). (If the module fails to load there'll also be an error in the log file). 5. Check a firewall isn't blocking access to the port
-Steve
On 7 October 2010 01:23, Peter Schrock <peter.schrock@gmail.com> wrote:
Okay, so I managed to get FS working the other day and I even managed to test a call and test my voicemail. All seemed to be working smoothly until, because of the rain here, my power went out and I had to reboot my computer. I logged in through the terminal, set up FS in background went to fs_cli and I get this error message: [ERROR] libs/esl/fs_cli.c:1206 main() Error Connecting [Socket Connection Error] I managed to figure out that in the file "fs_cli.c" on line 1206 you find the code for displaying this error message. The problem is that I don't know why this error message is occurring. Does anyone have any helpful hints as to what I should look at to resolve this problem? I even tried going to the git tree and make current, but that gave me problems that forced me to turn off mod_spandsp and mod_skyopen in the modules.conf, which I had running earlier. Any thoughts? PeterS PS I am not sure if this is of any help, but in addition to the error line above, it also posted this info: Usage: fs_cli [-H <host>] [-P <port>] [-p <secret>] [-d <level>] [-x command] [profile] -?,-h --help Usage Information -H, --host=hostname Host to connect -P, --port=port Port to connect (1 - 65535) -u, --user=user@domain user@domain -p, --password=password Password -x, --execute=command Execute Command and Exit -l, --loglevel=command Log Level -q, --quiet Disable logging -r, --retry Retry connection on failure -R, --reconnect Reconnect if disconnected -d, --debug=level Debug Level (0 - 7)
_______________________________________________ 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
_______________________________________________ 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
-- Sent from my mobile device
Try telnet to localhost port 8021 and see if that connects. On Mon, Oct 11, 2010 at 10:21 PM, Nyamul Hassan <mnhassan@usa.net> wrote:
That file lists the port that FS listens on for event socket connections.
Run a "netstat -nlp | grep <port>" to check which IP that port is being listened on.
Then you can use command line switches for fs_cli to force it to connect on that IP/port.
Regards HASSAN
On 2010-10-12, Peter Schrock <peter.schrock@gmail.com> wrote:
just to make sure what am I comparing event_socket.conf.xml to? I have found that it is set up with the default settings but am not sure how or to what I am suppose to fix. I understand that I am comparing it to FS, but I am wondering if there is some kind of file that I am looking for to compare the two.
PeterS
On Fri, Oct 8, 2010 at 4:56 AM, Steven Ayre <steveayre@gmail.com> wrote:
1. Check FS is running 2. Check the port you're connecting to matches the one in event_socket.conf.xml 3. Check that event_socket.conf.xml binding to the same IP you're connecting to (e.g. 0.0.0.0 if you're connecting from a remote machine, since the default 127.0.0.1 won't work then) 4. Use netstat on the FS server to verify FreeSWITCH is actually listening on the port you're trying to connect to (I've had a syntax error in the config file make the module fail to load in the past which left FS running but with no ESL socket). (If the module fails to load there'll also be an error in the log file). 5. Check a firewall isn't blocking access to the port
-Steve
On 7 October 2010 01:23, Peter Schrock <peter.schrock@gmail.com> wrote:
Okay, so I managed to get FS working the other day and I even managed to test a call and test my voicemail. All seemed to be working smoothly until, because of the rain here, my power went out and I had to reboot my computer. I logged in through the terminal, set up FS in background went to fs_cli and I get this error message: [ERROR] libs/esl/fs_cli.c:1206 main() Error Connecting [Socket Connection Error] I managed to figure out that in the file "fs_cli.c" on line 1206 you find the code for displaying this error message. The problem is that I don't know why this error message is occurring. Does anyone have any helpful hints as to what I should look at to resolve this problem? I even tried going to the git tree and make current, but that gave me problems that forced me to turn off mod_spandsp and mod_skyopen in the modules.conf, which I had running earlier. Any thoughts? PeterS PS I am not sure if this is of any help, but in addition to the error line above, it also posted this info: Usage: fs_cli [-H <host>] [-P <port>] [-p <secret>] [-d <level>] [-x command] [profile] -?,-h --help Usage Information -H, --host=hostname Host to connect -P, --port=port Port to connect (1 - 65535) -u, --user=user@domain user@domain -p, --password=password Password -x, --execute=command Execute Command and Exit -l, --loglevel=command Log Level -q, --quiet Disable logging -r, --retry Retry connection on failure -R, --reconnect Reconnect if disconnected -d, --debug=level Debug Level (0 - 7)
_______________________________________________ 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
_______________________________________________ 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
-- Sent from my mobile device
_______________________________________________ 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
-- Anthony Minessale II FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/ Twitter: http://twitter.com/FreeSWITCH_wire AIM: anthm MSN:anthony_minessale@hotmail.com GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com IRC: irc.freenode.net #freeswitch FreeSWITCH Developer Conference sip:888@conference.freeswitch.org googletalk:conf+888@conference.freeswitch.org pstn:+19193869900
Thanks for your help. I don't know what happen but I did the "make current" and rebuilt the whole thing and now it seems to be working fine. At least now I know some tricks to try out to see if I can get it working should it happen again. Thanks again. PeterS On Tue, Oct 12, 2010 at 8:01 AM, Anthony Minessale < anthony.minessale@gmail.com> wrote:
Try telnet to localhost port 8021 and see if that connects.
On Mon, Oct 11, 2010 at 10:21 PM, Nyamul Hassan <mnhassan@usa.net> wrote:
That file lists the port that FS listens on for event socket connections.
Run a "netstat -nlp | grep <port>" to check which IP that port is being listened on.
Then you can use command line switches for fs_cli to force it to connect on that IP/port.
Regards HASSAN
On 2010-10-12, Peter Schrock <peter.schrock@gmail.com> wrote:
just to make sure what am I comparing event_socket.conf.xml to? I have found that it is set up with the default settings but am not sure how or to what I am suppose to fix. I understand that I am comparing it to FS, but I am wondering if there is some kind of file that I am looking for to compare the two.
PeterS
On Fri, Oct 8, 2010 at 4:56 AM, Steven Ayre <steveayre@gmail.com> wrote:
1. Check FS is running 2. Check the port you're connecting to matches the one in event_socket.conf.xml 3. Check that event_socket.conf.xml binding to the same IP you're connecting to (e.g. 0.0.0.0 if you're connecting from a remote machine, since the default 127.0.0.1 won't work then) 4. Use netstat on the FS server to verify FreeSWITCH is actually listening on the port you're trying to connect to (I've had a syntax error in the config file make the module fail to load in the past which left FS running but with no ESL socket). (If the module fails to load there'll also be an error in the log file). 5. Check a firewall isn't blocking access to the port
-Steve
On 7 October 2010 01:23, Peter Schrock <peter.schrock@gmail.com> wrote:
Okay, so I managed to get FS working the other day and I even managed to test a call and test my voicemail. All seemed to be working smoothly until, because of the rain here, my power went out and I had to reboot my computer. I logged in through the terminal, set up FS in background went to fs_cli and I get this error message: [ERROR] libs/esl/fs_cli.c:1206 main() Error Connecting [Socket Connection Error] I managed to figure out that in the file "fs_cli.c" on line 1206 you find the code for displaying this error message. The problem is that I don't know why this error message is occurring. Does anyone have any helpful hints as to what I should look at to resolve this problem? I even tried going to the git tree and make current, but that gave me problems that forced me to turn off mod_spandsp and mod_skyopen in the modules.conf, which I had running earlier. Any thoughts? PeterS PS I am not sure if this is of any help, but in addition to the error line above, it also posted this info: Usage: fs_cli [-H <host>] [-P <port>] [-p <secret>] [-d <level>] [-x command] [profile] -?,-h --help Usage Information -H, --host=hostname Host to connect -P, --port=port Port to connect (1 - 65535) -u, --user=user@domain user@domain -p, --password=password Password -x, --execute=command Execute Command and Exit -l, --loglevel=command Log Level -q, --quiet Disable logging -r, --retry Retry connection on failure -R, --reconnect Reconnect if disconnected -d, --debug=level Debug Level (0 - 7)
_______________________________________________ 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
_______________________________________________ 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
-- Sent from my mobile device
_______________________________________________ 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
-- Anthony Minessale II
FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/ Twitter: http://twitter.com/FreeSWITCH_wire
AIM: anthm MSN:anthony_minessale@hotmail.com <MSN%3Aanthony_minessale@hotmail.com> GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com<PAYPAL%3Aanthony.minessale@gmail.com> IRC: irc.freenode.net #freeswitch
FreeSWITCH Developer Conference sip:888@conference.freeswitch.org <sip%3A888@conference.freeswitch.org> googletalk:conf+888@conference.freeswitch.org<googletalk%3Aconf%2B888@conference.freeswitch.org> pstn:+19193869900
_______________________________________________ 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 (7)
-
Anthony Minessale
-
covici＠ccs.covici.com
-
Mathieu Rene
-
Nyamul Hassan
-
Peter Olsson
-
Peter Schrock
-
Steven Ayre