Then I suggest you to simply run the command "freeswitch" without any parameters so you can see at the startup console why the Freeswitch process is hanging up.

It could be a wrong parameter into some XML file or whatever..


BTW, why not using a stable version (I mean 1.4) rather than a development version?

Cheers
Max




Il giorno 17/nov/2014, alle ore 14:01, akhil garg ha scritto:

fs_cli still not opening after running "./freeswitch -nonat"



Regards,
Akhil

On Mon, Nov 17, 2014 at 6:19 PM, akhil garg <akhilgarg7@gmail.com> wrote:
sorry, I am using freeswitch version 1.5.6b

On Mon, Nov 17, 2014 at 6:08 PM, akhil garg <akhilgarg7@gmail.com> wrote:
Hi,
I am using 1.5.4b freeswitch release.

I am running freeswitch by commands "freeswtich" or "freeswtich -nc"

running fs_cli hangs.
it gives no output.

I could see the socket is open by running command "netstat -anlp | grep 8021"
"tcp        0      0 127.0.0.1:8021          0.0.0.0:*               LISTEN      3084/freeswitch"



Please help

--
regards,
akhil



--
regards,
akhil



--
regards,
akhil
_________________________________________________________________________
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