<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"\@MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Exactly. You probably want to have something like this anyways,
so that when someone accidentally unplugs the system, or the disks/CPU/RAM
crash, you’re not stuck.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>That is, until FreeSWITCH can record its internal state to some
inter-machine memory so we can have hot failover. ;)<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>-Michael<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
freeswitch-users-bounces@lists.freeswitch.org
[mailto:freeswitch-users-bounces@lists.freeswitch.org] <b>On Behalf Of </b>Anthony
Minessale<br>
<b>Sent:</b> Thursday, June 11, 2009 10:55 AM<br>
<b>To:</b> freeswitch-users@lists.freeswitch.org<br>
<b>Subject:</b> Re: [Freeswitch-users] Live Upgrade Techniques<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'>or you can put a sip proxy in
front of 2 boxes where you can control the flow of traffic.<br>
when you want to upgrade one, take all the traffic off of it by forcing all
calls to the other box, upgrade it then shift the traffic to the new one.<br>
if that goes well, upgrade the other one too.<br>
<br>
<br>
<o:p></o:p></p>
<div>
<p class=MsoNormal>On Thu, Jun 11, 2009 at 5:47 AM, Michal Bielicki
<michal.bielicki@halo2.pl> wrote:<o:p></o:p></p>
<p class=MsoNormal><br>
Am 11.06.2009 um 05:04 schrieb John Dalgliesh:<o:p></o:p></p>
<div>
<blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;
margin-left:4.8pt;margin-right:0in'>
<p class=MsoNormal style='margin-bottom:12.0pt'><o:p> </o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><br>
Hi,<br>
<br>
I am slowly gaining confidence using FreeSWITCH in production, but there<br>
is one issue that I'm still wondering about: how are people upgrading<br>
their FreeSWITCH installation binaries without dropping all current calls?<br>
<br>
So far I have been upgrading in the dead of night, after pausing for 5<br>
minutes then dropping the stragglers, but this is hardly ideal.<br>
<br>
What I would like to do is to run an upgraded instance of FreeSWITCH on<br>
the same machine, and have it handle all new call packets, whereas the old<br>
instance continues to handle the existing call packets, until there are no<br>
more old calls left.<br>
<br>
I can think of about seven ways to accomplish this, but before I dive into<br>
the code I thought I'd better ask what everyone else has been doing :)<br>
<br>
(The only standard way I can think of doing this is to have a SIP proxy<br>
sitting in front of FS the whole time, just to handle these upgrade<br>
windows. It seems like a bit of a waste.)<br>
<br>
So how are you handling your FS software upgrades?<br>
<br>
{P^/<br>
John<br>
<br>
<o:p></o:p></p>
</blockquote>
<p class=MsoNormal style='margin-bottom:12.0pt'><o:p> </o:p></p>
</div>
<p class=MsoNormal style='margin-bottom:12.0pt'>We use freeswitch on solaris
and just upgrade it to a new zfs which gets remounted to the old place and
freeswitch gracefully restartet. On failure we can allways do a rollback, which
takes between 2 and 10 seconds, so the dwntime is pretty acceptable.<br>
<br>
Michal Bielicki<br>
Leiter der Niederlassung<br>
HaloKwadrat Sp. z o.o.<br>
Niederlassung Kleinmachnow<br>
Eingetragen im Handelsregister beim Amtsgericht Potsdam, HRB21422P<br>
Ust.Id.: DE261885536<br>
Geschaeftsfuehrer: Aleksander Wiercinski<br>
Meiereifeld 2b, 14532 Kleinmachnow<br>
t. +49 33203 263220<br>
f. +49 33203 263229 sip. <a href="mailto:info@halokwadrat.de" target="_blank">info@halokwadrat.de</a><br>
e. <a href="mailto:michal.bielicki@halokwadrat.de" target="_blank">michal.bielicki@halokwadrat.de</a>
| w. <a href="http://www.halokwadrat.de" target="_blank">www.halokwadrat.de</a><br>
Hauptgeschäftsstelle:<br>
Halo Kwadrat Sp. z o.o.<br>
ul. Polna 46/14<br>
00-644 Warszawa, Polen<br>
EIngetragen im HRB Warszawa, KRS 0000153539<br>
<br>
<br>
_______________________________________________<br>
Freeswitch-users mailing list<br>
<a href="mailto:Freeswitch-users@lists.freeswitch.org">Freeswitch-users@lists.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users"
target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
UNSUBSCRIBE:<a
href="http://lists.freeswitch.org/mailman/options/freeswitch-users"
target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><o:p></o:p></p>
</div>
<p class=MsoNormal><br>
<br clear=all>
<br>
-- <br>
Anthony Minessale II<br>
<br>
FreeSWITCH <a href="http://www.freeswitch.org/">http://www.freeswitch.org/</a><br>
ClueCon <a href="http://www.cluecon.com/">http://www.cluecon.com/</a><br>
<br>
AIM: anthm<br>
<a href="mailto:MSN%3Aanthony_minessale@hotmail.com">MSN:anthony_minessale@hotmail.com</a><br>
GTALK/JABBER/<a href="mailto:PAYPAL%3Aanthony.minessale@gmail.com">PAYPAL:anthony.minessale@gmail.com</a><br>
IRC: <a href="http://irc.freenode.net">irc.freenode.net</a> #freeswitch<br>
<br>
FreeSWITCH Developer Conference<br>
<a href="mailto:sip%3A888@conference.freeswitch.org">sip:888@conference.freeswitch.org</a><br>
<a href="http://iax:guest@conference.freeswitch.org/888">iax:guest@conference.freeswitch.org/888</a><br>
<a href="mailto:googletalk%3Aconf%2B888@conference.freeswitch.org">googletalk:conf+888@conference.freeswitch.org</a><br>
pstn:213-799-1400<o:p></o:p></p>
</div>
</body>
</html>