<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman, new york, times, serif;font-size:12pt"><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;">>----- Original Message ----<br><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;">>From: Scott Moseman <scmoseman@gmail.com><br>>To: Asterisk Users Mailing List - Non-Commercial Discussion <asterisk-users@lists.digium.com><br>>Sent: Wednesday, September 26, 2007 6:07:06 AM<br>>Subject: Re: [asterisk-users] Asterisk Redundancy<br>><br><div>>On 9/26/07, SIP <sip@arcdiv.com> wrote:<br>>><br>>> No. It's not. But there still exists the possibility even in a<br>>> relatively stable situation that the software could crash or that<br>>> hardware could fail. It's best, when planning a highly-available<br>>>
solution, to plan for the unforeseen and not assume you can<br>>> avoid all mishaps. Let's assume, for the sake of argument, that<br>>> the software will NEVER fail. Hardware still might, and that would<br>>> still mean a lost call unless there's a way to switch running calls<br>>> over to a new server seamlessly.<br>>><br>><br>>Also be sure that you have a very redundant network configuration.<br>>Too often I see people spend a great deal of time and money to get<br>>redundant servers when their switches, firewalls, routers, etc are not<br>>even capable of handling a failed network element.<br><br>You can achieve this at the application level.<br><br></div></div></div></div><br>
<hr size=1>Take the Internet to Go: Yahoo!Go puts the <a href="http://us.rd.yahoo.com/evt=48253/*http://mobile.yahoo.com/go?refer=1GNXIC">Internet in your pocket:</a> mail, news, photos & more. </body></html>