Or use sysctl to set net.ipv4.ip_nonlocal_bind = 1 That will allow FS to bind to the IP even when it does not have that IP. It won't receive traffic until the machine takes control of that IP, but will allow FS to start up before that time so that it'll start handling calls as soon as it fails over. You could also look at an approach like this http://wiki.freeswitch.org/wiki/Enterprise_deployment_OpenSIPS if you have another couple of servers available. -Steve On 8 July 2010 14:53, Rupa Schomaker <rupa@rupa.com> wrote:
instead of stopping/starting FS, why not stop/start just the appropriate sofia profile? That should be much faster. You can script it using fs_cli -x "sofia ..."
On Thu, Jul 8, 2010 at 5:11 AM, viewpoint <yurazilot1@list.ru> wrote:
Hello.
I currently have a project where I'm researching how to establish a clustered platform wieth failover time ~= some milliseconds.
At present we have: 2 identical servers FS, wieth established Pacemaker ( http://www.clusterlabs.org/wiki/Install#From_Source) - heartbeat. On the one hand it is possible to tell that all works, as, at refusal of the first server, the second server receives cluster-ip. A problem that FreeSWITCH it is necessary to restart (or simply to start) that it began to work with the new IP-address. As the result, a switching total time makes 10-20 sec which basic part is necessary on launch FreeSwitch.
any ideas?
Thanks.
_______________________________________________ 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
-- -Rupa
_______________________________________________ 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