For the 'HA configuration' part, there is also this page (well, pages): http://wiki.freeswitch.org/wiki/Enterprise_deployment Which discusses a few ways to get high availability through things like SRV DNS, Heartbeat etc. The Freeswitch_HA page content was initially only for the sofia recover features that allows calls to be restarted after a crash or server migration. -Steve On 19 October 2010 12:07, Tihomir Culjaga <tculjaga@gmail.com> wrote:
On Tue, Oct 19, 2010 at 12:39 PM, Seven Du <dujinfang@gmail.com> wrote:
Anyone are welcome to help document it consistent and sufficient.
On Tue, Oct 19, 2010 at 6:07 PM, Tihomir Culjaga <tculjaga@gmail.com> wrote:
On Tue, Oct 19, 2010 at 4:16 AM, Seven Du <dujinfang@gmail.com> wrote:
Yes, just google freeswitch ha
ok, why don't we document it properly?
the information on this page is inconsistent and insufficient.
Please don't get me wrong, i can do it ... the only thing is that i missing the 2nd installed server and test it properly.
can you, please describe this:
sysctl to set net.ipv4.ip_nonlocal_bind = 1 or /proc/sys/net/ipv4/ip_nonlocal_bind
does it mean i can configure both FS to bind to an IP address that i will keep floating between 2 servers:
from vars.conf <X-PRE-PROCESS cmd="set" data="bind_server_ip=10.1.1.100"/>
assuming my floating IP is 10.1.1.100.
is that correct ?
regarding your NAT issue, i guess we can overcome it by butting FS out of media path
uuid_media off <uuid> uuid_media <uuid>
maybe there is something general that can do the job for all ongoing calls....
anyhow, im going to do it once i got the 2nd server installed ...
_______________________________________________ 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