I know this is some what a loaded question with many variables attached, but is 1.4 branches. as stable as 1.2. now?

Leif Madsen wrote:
On Nov 13, 2007 2:16 PM, Reza - Asterisk Enthusiast
<[EMAIL PROTECTED]> wrote:
Fellow Asterisk Users:

BE WARNED!   Prepare for a couple of days to few days of endless sleepless
nights and days if you are upgrading from 1.2 to 1.4.   A lot of things are
deprecated and certain syntax have changed.    You WILL be affected if you
are providing any form of Hosted PBX services for your clients.  You WILL be
affected if you have a lot of clients.  You WILL be affected!

We've gone through almost 72 hrs of non-stop analysis, tinkering, and
testing.   Be warned...  that IF you are running a production system, make
sure you thoroughly TEST your new settings on the 1.4 box ....   and by NO
means attempt to upgrade from 1.2 to 1.4 on your production box.  YOU WILL
GET SCREWED.

We have not yet converted our production box to 1.4,   but our current trial
(over the last couple of days) on a bunch of test beds has taught us some
valuable lessons.    Some people will say that there are only minor
changes... and assuming this is true...  even those minor changes affects
you drastically specially when you have thousands of lines of in-house
written codes for your service offerings.

Anyone care to share your experience?

I can basically attest to this. Upgrading from 1.2 to 1.4 is not a
trivial task. Be sure to read the UPGRADE.txt file, and you will need
to do some development on a test system to make sure everything still
works. As Reza stated, if you simply install 1.4 over your 1.2 system,
it's not going to "just work". The major revision number is
difference, thus that means core changes to how Asterisk works.

I've been using 1.4 for over a year now, and I love it! But I can't
state enough that upgrading from 1.2 to 1.4 is not a trivial task.



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to