<div dir="ltr">What about DNS SRV?</div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Feb 11, 2016 at 2:00 PM, Stanislav Sinyagin <span dir="ltr"><<a href="mailto:ssinyagin@gmail.com" target="_blank">ssinyagin@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">hi Emrah and all,<br>
<br>
it's the first time I actually searched for it, but there are hosting<br>
offers with anycast IP routing. It means, you have multiple servers in<br>
various locations, and they share the same service IP address. The<br>
clients connect to the nearest server, which is determined by standard<br>
BGP routing. You are still limited to a single global hosting<br>
provider, but you benefit from its redundant network and geographical<br>
distribution.<br>
<br>
In case of anycast addressing, incoming connections will be served<br>
easily. But the outgoing connections are rather tricky: you will need<br>
to bring the outbound call to the physical server where the user has<br>
registered, and initiate the connection from its anycast address. So,<br>
you can share and replicate the registration database, but you need to<br>
send the outbound call to the server which accepted the registration.<br>
I guess you should be able to retrieve this information from the<br>
registration database. This needs to be looked in details.<br>
<br>
Google for anycast server hosting, and there are at least 3 providers<br>
offering virtual hosts, and OVH is offering physical hosts as well. I<br>
guess there are more providers with similar offerings.<br>
<br>
<br>
Without anycast, you would need to use redundant registrars sharing<br>
the same service IP address -- for example, Digitalocean offers such<br>
service within any single datacenter.<br>
<br>
Having multiple registrars with different IP addresses is also<br>
possible, but then you depend on the way how each particular SIP<br>
client handles multiple IP addresses after resolving the domain name.<br>
Some of them may get stuck to a single address, even if it's not<br>
responding.<br>
<br>
<br>
cheers,<br>
stanislav<br>
<div class="HOEnZb"><div class="h5"><br>
On Thu, Feb 11, 2016 at 5:53 PM, Emrah <<a href="mailto:lists@kavun.ch">lists@kavun.ch</a>> wrote:<br>
> Hi list,<br>
> I’m writing to gather your thoughts and suggestions on how to have a high availability FS setup on different networks.<br>
><br>
> I am trying to achieve the following:<br>
> - Load balance FreeSWITCH instances on 2 or more servers, possibly in different countries.<br>
> - Shared user directory and dialplan, but I’m not sure if shared registrations would make sense.<br>
> - If a server goes down, the phone should register on the alternative servers. Obviously we can’t keep calls up.<br>
><br>
> I’m obviously not the first one out there doing this. I’m trying to learn from those who’ve come up with reliable solutions.<br>
><br>
> I’ve tried sharing a registration table among multiple FS instances. But it was a beginners mistake. Even with the right path to reach the client, only the invites sent from the server used by the phone would be processed.<br>
> If my phone registers on server A, then server A shares the info with server B, server B knows how to contact the phone but it won’t be able to. Supposedly because of NAT issues.<br>
><br>
> I am aiming for fully independent FS instances that can back each other up and be used independently. I am guessing this would require some sort of SBC or external registrar server with a Kamailio or Repro.<br>
><br>
> Anyway just trying to spark the conversation around this subject and hopefully we can come up with a formula that can help many with their FS deployments. My provider’s network just went all down in IPv4 and HA behind the same provider proved to be useless.<br>
><br>
> Best,<br>
> E<br>
> _________________________________________________________________________<br>
> Professional FreeSWITCH Consulting Services:<br>
> <a href="mailto:consulting@freeswitch.org">consulting@freeswitch.org</a><br>
> <a href="http://www.freeswitchsolutions.com" rel="noreferrer" target="_blank">http://www.freeswitchsolutions.com</a><br>
><br>
> Official FreeSWITCH Sites<br>
> <a href="http://www.freeswitch.org" rel="noreferrer" target="_blank">http://www.freeswitch.org</a><br>
> <a href="http://confluence.freeswitch.org" rel="noreferrer" target="_blank">http://confluence.freeswitch.org</a><br>
> <a href="http://www.cluecon.com" rel="noreferrer" target="_blank">http://www.cluecon.com</a><br>
><br>
> FreeSWITCH-users mailing list<br>
> <a href="mailto:FreeSWITCH-users@lists.freeswitch.org">FreeSWITCH-users@lists.freeswitch.org</a><br>
> <a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" rel="noreferrer" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
> UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" rel="noreferrer" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
> <a href="http://www.freeswitch.org" rel="noreferrer" target="_blank">http://www.freeswitch.org</a><br>
<br>
_________________________________________________________________________<br>
Professional FreeSWITCH Consulting Services:<br>
<a href="mailto:consulting@freeswitch.org">consulting@freeswitch.org</a><br>
<a href="http://www.freeswitchsolutions.com" rel="noreferrer" target="_blank">http://www.freeswitchsolutions.com</a><br>
<br>
Official FreeSWITCH Sites<br>
<a href="http://www.freeswitch.org" rel="noreferrer" target="_blank">http://www.freeswitch.org</a><br>
<a href="http://confluence.freeswitch.org" rel="noreferrer" target="_blank">http://confluence.freeswitch.org</a><br>
<a href="http://www.cluecon.com" rel="noreferrer" target="_blank">http://www.cluecon.com</a><br>
<br>
FreeSWITCH-users mailing list<br>
<a href="mailto:FreeSWITCH-users@lists.freeswitch.org">FreeSWITCH-users@lists.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" rel="noreferrer" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" rel="noreferrer" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
<a href="http://www.freeswitch.org" rel="noreferrer" target="_blank">http://www.freeswitch.org</a></div></div></blockquote></div><br></div>