<br><br><div class="gmail_quote">On Thu, Oct 23, 2008 at 12:16 PM, Alex Balashov <span dir="ltr"><<a href="mailto:abalashov@evaristesys.com">abalashov@evaristesys.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Any "frontal application-level switch" would simply have the same liability.<br>
</blockquote><div><br>right. <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
Kamailio is a very high-throughput proxy that can handle huge amounts of call setups per second. I think you can count on that.</blockquote><div><br>Yes but you may need to use the power of all your load-balancer nodes. I believe we can expect 10K transactions/seconds on a single load-balancer node, but if you need to handle more traffic, load balancer node may be a bottleneck. <br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<br>
Failing over around the load balancer node to a secondary load balancer or distributing the traffic among multiple load balancers is a job best left to the sending endpoint. For example, a DID origination provider's switch or SBC can be set up to fail over calls to a different IP endpoint for your SIP trunk if no response is received within a certain amount of time. That is how this is typically done. At some point you've got to say that you've done all you can do, and it's up to the other side.<br>
</blockquote><div><br>Thanks Alex, it's a good point.<br><br>-pascal<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
Pascal Maugeri wrote:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div></div><div class="Wj3C7c">
Hi<br>
<br>
I was wondering how to achieve an architecture with two or more active load-balancer nodes (kamailio+dispatcher module).<br>
<br>
I have read how to setup two dispatcher nodes, one node as a master and the other one as a backup.<br>
<br>
The backup node doesn't process any traffic until master fails. But how to make the traffic being processed by both load-balancers ? In the case for instance the capacity of single node is not enough to process all incoming traffic. Is there any recommended configuration (eg. using frontal application-level swith)<br>
<br>
Regards,<br>
Pascal<br>
<br>
<br></div></div>
------------------------------------------------------------------------<br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.kamailio.org" target="_blank">Users@lists.kamailio.org</a><br>
<a href="http://lists.kamailio.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.kamailio.org/cgi-bin/mailman/listinfo/users</a><br>
</blockquote>
<br>
<br>
-- <br>
Alex Balashov<br>
Evariste Systems<br>
Web : <a href="http://www.evaristesys.com/" target="_blank">http://www.evaristesys.com/</a><br>
Tel : (+1) (678) 954-0670<br>
Direct : (+1) (678) 954-0671<br>
Mobile : (+1) (706) 338-8599<br>
</blockquote></div><br>