<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.28.1">
</HEAD>
<BODY TEXT="#000000" BGCOLOR="#ffffff">
This is actually pretty slick, but in the context of my particular need it seems like it would be akin to prescribing orbital death lasers when what I really need is a hammer. I am looking more into using OpenSIPS with route headers for now since that might seem to have the fewest moving parts. <BR>
<BR>
I think for the ultra-paranoid asterisk deployments this might be an option, though you do ultimately run into the same problem of handling media in a VM which can get sticky, and of course of replicating whatever it was that caused the crash etc (insert paranoid scenarios here). <BR>
<BR>
On Wed, 2009-11-11 at 17:18 -0600, Lee Riemer wrote:<BR>
<BLOCKQUOTE TYPE=CITE>
This just appeared on slashdot:<BR>
<BR>
<A HREF="http://tech.slashdot.org/story/09/11/11/2246226/Remus-Project-Brings-Transparent-High-Availability-To-Xen?art_pos=1">http://tech.slashdot.org/story/09/11/11/2246226/Remus-Project-Brings-Transparent-High-Availability-To-Xen?art_pos=1</A><BR>
<BR>
anorexicpoodle wrote: <BR>
<BLOCKQUOTE TYPE=CITE>
I have come across the need for a stateful SIP load balancer with fail-over and HA capabilities, and I am hoping some on this list can chime in with some personal experience. <BR>
<BR>
The need is not for a particularly large volume of traffic, more to act as a socket to adapt my active/active model UM system to Metaswitch's 1:1 UM system model, which cannot support active/active application servers. Yes I felt this was a strange omission in functionality as well. <BR>
<BR>
I have pretty much ruled out OpenSER/OpenSIPS/Kamilio because it isn't stateful in HA failover. Passing it through an Acme is ridiculously costly for the need i have, and most hardware based load balancers I am finding just aren't sip-aware, so I don't see them doing much better than OpenSER in a fail-over scenario, it would just be a different kind of ugliness. <BR>
<BR>
Thanks in advance<BR>
<BR>
<PRE>
<HR SIZE="4">
_______________________________________________
VoiceOps mailing list
<A HREF="mailto:VoiceOps@voiceops.org">VoiceOps@voiceops.org</A>
<A HREF="https://puck.nether.net/mailman/listinfo/voiceops">https://puck.nether.net/mailman/listinfo/voiceops</A>
</PRE>
</BLOCKQUOTE>
</BLOCKQUOTE>
<BR>
</BODY>
</HTML>