On Thu, Jun 30, 2016 at 03:56:00PM +, Colin Morelli wrote:
> However, I think the best solution would be something like what Daniel
> mentioned - to have multiple (maybe 2-4 but the number really depends on
> your availability and scalability requirements) Kamailio instances at the
> edge, each
On Thu, Jun 30, 2016 at 03:18:11PM +, Colin Morelli wrote:
> Maybe I'm missing something about the core infrastructure of Kamailio that
> makes this impossible, but why does it seem like nobody wants to run
> multiple Kamailio load balancers in a cluster? sip.yourcompany.com can have
> A/SRV re
Daryn,
That response was more general, not necessarily directed at you!
DNS-based load balancing has always been problematic for clients. They tend
to not properly balance across SRV records, or failover to secondary A
records.
However, I think the best solution would be something like what Dani
Collin,
My apologies for the lack of clarity. We are desiring to use multiple sets
of each task (Load Balancer) (Proxy Registrar) (App Servers). My main
reason for the post and inquiry is to determine if separating the roles to
multiple machine(s) is a common architecture, and if there are any
s
On Thu, Jun 30, 2016 at 05:15:19PM +0200, Giacomo Vacca wrote:
> Remember though that the Load Balancer will be
> your Single Point Of Failure. If the Load Balancer dies, for any reason,
> the service is not available.
...
> Depending on the capabilities of the clients you may consider removing the
Thank you Giacomo for the info!
We are thinking to use DNS SRV for failover and to use multiple LBs and do
some sort of HA on the Load Balancer(s) using keepalived or etcd, etc
One of my marching orders is to eliminate any single point of failures.
Using one set of hosts would definitely simp
Maybe I'm missing something about the core infrastructure of Kamailio that
makes this impossible, but why does it seem like nobody wants to run
multiple Kamailio load balancers in a cluster? sip.yourcompany.com can have
A/SRV records pointing to multiple IP addresses of separate Kamailio
instances.
Hi Daryn,
it may not be an overkill, depending on the constrains you have. For
example if the clients can possibly only be instructed to connect to a
single public IP address (5.5.5.5 in your example), while you want to be
able to scale the Kamailio architecture with multiple instances, then it
can
I am interested in opinions and suggestions about load balancing with
Kamailio. I work for an ITSP that currently uses Oracle & Broadsoft, and I
am working to design and develop an open source solution using Kamailio
(Proxy, Registrar, LB) & other Application/Media servers for more
flexibility an
