High availability on different networks
Hi list, I’m writing to gather your thoughts and suggestions on how to have a high availability FS setup on different networks. I am trying to achieve the following: - Load balance FreeSWITCH instances on 2 or more servers, possibly in different countries. - Shared user directory and dialplan, but I’m not sure if shared registrations would make sense. - If a server goes down, the phone should register on the alternative servers. Obviously we can’t keep calls up. 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. 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. 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. 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. 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. Best, E
hi Emrah and all, it's the first time I actually searched for it, but there are hosting offers with anycast IP routing. It means, you have multiple servers in various locations, and they share the same service IP address. The clients connect to the nearest server, which is determined by standard BGP routing. You are still limited to a single global hosting provider, but you benefit from its redundant network and geographical distribution. In case of anycast addressing, incoming connections will be served easily. But the outgoing connections are rather tricky: you will need to bring the outbound call to the physical server where the user has registered, and initiate the connection from its anycast address. So, you can share and replicate the registration database, but you need to send the outbound call to the server which accepted the registration. I guess you should be able to retrieve this information from the registration database. This needs to be looked in details. Google for anycast server hosting, and there are at least 3 providers offering virtual hosts, and OVH is offering physical hosts as well. I guess there are more providers with similar offerings. Without anycast, you would need to use redundant registrars sharing the same service IP address -- for example, Digitalocean offers such service within any single datacenter. Having multiple registrars with different IP addresses is also possible, but then you depend on the way how each particular SIP client handles multiple IP addresses after resolving the domain name. Some of them may get stuck to a single address, even if it's not responding. cheers, stanislav On Thu, Feb 11, 2016 at 5:53 PM, Emrah <lists@kavun.ch> wrote:
Hi list, I’m writing to gather your thoughts and suggestions on how to have a high availability FS setup on different networks.
I am trying to achieve the following: - Load balance FreeSWITCH instances on 2 or more servers, possibly in different countries. - Shared user directory and dialplan, but I’m not sure if shared registrations would make sense. - If a server goes down, the phone should register on the alternative servers. Obviously we can’t keep calls up.
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.
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. 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.
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.
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.
Best, E _________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
What about DNS SRV? On Thu, Feb 11, 2016 at 2:00 PM, Stanislav Sinyagin <ssinyagin@gmail.com> wrote:
hi Emrah and all,
it's the first time I actually searched for it, but there are hosting offers with anycast IP routing. It means, you have multiple servers in various locations, and they share the same service IP address. The clients connect to the nearest server, which is determined by standard BGP routing. You are still limited to a single global hosting provider, but you benefit from its redundant network and geographical distribution.
In case of anycast addressing, incoming connections will be served easily. But the outgoing connections are rather tricky: you will need to bring the outbound call to the physical server where the user has registered, and initiate the connection from its anycast address. So, you can share and replicate the registration database, but you need to send the outbound call to the server which accepted the registration. I guess you should be able to retrieve this information from the registration database. This needs to be looked in details.
Google for anycast server hosting, and there are at least 3 providers offering virtual hosts, and OVH is offering physical hosts as well. I guess there are more providers with similar offerings.
Without anycast, you would need to use redundant registrars sharing the same service IP address -- for example, Digitalocean offers such service within any single datacenter.
Having multiple registrars with different IP addresses is also possible, but then you depend on the way how each particular SIP client handles multiple IP addresses after resolving the domain name. Some of them may get stuck to a single address, even if it's not responding.
cheers, stanislav
On Thu, Feb 11, 2016 at 5:53 PM, Emrah <lists@kavun.ch> wrote:
Hi list, I’m writing to gather your thoughts and suggestions on how to have a high availability FS setup on different networks.
I am trying to achieve the following: - Load balance FreeSWITCH instances on 2 or more servers, possibly in different countries. - Shared user directory and dialplan, but I’m not sure if shared registrations would make sense. - If a server goes down, the phone should register on the alternative servers. Obviously we can’t keep calls up.
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.
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. 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.
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.
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.
Best, E _________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
I use A record updated to point active FS servers in geo-distributed cluster. I DNS server i can recommend use Amazon Route53 On Thu, Feb 11, 2016 at 10:27 PM, Vik Killa <vipkilla@gmail.com> wrote:
What about DNS SRV?
On Thu, Feb 11, 2016 at 2:00 PM, Stanislav Sinyagin <ssinyagin@gmail.com> wrote:
hi Emrah and all,
it's the first time I actually searched for it, but there are hosting offers with anycast IP routing. It means, you have multiple servers in various locations, and they share the same service IP address. The clients connect to the nearest server, which is determined by standard BGP routing. You are still limited to a single global hosting provider, but you benefit from its redundant network and geographical distribution.
In case of anycast addressing, incoming connections will be served easily. But the outgoing connections are rather tricky: you will need to bring the outbound call to the physical server where the user has registered, and initiate the connection from its anycast address. So, you can share and replicate the registration database, but you need to send the outbound call to the server which accepted the registration. I guess you should be able to retrieve this information from the registration database. This needs to be looked in details.
Google for anycast server hosting, and there are at least 3 providers offering virtual hosts, and OVH is offering physical hosts as well. I guess there are more providers with similar offerings.
Without anycast, you would need to use redundant registrars sharing the same service IP address -- for example, Digitalocean offers such service within any single datacenter.
Having multiple registrars with different IP addresses is also possible, but then you depend on the way how each particular SIP client handles multiple IP addresses after resolving the domain name. Some of them may get stuck to a single address, even if it's not responding.
cheers, stanislav
On Thu, Feb 11, 2016 at 5:53 PM, Emrah <lists@kavun.ch> wrote:
Hi list, I’m writing to gather your thoughts and suggestions on how to have a high availability FS setup on different networks.
I am trying to achieve the following: - Load balance FreeSWITCH instances on 2 or more servers, possibly in different countries. - Shared user directory and dialplan, but I’m not sure if shared registrations would make sense. - If a server goes down, the phone should register on the alternative servers. Obviously we can’t keep calls up.
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.
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. 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.
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.
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.
Best, E
_________________________________________________________________________
Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
Read this https://okay.com.mx/en/entrepreneurs/balancing-clustering-and-high-availabil... It is just what you're looking for. Take the ideas and modify it to your needs Le 11 févr. 2016 3:17 PM, "Sergey Safarov" <s.safarov@gmail.com> a écrit :
I use A record updated to point active FS servers in geo-distributed cluster. I DNS server i can recommend use Amazon Route53
On Thu, Feb 11, 2016 at 10:27 PM, Vik Killa <vipkilla@gmail.com> wrote:
What about DNS SRV?
On Thu, Feb 11, 2016 at 2:00 PM, Stanislav Sinyagin <ssinyagin@gmail.com> wrote:
hi Emrah and all,
it's the first time I actually searched for it, but there are hosting offers with anycast IP routing. It means, you have multiple servers in various locations, and they share the same service IP address. The clients connect to the nearest server, which is determined by standard BGP routing. You are still limited to a single global hosting provider, but you benefit from its redundant network and geographical distribution.
In case of anycast addressing, incoming connections will be served easily. But the outgoing connections are rather tricky: you will need to bring the outbound call to the physical server where the user has registered, and initiate the connection from its anycast address. So, you can share and replicate the registration database, but you need to send the outbound call to the server which accepted the registration. I guess you should be able to retrieve this information from the registration database. This needs to be looked in details.
Google for anycast server hosting, and there are at least 3 providers offering virtual hosts, and OVH is offering physical hosts as well. I guess there are more providers with similar offerings.
Without anycast, you would need to use redundant registrars sharing the same service IP address -- for example, Digitalocean offers such service within any single datacenter.
Having multiple registrars with different IP addresses is also possible, but then you depend on the way how each particular SIP client handles multiple IP addresses after resolving the domain name. Some of them may get stuck to a single address, even if it's not responding.
cheers, stanislav
On Thu, Feb 11, 2016 at 5:53 PM, Emrah <lists@kavun.ch> wrote:
Hi list, I’m writing to gather your thoughts and suggestions on how to have a high availability FS setup on different networks.
I am trying to achieve the following: - Load balance FreeSWITCH instances on 2 or more servers, possibly in different countries. - Shared user directory and dialplan, but I’m not sure if shared registrations would make sense. - If a server goes down, the phone should register on the alternative servers. Obviously we can’t keep calls up.
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.
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. 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.
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.
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.
Best, E
_________________________________________________________________________
Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
Luis, This mailing list is a Freeswitch users list, this list is for users to help each other with freeswitch, not a place to advertise your services, you may want to look at the freeswitch biz list http://lists.freeswitch.org/mailman/listinfo/freeswitch-biz Thanks, Moishe Grunstein Tornado Computer Systems, Inc. 212.400.7650 888.IPPBX.US Service Request Email: support@nysolutions.com<mailto:support@nysolutions.com> [cid:image001.jpg@01C72F94.9EE45D60]<http://www.nysolutions.com/> Computer Networking * Managed Services * IP Video Surveillance * Network Assessments * Web Solutions * Voice over IP * Disaster Recovery * Network Security * Site Surveys * CMS From: freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Luis Daniel Lucio Quiroz Sent: Thursday, February 11, 2016 9:40 PM To: FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org> Subject: Re: [Freeswitch-users] High availability on different networks Read this https://okay.com.mx/en/entrepreneurs/balancing-clustering-and-high-availabil... It is just what you're looking for. Take the ideas and modify it to your needs Le 11 févr. 2016 3:17 PM, "Sergey Safarov" <s.safarov@gmail.com<mailto:s.safarov@gmail.com>> a écrit : I use A record updated to point active FS servers in geo-distributed cluster. I DNS server i can recommend use Amazon Route53 On Thu, Feb 11, 2016 at 10:27 PM, Vik Killa <vipkilla@gmail.com<mailto:vipkilla@gmail.com>> wrote: What about DNS SRV? On Thu, Feb 11, 2016 at 2:00 PM, Stanislav Sinyagin <ssinyagin@gmail.com<mailto:ssinyagin@gmail.com>> wrote: hi Emrah and all, it's the first time I actually searched for it, but there are hosting offers with anycast IP routing. It means, you have multiple servers in various locations, and they share the same service IP address. The clients connect to the nearest server, which is determined by standard BGP routing. You are still limited to a single global hosting provider, but you benefit from its redundant network and geographical distribution. In case of anycast addressing, incoming connections will be served easily. But the outgoing connections are rather tricky: you will need to bring the outbound call to the physical server where the user has registered, and initiate the connection from its anycast address. So, you can share and replicate the registration database, but you need to send the outbound call to the server which accepted the registration. I guess you should be able to retrieve this information from the registration database. This needs to be looked in details. Google for anycast server hosting, and there are at least 3 providers offering virtual hosts, and OVH is offering physical hosts as well. I guess there are more providers with similar offerings. Without anycast, you would need to use redundant registrars sharing the same service IP address -- for example, Digitalocean offers such service within any single datacenter. Having multiple registrars with different IP addresses is also possible, but then you depend on the way how each particular SIP client handles multiple IP addresses after resolving the domain name. Some of them may get stuck to a single address, even if it's not responding. cheers, stanislav On Thu, Feb 11, 2016 at 5:53 PM, Emrah <lists@kavun.ch<mailto:lists@kavun.ch>> wrote:
Hi list, I’m writing to gather your thoughts and suggestions on how to have a high availability FS setup on different networks.
I am trying to achieve the following: - Load balance FreeSWITCH instances on 2 or more servers, possibly in different countries. - Shared user directory and dialplan, but I’m not sure if shared registrations would make sense. - If a server goes down, the phone should register on the alternative servers. Obviously we can’t keep calls up.
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.
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. 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.
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.
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.
Best, E _________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org<mailto:consulting@freeswitch.org> http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org<mailto: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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org<mailto:consulting@freeswitch.org> http://www.freeswitchsolutions.com Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org<mailto: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 _________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org<mailto:consulting@freeswitch.org> http://www.freeswitchsolutions.com Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org<mailto: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 _________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org<mailto:consulting@freeswitch.org> http://www.freeswitchsolutions.com Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org<mailto: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
there is an issue with anycast routing though: when you bring up a new server, some running sessions will be dropped, because their IP packets would be routed to a different host. So, it needs a careful design. Maybe place only the SIP proxy on an anycast address, and run the calls from unique local addresses. Multiple DNS SRV records with different priorities are also possible, but you can't direct the users to the nearest location within the same domain. Also a bunch of SIP clients needs to be tested and you need to answer the questions, like: -- what is the timeout if the primary server is unavailable? -- if the primary host goes down during the call, how soon can the client re-dial? -- what happens if the primary server comes up again? On Thu, Feb 11, 2016 at 8:00 PM, Stanislav Sinyagin <ssinyagin@gmail.com> wrote:
hi Emrah and all,
it's the first time I actually searched for it, but there are hosting offers with anycast IP routing. It means, you have multiple servers in various locations, and they share the same service IP address. The clients connect to the nearest server, which is determined by standard BGP routing. You are still limited to a single global hosting provider, but you benefit from its redundant network and geographical distribution.
In case of anycast addressing, incoming connections will be served easily. But the outgoing connections are rather tricky: you will need to bring the outbound call to the physical server where the user has registered, and initiate the connection from its anycast address. So, you can share and replicate the registration database, but you need to send the outbound call to the server which accepted the registration. I guess you should be able to retrieve this information from the registration database. This needs to be looked in details.
Google for anycast server hosting, and there are at least 3 providers offering virtual hosts, and OVH is offering physical hosts as well. I guess there are more providers with similar offerings.
Without anycast, you would need to use redundant registrars sharing the same service IP address -- for example, Digitalocean offers such service within any single datacenter.
Having multiple registrars with different IP addresses is also possible, but then you depend on the way how each particular SIP client handles multiple IP addresses after resolving the domain name. Some of them may get stuck to a single address, even if it's not responding.
cheers, stanislav
On Thu, Feb 11, 2016 at 5:53 PM, Emrah <lists@kavun.ch> wrote:
Hi list, I’m writing to gather your thoughts and suggestions on how to have a high availability FS setup on different networks.
I am trying to achieve the following: - Load balance FreeSWITCH instances on 2 or more servers, possibly in different countries. - Shared user directory and dialplan, but I’m not sure if shared registrations would make sense. - If a server goes down, the phone should register on the alternative servers. Obviously we can’t keep calls up.
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.
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. 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.
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.
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.
Best, E _________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
It's not instant, but I've used OVH failover IP's to do that sort of thing. Heartbeat over ipsec tunnel, use pacemaker with a custom script that does the OVH API call to move the IP address. Sadly it's not that quick, takes about 2 minutes. On 12 February 2016 at 07:40, Stanislav Sinyagin <ssinyagin@gmail.com> wrote:
there is an issue with anycast routing though: when you bring up a new server, some running sessions will be dropped, because their IP packets would be routed to a different host. So, it needs a careful design. Maybe place only the SIP proxy on an anycast address, and run the calls from unique local addresses.
Multiple DNS SRV records with different priorities are also possible, but you can't direct the users to the nearest location within the same domain. Also a bunch of SIP clients needs to be tested and you need to answer the questions, like:
-- what is the timeout if the primary server is unavailable? -- if the primary host goes down during the call, how soon can the client re-dial? -- what happens if the primary server comes up again?
On Thu, Feb 11, 2016 at 8:00 PM, Stanislav Sinyagin <ssinyagin@gmail.com> wrote:
hi Emrah and all,
it's the first time I actually searched for it, but there are hosting offers with anycast IP routing. It means, you have multiple servers in various locations, and they share the same service IP address. The clients connect to the nearest server, which is determined by standard BGP routing. You are still limited to a single global hosting provider, but you benefit from its redundant network and geographical distribution.
In case of anycast addressing, incoming connections will be served easily. But the outgoing connections are rather tricky: you will need to bring the outbound call to the physical server where the user has registered, and initiate the connection from its anycast address. So, you can share and replicate the registration database, but you need to send the outbound call to the server which accepted the registration. I guess you should be able to retrieve this information from the registration database. This needs to be looked in details.
Google for anycast server hosting, and there are at least 3 providers offering virtual hosts, and OVH is offering physical hosts as well. I guess there are more providers with similar offerings.
Without anycast, you would need to use redundant registrars sharing the same service IP address -- for example, Digitalocean offers such service within any single datacenter.
Having multiple registrars with different IP addresses is also possible, but then you depend on the way how each particular SIP client handles multiple IP addresses after resolving the domain name. Some of them may get stuck to a single address, even if it's not responding.
cheers, stanislav
On Thu, Feb 11, 2016 at 5:53 PM, Emrah <lists@kavun.ch> wrote:
Hi list, I’m writing to gather your thoughts and suggestions on how to have a high availability FS setup on different networks.
I am trying to achieve the following: - Load balance FreeSWITCH instances on 2 or more servers, possibly in different countries. - Shared user directory and dialplan, but I’m not sure if shared registrations would make sense. - If a server goes down, the phone should register on the alternative servers. Obviously we can’t keep calls up.
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.
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. 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.
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.
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.
Best, E
Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
-- *Andrew Cassidy BSc (Hons) MBCS SSCA* Managing Director *T <info@cassidywebservices.co.uk> *03300 100 960 *F <info@cassidywebservices.co.uk> *03300 100 961 *E <info@cassidywebservices.co.uk> *andrew@cassidywebservices.co.uk *W <info@cassidywebservices.co.uk> *www.cassidywebservices.co.uk
as Sergey has proposed, there could be a DNS service which monitors the availability of your VoIP servers and changes the DNS entries if a server goes down. The TTL for individual SRV records could be set to few seconds. But that means again that all users are using the same server, so it's not really a distributed model as Emrah challenged in the original mail. Probably this new project will help in building a distributed cluster, but it needs a detailed study: https://ipfs.io/ On Fri, Feb 12, 2016 at 10:09 AM, Andrew Cassidy < andrew@cassidywebservices.co.uk> wrote:
It's not instant, but I've used OVH failover IP's to do that sort of thing. Heartbeat over ipsec tunnel, use pacemaker with a custom script that does the OVH API call to move the IP address.
Sadly it's not that quick, takes about 2 minutes.
On 12 February 2016 at 07:40, Stanislav Sinyagin <ssinyagin@gmail.com> wrote:
there is an issue with anycast routing though: when you bring up a new server, some running sessions will be dropped, because their IP packets would be routed to a different host. So, it needs a careful design. Maybe place only the SIP proxy on an anycast address, and run the calls from unique local addresses.
Multiple DNS SRV records with different priorities are also possible, but you can't direct the users to the nearest location within the same domain. Also a bunch of SIP clients needs to be tested and you need to answer the questions, like:
-- what is the timeout if the primary server is unavailable? -- if the primary host goes down during the call, how soon can the client re-dial? -- what happens if the primary server comes up again?
On Thu, Feb 11, 2016 at 8:00 PM, Stanislav Sinyagin <ssinyagin@gmail.com> wrote:
hi Emrah and all,
it's the first time I actually searched for it, but there are hosting offers with anycast IP routing. It means, you have multiple servers in various locations, and they share the same service IP address. The clients connect to the nearest server, which is determined by standard BGP routing. You are still limited to a single global hosting provider, but you benefit from its redundant network and geographical distribution.
In case of anycast addressing, incoming connections will be served easily. But the outgoing connections are rather tricky: you will need to bring the outbound call to the physical server where the user has registered, and initiate the connection from its anycast address. So, you can share and replicate the registration database, but you need to send the outbound call to the server which accepted the registration. I guess you should be able to retrieve this information from the registration database. This needs to be looked in details.
Google for anycast server hosting, and there are at least 3 providers offering virtual hosts, and OVH is offering physical hosts as well. I guess there are more providers with similar offerings.
Without anycast, you would need to use redundant registrars sharing the same service IP address -- for example, Digitalocean offers such service within any single datacenter.
Having multiple registrars with different IP addresses is also possible, but then you depend on the way how each particular SIP client handles multiple IP addresses after resolving the domain name. Some of them may get stuck to a single address, even if it's not responding.
cheers, stanislav
On Thu, Feb 11, 2016 at 5:53 PM, Emrah <lists@kavun.ch> wrote:
Hi list, I’m writing to gather your thoughts and suggestions on how to have a high availability FS setup on different networks.
I am trying to achieve the following: - Load balance FreeSWITCH instances on 2 or more servers, possibly in different countries. - Shared user directory and dialplan, but I’m not sure if shared registrations would make sense. - If a server goes down, the phone should register on the alternative servers. Obviously we can’t keep calls up.
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.
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. 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.
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.
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.
Best, E
Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
-- *Andrew Cassidy BSc (Hons) MBCS SSCA* Managing Director
*T <info@cassidywebservices.co.uk> *03300 100 960 *F <info@cassidywebservices.co.uk> *03300 100 961 *E <info@cassidywebservices.co.uk> *andrew@cassidywebservices.co.uk *W <info@cassidywebservices.co.uk> *www.cassidywebservices.co.uk
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
As cluster solution I use kazoo cluster with kamailio - after 6 mouth of usage I can say it perfect solution. Also updates DNS record can be implemented via custom corosync resource agent script. Write this script is task of two or tree days. This solution is not require external servers. On Fri, Feb 12, 2016, 14:50 Stanislav Sinyagin <ssinyagin@gmail.com> wrote:
as Sergey has proposed, there could be a DNS service which monitors the availability of your VoIP servers and changes the DNS entries if a server goes down. The TTL for individual SRV records could be set to few seconds.
But that means again that all users are using the same server, so it's not really a distributed model as Emrah challenged in the original mail.
Probably this new project will help in building a distributed cluster, but it needs a detailed study: https://ipfs.io/
On Fri, Feb 12, 2016 at 10:09 AM, Andrew Cassidy < andrew@cassidywebservices.co.uk> wrote:
It's not instant, but I've used OVH failover IP's to do that sort of thing. Heartbeat over ipsec tunnel, use pacemaker with a custom script that does the OVH API call to move the IP address.
Sadly it's not that quick, takes about 2 minutes.
On 12 February 2016 at 07:40, Stanislav Sinyagin <ssinyagin@gmail.com> wrote:
there is an issue with anycast routing though: when you bring up a new server, some running sessions will be dropped, because their IP packets would be routed to a different host. So, it needs a careful design. Maybe place only the SIP proxy on an anycast address, and run the calls from unique local addresses.
Multiple DNS SRV records with different priorities are also possible, but you can't direct the users to the nearest location within the same domain. Also a bunch of SIP clients needs to be tested and you need to answer the questions, like:
-- what is the timeout if the primary server is unavailable? -- if the primary host goes down during the call, how soon can the client re-dial? -- what happens if the primary server comes up again?
On Thu, Feb 11, 2016 at 8:00 PM, Stanislav Sinyagin <ssinyagin@gmail.com> wrote:
hi Emrah and all,
it's the first time I actually searched for it, but there are hosting offers with anycast IP routing. It means, you have multiple servers in various locations, and they share the same service IP address. The clients connect to the nearest server, which is determined by standard BGP routing. You are still limited to a single global hosting provider, but you benefit from its redundant network and geographical distribution.
In case of anycast addressing, incoming connections will be served easily. But the outgoing connections are rather tricky: you will need to bring the outbound call to the physical server where the user has registered, and initiate the connection from its anycast address. So, you can share and replicate the registration database, but you need to send the outbound call to the server which accepted the registration. I guess you should be able to retrieve this information from the registration database. This needs to be looked in details.
Google for anycast server hosting, and there are at least 3 providers offering virtual hosts, and OVH is offering physical hosts as well. I guess there are more providers with similar offerings.
Without anycast, you would need to use redundant registrars sharing the same service IP address -- for example, Digitalocean offers such service within any single datacenter.
Having multiple registrars with different IP addresses is also possible, but then you depend on the way how each particular SIP client handles multiple IP addresses after resolving the domain name. Some of them may get stuck to a single address, even if it's not responding.
cheers, stanislav
On Thu, Feb 11, 2016 at 5:53 PM, Emrah <lists@kavun.ch> wrote:
Hi list, I’m writing to gather your thoughts and suggestions on how to have a high availability FS setup on different networks.
I am trying to achieve the following: - Load balance FreeSWITCH instances on 2 or more servers, possibly in different countries. - Shared user directory and dialplan, but I’m not sure if shared registrations would make sense. - If a server goes down, the phone should register on the alternative servers. Obviously we can’t keep calls up.
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.
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. 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.
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.
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.
Best, E
Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
-- *Andrew Cassidy BSc (Hons) MBCS SSCA* Managing Director
*T <info@cassidywebservices.co.uk> *03300 100 960 *F <info@cassidywebservices.co.uk> *03300 100 961 *E <info@cassidywebservices.co.uk> *andrew@cassidywebservices.co.uk *W <info@cassidywebservices.co.uk> *www.cassidywebservices.co.uk
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
I love all your ideas, and thanks for sharing. The best option remains to test things out in real scenarios and see what happens. I’m already distributing my media traffic. Now I’d like to make the SIP part redundant. Just got some server resources in different locations. I’ll report back with my findings! E
On Feb 12, 2016, at 10:09 AM, Andrew Cassidy <andrew@cassidywebservices.co.uk> wrote:
It's not instant, but I've used OVH failover IP's to do that sort of thing. Heartbeat over ipsec tunnel, use pacemaker with a custom script that does the OVH API call to move the IP address.
Sadly it's not that quick, takes about 2 minutes.
On 12 February 2016 at 07:40, Stanislav Sinyagin <ssinyagin@gmail.com <mailto:ssinyagin@gmail.com>> wrote: there is an issue with anycast routing though: when you bring up a new server, some running sessions will be dropped, because their IP packets would be routed to a different host. So, it needs a careful design. Maybe place only the SIP proxy on an anycast address, and run the calls from unique local addresses.
Multiple DNS SRV records with different priorities are also possible, but you can't direct the users to the nearest location within the same domain. Also a bunch of SIP clients needs to be tested and you need to answer the questions, like:
-- what is the timeout if the primary server is unavailable? -- if the primary host goes down during the call, how soon can the client re-dial? -- what happens if the primary server comes up again?
On Thu, Feb 11, 2016 at 8:00 PM, Stanislav Sinyagin <ssinyagin@gmail.com <mailto:ssinyagin@gmail.com>> wrote:
hi Emrah and all,
it's the first time I actually searched for it, but there are hosting offers with anycast IP routing. It means, you have multiple servers in various locations, and they share the same service IP address. The clients connect to the nearest server, which is determined by standard BGP routing. You are still limited to a single global hosting provider, but you benefit from its redundant network and geographical distribution.
In case of anycast addressing, incoming connections will be served easily. But the outgoing connections are rather tricky: you will need to bring the outbound call to the physical server where the user has registered, and initiate the connection from its anycast address. So, you can share and replicate the registration database, but you need to send the outbound call to the server which accepted the registration. I guess you should be able to retrieve this information from the registration database. This needs to be looked in details.
Google for anycast server hosting, and there are at least 3 providers offering virtual hosts, and OVH is offering physical hosts as well. I guess there are more providers with similar offerings.
Without anycast, you would need to use redundant registrars sharing the same service IP address -- for example, Digitalocean offers such service within any single datacenter.
Having multiple registrars with different IP addresses is also possible, but then you depend on the way how each particular SIP client handles multiple IP addresses after resolving the domain name. Some of them may get stuck to a single address, even if it's not responding.
cheers, stanislav
On Thu, Feb 11, 2016 at 5:53 PM, Emrah <lists@kavun.ch <mailto:lists@kavun.ch>> wrote:
Hi list, I’m writing to gather your thoughts and suggestions on how to have a high availability FS setup on different networks.
I am trying to achieve the following: - Load balance FreeSWITCH instances on 2 or more servers, possibly in different countries. - Shared user directory and dialplan, but I’m not sure if shared registrations would make sense. - If a server goes down, the phone should register on the alternative servers. Obviously we can’t keep calls up.
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.
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. 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.
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.
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.
Best, E _________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org <mailto:consulting@freeswitch.org> http://www.freeswitchsolutions.com <http://www.freeswitchsolutions.com/>
Official FreeSWITCH Sites http://www.freeswitch.org <http://www.freeswitch.org/> http://confluence.freeswitch.org <http://confluence.freeswitch.org/> http://www.cluecon.com <http://www.cluecon.com/>
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org <mailto:FreeSWITCH-users@lists.freeswitch.org> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users <http://lists.freeswitch.org/mailman/listinfo/freeswitch-users> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users <http://lists.freeswitch.org/mailman/options/freeswitch-users> http://www.freeswitch.org <http://www.freeswitch.org/>
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org <mailto:consulting@freeswitch.org> http://www.freeswitchsolutions.com <http://www.freeswitchsolutions.com/>
Official FreeSWITCH Sites http://www.freeswitch.org <http://www.freeswitch.org/> http://confluence.freeswitch.org <http://confluence.freeswitch.org/> http://www.cluecon.com <http://www.cluecon.com/>
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org <mailto:FreeSWITCH-users@lists.freeswitch.org> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users <http://lists.freeswitch.org/mailman/listinfo/freeswitch-users> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users <http://lists.freeswitch.org/mailman/options/freeswitch-users> http://www.freeswitch.org <http://www.freeswitch.org/>
-- Andrew Cassidy BSc (Hons) MBCS SSCA Managing Director
T <mailto:info@cassidywebservices.co.uk> 03300 100 960 F <mailto:info@cassidywebservices.co.uk> 03300 100 961 E <mailto:info@cassidywebservices.co.uk> andrew@cassidywebservices.co.uk <mailto:andrew@cassidywebservices.co.uk> W <mailto:info@cassidywebservices.co.uk> www.cassidywebservices.co.uk <http://www.cassidywebservices.co.uk/>_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
For outbound calls, you should be fine as long as your frontend SIP proxies can reach any backend (media/app/whatever) server. This is exactly what Via is for, right? From: freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Emrah Sent: Sunday, 14 February, 2016 10:18 To: FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org> Subject: Re: [Freeswitch-users] High availability on different networks I love all your ideas, and thanks for sharing. The best option remains to test things out in real scenarios and see what happens. I’m already distributing my media traffic. Now I’d like to make the SIP part redundant. Just got some server resources in different locations. I’ll report back with my findings! E On Feb 12, 2016, at 10:09 AM, Andrew Cassidy <andrew@cassidywebservices.co.uk<mailto:andrew@cassidywebservices.co.uk>> wrote: It's not instant, but I've used OVH failover IP's to do that sort of thing. Heartbeat over ipsec tunnel, use pacemaker with a custom script that does the OVH API call to move the IP address. Sadly it's not that quick, takes about 2 minutes. On 12 February 2016 at 07:40, Stanislav Sinyagin <ssinyagin@gmail.com<mailto:ssinyagin@gmail.com>> wrote: there is an issue with anycast routing though: when you bring up a new server, some running sessions will be dropped, because their IP packets would be routed to a different host. So, it needs a careful design. Maybe place only the SIP proxy on an anycast address, and run the calls from unique local addresses. Multiple DNS SRV records with different priorities are also possible, but you can't direct the users to the nearest location within the same domain. Also a bunch of SIP clients needs to be tested and you need to answer the questions, like: -- what is the timeout if the primary server is unavailable? -- if the primary host goes down during the call, how soon can the client re-dial? -- what happens if the primary server comes up again? On Thu, Feb 11, 2016 at 8:00 PM, Stanislav Sinyagin <ssinyagin@gmail.com<mailto:ssinyagin@gmail.com>> wrote:
hi Emrah and all,
it's the first time I actually searched for it, but there are hosting offers with anycast IP routing. It means, you have multiple servers in various locations, and they share the same service IP address. The clients connect to the nearest server, which is determined by standard BGP routing. You are still limited to a single global hosting provider, but you benefit from its redundant network and geographical distribution.
In case of anycast addressing, incoming connections will be served easily. But the outgoing connections are rather tricky: you will need to bring the outbound call to the physical server where the user has registered, and initiate the connection from its anycast address. So, you can share and replicate the registration database, but you need to send the outbound call to the server which accepted the registration. I guess you should be able to retrieve this information from the registration database. This needs to be looked in details.
Google for anycast server hosting, and there are at least 3 providers offering virtual hosts, and OVH is offering physical hosts as well. I guess there are more providers with similar offerings.
Without anycast, you would need to use redundant registrars sharing the same service IP address -- for example, Digitalocean offers such service within any single datacenter.
Having multiple registrars with different IP addresses is also possible, but then you depend on the way how each particular SIP client handles multiple IP addresses after resolving the domain name. Some of them may get stuck to a single address, even if it's not responding.
cheers, stanislav
On Thu, Feb 11, 2016 at 5:53 PM, Emrah <lists@kavun.ch<mailto:lists@kavun.ch>> wrote:
Hi list, I’m writing to gather your thoughts and suggestions on how to have a high availability FS setup on different networks.
I am trying to achieve the following: - Load balance FreeSWITCH instances on 2 or more servers, possibly in different countries. - Shared user directory and dialplan, but I’m not sure if shared registrations would make sense. - If a server goes down, the phone should register on the alternative servers. Obviously we can’t keep calls up.
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.
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. 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.
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.
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.
Best, E _________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org<mailto:consulting@freeswitch.org> http://www.freeswitchsolutions.com<http://www.freeswitchsolutions.com/>
Official FreeSWITCH Sites http://www.freeswitch.org<http://www.freeswitch.org/> http://confluence.freeswitch.org<http://confluence.freeswitch.org/> http://www.cluecon.com<http://www.cluecon.com/>
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org<mailto: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<http://www.freeswitch.org/>
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org<mailto:consulting@freeswitch.org> http://www.freeswitchsolutions.com<http://www.freeswitchsolutions.com/> Official FreeSWITCH Sites http://www.freeswitch.org<http://www.freeswitch.org/> http://confluence.freeswitch.org<http://confluence.freeswitch.org/> http://www.cluecon.com<http://www.cluecon.com/> FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org<mailto: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<http://www.freeswitch.org/> -- Andrew Cassidy BSc (Hons) MBCS SSCA Managing Director [http://www.cassidywebservices.co.uk/static/emailsig.png] T<mailto:info@cassidywebservices.co.uk> 03300 100 960 F<mailto:info@cassidywebservices.co.uk> 03300 100 961 E<mailto:info@cassidywebservices.co.uk> andrew@cassidywebservices.co.uk<mailto:andrew@cassidywebservices.co.uk> W<mailto:info@cassidywebservices.co.uk> www.cassidywebservices.co.uk<http://www.cassidywebservices.co.uk/> _________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org<mailto:consulting@freeswitch.org> http://www.freeswitchsolutions.com Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org<mailto: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
participants (8)
-
Andrew Cassidy
-
Emrah
-
Luis Daniel Lucio Quiroz
-
Michael Giagnocavo
-
Moishe Grunstein
-
Sergey Safarov
-
Stanislav Sinyagin
-
Vik Killa