[Freeswitch-users] Problems with fs_cli on OS X 10.6.4

[Nyamul Hassan]

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 at 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 at 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 at 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 at domain          user at 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 at 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 at 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