<div>Hi,</div><div>Thanks for taking out time for this. really appreciate your ideas. Here are few things I've found useful so far.</div><div><br></div><a href="http://kamailio.org/events/2011-fosdem/p_usrloc.pdf">http://kamailio.org/events/2011-fosdem/p_usrloc.pdf</a> <div>
This looks like one thing that one could have to ensure more reliability but we do need other application level and physical level failover techniques additionally.</div><div><br></div><div><div>For using any technique like Linux-HA, Heartbeat, keepalived, UCARP or any floating/virtual IP techniques I really hope that the sysctl option mentioned in b/m thread really works.</div>
<div><a href="http://www.mail-archive.com/sr-users@lists.sip-router.org/msg03714.html">http://www.mail-archive.com/sr-users@lists.sip-router.org/msg03714.html</a></div><div><br></div></div><div><a href="http://old.nabble.com/Kamilio-Failover-Options-td21947502.html">http://old.nabble.com/Kamilio-Failover-Options-td21947502.html</a> </div>
<div>DNS SRV is one option. Using another Kamailio on top of two Kamailio is again a SPOF so I think its of no use at all.</div><div><br></div><div>I hope to get a very reliable and working solution out of these forums.</div>
<div><br></div><div>Regards,</div><div>Sammy</div><div><br><div class="gmail_quote">On Wed, Jan 25, 2012 at 9:49 PM, Andreas Granig <span dir="ltr"><<a href="mailto:agranig@sipwise.com">agranig@sipwise.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Sammy,<br>
<div class="im"><br>
On 01/25/2012 02:08 PM, Sammy Govind wrote:<br>
> I've been looking for ways to create a redundant Kamailio cluster. I've<br>
> googled alot but haven't got any concrete or final wording on any one<br>
> solution that'll just work perfectly. The basic requirement is that in<br>
<br>
</div>HA is never really easy :)<br>
<div class="im"><br>
> case of Kamailio application failure or in case of physical machine<br>
> error the whole setup just starts working on secondary server.<br>
><br>
> Please suggest anything whichever you guys are using. Any reference URLs<br>
> would be very much appreciated.<br>
<br>
</div>For 1+1 setups, you can use a master/master replication (people also use<br>
drbd to sync the whole table space, not sure how good that works) on db<br>
level, use write-back mode in kamailio to make sure your registrations<br>
are written to DB immediately, then use heartbeat to do the IP/process<br>
fail-overs on network/power failures. On top, you can do manual checks<br>
to trigger a fail-over in case of high-level failures. I guess this is<br>
the typical and most straight-forward scenario. Your mileage might vary,<br>
depending on specific environment variables (e.g. you might want to<br>
announce your active server via RIP/OSPF using quagga instead of the<br>
more common gratuitous arp if your servers are geographically split).<br>
<br>
For scaling larger, put a kamailio instance acting as load-balancer in<br>
front of your proxies and scale them by providing some sharding<br>
information to the lb.<br>
<br>
Also the new db_cassandra backend in master branch looks pretty<br>
promising when it comes to HA/scaling. Maybe someone can provide some<br>
best practices regarding that as well?<br>
<span class="HOEnZb"><font color="#888888"><br>
Andreas<br>
<br>
</font></span><br>_______________________________________________<br>
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list<br>
<a href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a><br>
<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a><br>
<br></blockquote></div><br></div>