Ok,
figured out from your post to load the FS-CLI in order to run the Sophia status
Michael mentioned.
Now
I get: [ERROR] libs/esl/fs_cli.c.639 main() Error Connecting [Socket Connection
Error] when running ./fs_cli from a terminal window in
/usr/local/freeswitch/bin where fs_cli is located.
Mike
From:
freeswitch-users-bounces@lists.freeswitch.org
[mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Michael
Jerris
Sent: Tuesday, August 25, 2009 12:39 PM
To: freeswitch-users@lists.freeswitch.org
Subject: Re: [Freeswitch-users] Moved Freeswitch to new subnet.
if you want to run that at your prompt instead of at the
fs_cli you can do this:
function sofia() { fs_cli -x "$(echo "sofia $@")";
}
(thanks ray for the bash foo)
Mike
On Aug 25, 2009, at 1:04 PM, Mike Peace wrote:
I
get a bash: sofia: command not found. Is there something I need to add to my
config to use these commands?
From: freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Michael Collins
Sent: Tuesday, August 25,
2009 10:55 AM
To: freeswitch-users@lists.freeswitch.org
Subject: Re:
[Freeswitch-users] Moved Freeswitch to new subnet.
Hmm... can you fire up FS and then do "sofia
status" and tell us if the internal profile looks okay? Also, do
"sofia status profile internal" and capture the output. Something
fishy is going on...
-MC
Mike Peace
Network Analyst
EDCO, The Document People
Direct 417-447-3367