On Tue, 2007-09-25 at 15:59 +0200, Per Jessen wrote: > I haven't looked into it in any detail, but how about the standard Linux > HA solution with a heartbeat monitor, a shared file-system and IP > take-over?
It's been my experience that this usually works fairly well for stateless protocols like HTTP, but doesn't do so well on stateful protocols like SIP and IAX, and in general is a much more difficult problem to solve. Most people tend to use some combination of SIP proxies (such as SER and OpenSER), DUNDi, shared storage, redundant databases with replication, T1/E1 failover boxes, and horizontal scaling to make Asterisk more highly-available. Of course, I haven't really gone into much detail here, but hopefully it helps answer your question. (It's also my personal experience that people who know how to build such solutions are making enough money off of selling their solution that they aren't real eager to give away all their secrets.) In reality though, you say the word "cluster" and it means five different things to five different people. To really be able to answer the original poster's question, we'd really have to know a lot more about his architecture and his potential points of failure. -- Jared Smith Community Relations Manager Digium, Inc. _______________________________________________ Sign up now for AstriCon 2007! September 25-28th. http://www.astricon.net/ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
