<div class="gmail_quote"><div>Thanks Zeeshan,</div><div><br></div><div>In fact,i have RealTime configured and working...</div><div><br></div><div>What i want is to make an upgrade of libpri and wanpipe at least, asterisk and zaptel will be like i have now...</div>
<div><br></div><div>Do you think that recompile/upgrade this softwares version will produce a problem? what steps should i do?</div><div><br></div><div>Is it necessary to recompile asterisk if i make an upgrade of libpri? this recompilation will affect the realtime or the well bahavior of the server?</div>
<div><br></div><div>Working with an old version of asterisk like 1.4.21.2 with the newest version of libpri is recommended or not?</div><div><br></div><div>Thanks in advance for all your advices!</div><div><br></div><div>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Message: 11<br>
Date: Mon, 22 Mar 2010 23:15:00 -0400<br>
From: Zeeshan Zakaria <<a href="mailto:zishanov@gmail.com">zishanov@gmail.com</a>><br>
Subject: Re: [asterisk-users] How to make upgrades with Asterisk<br>
To: Asterisk Users Mailing List - Non-Commercial Discussion<br>
<<a href="mailto:asterisk-users@lists.digium.com">asterisk-users@lists.digium.com</a>><br>
Message-ID:<br>
<<a href="mailto:5ad99e891003222015o1727265cr4860d4e8a0b96c5a@mail.gmail.com">5ad99e891003222015o1727265cr4860d4e8a0b96c5a@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
If it is a production server, you should not do the upgrade on it. Setup a<br>
new server with upgraded software, migrate all the data, test it and make<br>
sure it works fine. There are things like CDR and voicemail which are<br>
constantly being updated, meaning just before the final migration, you<br>
should copy them to the new server.<br>
<br>
I have done some migrations and have found clonezilla to be a wonderful tool<br>
for this purpose. You create a second server on any computer, and once it is<br>
ready, clone it on a USB stick or CD, or on another computer via SSH, then<br>
clone the production server for backup purposes on a medium of your choice,<br>
and finally restore this new server image on to the production server. If<br>
something goes wrong, you'll be able to restore the server back to its<br>
functional state from the backup cloned image.<br>
<br>
When I migrated my own production server from 1.2 to 1.4, I did the<br>
rehearsal many times, and very carefully drafted the whole migation plan.<br>
This also included asking all the users to copy and delete their voicemails<br>
before the day of migration. It took me about two weeks in planning and<br>
making sure every single setting will be migrated, before I was comfotable<br>
to do the migration, which took hardly an hour, and went just perfectly<br>
smooth.<br>
<br>
Personally I am of the opinion that if it is not really necessary, don't<br>
upgrade it. Will 1.6 give you something which you don't have in 1.4? It'll<br>
have its own issues and learning curve. I tried it once and it was only a<br>
pain for my setup, specially with real-time architecture, and a few other<br>
things which I can't remember now.<br>
<br>
--<br>
Zeeshan A Zakaria<br>
<br><br>
</blockquote></div><br>