I didn't know that. Thanks Russell.
>
>
>
> You've mentioned this twice, now, but a better way to do it is to _not_
> stop FreeSwitch. Instead, run /usr/local/freeswitch/bin/fs_cli, which
> connects to FS, and then you can do everything that you can do directly in
> FS. When you are done, enter "
Russell Mosemann wrote:
>
> Yup, I got the slashes wrong, and I was staring right at the commands when I
> wrote the message. I'll blame it on how late it is here. :-) It should be
> "/quit", "/bye", "/exit" and "/help".
ctrl-d is also recognized and it's easier to type.
__
> When you are done, enter "\quit" or "\bye" or "\exit". See "\help" and
> "help" for more information.
Yup, I got the slashes wrong, and I was staring right at the commands when I
wrote the message. I'll blame it on how late it is here. :-) It should be
"/quit", "/bye", "/exit" and "/help".
--
Michael Gende wrote:
> Hit option 8 and you'll go to a shell. I'm assuming you can get around in
> Linux or Unix (If not, tell me). "ps aux | grep free" and kill the PID for
> FS (pfsense runs FS in the background) Then, invoke FS with
> /usr/local/freeswitch/bin/freeswitch.
You've mentioned this
Hey Orien,
pfsense has a nice interface, but I only use it for adding the FS package,
maybe messing with LAN and WAN addresses. Using the "command line" helped me
to better understand what FS was doing and how. Pfsense just made it easier
to have an OS and really good firewall married to FS withou
Mike,
I copied the status screen from the freeswitch package in the web
setup. I you need a console view, I will need instructions on how to
console into pfsense, Since I have never done that.
Orien L.
Name Type
DataState
