Any reason you have FS installed in two locations?
You can save some disk space by two versions from the same path.
ss5:/opt/freeswitch/bin# ./freeswitch --help
these are the optional arguments you can pass to freeswitch
-nf -- no forking
-u [user] -- specify user to switch to
-g [group] -- specify group to switch to
-help -- this message
-version -- print the version and exit
-waste -- allow memory waste
-core -- dump cores
-hp -- enable high priority settings
-vg -- run under valgrind
-nosql -- disable internal sql scoreboard
-heavy-timer -- Heavy Timer, possibly more accurate but at a cost
-nonat -- disable auto nat detection
-nocal -- disable clock calibration
-nort -- disable clock clock_realtime
-stop -- stop freeswitch
-nc -- do not output to a console and background
-ncwait -- do not output to a console and background but wait until the system is ready before exiting (implies -nc)
-c -- output to a console and stay in the foreground
-conf [confdir] -- specify an alternate config dir
-log [logdir] -- specify an alternate log dir
-run [rundir] -- specify an alternate run dir
-db [dbdir] -- specify an alternate db dir
-mod [moddir] -- specify an alternate mod dir
-htdocs [htdocsdir] -- specify an alternate htdocs dir
-scripts [scriptsdir] -- specify an alternate scripts dir
Those last -conf -log -run -db options would let you use different directories for configs, logs and sqlite databases per-instance but use the same binaries and modules.
Of course there's no reason not to do it the way you are now - it'll just save a bit of space this way.
You can also use two SIP profiles to have the same FS process listen on 2 different IPs. I guess you have a reason though for having them separated into two processes though.
-Steve
/usr/local/FS_1/bin/fs_cli -P 8021
/usr/local/FS_2/bin/fs_cli -P 8022
fs_cll doesn't read any config file. It's not part of the FS server at all, you can have it on a different machine that doesn't have FS installed. It entirely relies on the arguments to control where to connect to.
-SteveOn 11 January 2011 15:04, Sam <u2nsam@gmail.com> wrote:
Something more here ... i am getting the console for 192.168.2.1 every time i do fs_cli on both instances .
like
/usr/local/FS_1/bin/fs_cli
/usr/localFS_2/bin/fs_cli
i get the console for the 1st server only
the 2 server are listing to 2 different ips .
Regds
SamOn Tue, Jan 11, 2011 at 8:07 PM, Steven Ayre <steveayre@gmail.com> wrote:
It should work. Is there anything already listening on port 8022?
$ netstat -a -n -p | grep 8022
Are you also sure that they're not both loading the same config file?
Regards,
-Steve
On 11 January 2011 14:32, Sam <u2nsam@gmail.com> wrote:
> the scenario is i have 2 ips on 1 server for 2 FS instances;
>
> 192.168.2.1
> 192.168.2.2
>
> and the parameters i have set is:-
>
> for
> 192.168.2.1:-
> <param name="listen-ip" value="127.0.0.1"/>
> <param name="listen-port" value="8021"/>
> for
> 192.168.2.2:-
> <param name="listen-ip" value="127.0.0.1"/>
> <param name="listen-port" value="8022"/>
>
> Ideally it should work but i am getting console for only 192.168.2.1 FS .
>
>
> Regards
> Sam
>
> On Tue, Jan 11, 2011 at 4:20 PM, Steven Ayre <steveayre@gmail.com> wrote:
>>
>> <param name="listen-ip" value="127.0.0.1"/>
>> <param name="listen-port" value="8021"/>
>>
>> You can bind both to port 8021 on their individual IPs, or different
>> ports on the same IP.
>>
>> A listen IP of 0.0.0.0 will mean any IP.
>>
>> -Steve
>>
>> On 11 January 2011 10:44, Sam <u2nsam@gmail.com> wrote:
>> > A query,
>> >
>> > I have 2 FS running on one server on 2 different ips,
>> > so when i do fs_cli going to respective bins , i see console of only the
>> > first server.
>> >
>> > Is there any way to get the console of both the FS on the same server .
>> > I tried changing the port of event socket to 8022 but it donot works.
>> > <param name="listen-port" value="8022"/>
>> >
>> > Is there some method to start the console of both the instances.
>> >
>> > Regds
>> > Sam
>> >
>> > _______________________________________________
>> > 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
>
>
_______________________________________________
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