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
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!