asterisk users - Nov 2010 - Migration from 1.2 to 1.8 in production

Hello Everyone,

We are running asterisk 1.2.x version in production environment since last 5
year and we have no issue at all, But now time to upgrade. and i heard about 1.8
which has introduce many features. I am wondering should I use asterisk 1.8 in
production ? or should I go with 1.4 or 1.6 stable version?

I would like if you suggest me which version would be good for production since
asterisk 1.8 still in beta process.

Thanks,
S. Patel  


 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20101103/18cfc0eb/attachment.htm

_____  

From: asterisk-users-bounces at lists.digium.com
[mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of satish patel
Sent: Wednesday, November 03, 2010 9:14 AM
To: asterisk-users at lists.digium.com
Subject: [asterisk-users] Migration from 1.2 to 1.8 in production

 

Hello Everyone,

We are running asterisk 1.2.x version in production environment since last 5
year and we have no issue at all, But now time to upgrade. and i heard about
1.8 which has introduce many features. I am wondering should I use asterisk
1.8 in production ? or should I go with 1.4 or 1.6 stable version? 

I would like if you suggest me which version would be good for production
since asterisk 1.8 still in beta process. 

Thanks,
S. Patel  



1.8 will introduce many features and is the "supported standard",
which will
be important to you since you are on a "5 year upgrade" plan.  It also
has
more "opportunities" than the 1.4 version since it is under active
development and 1.4 is in a "patch only" state.  If immediate
stability is
your goal, you may want to stick with 1.4.  If I were going to bite the
bullet on 1.6, I'd jump straight to 1.8 since there is no
"end-of-life"
advantage.

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20101103/7a9d2870/attachment.htm

Am 03.11.10 15:14, schrieb satish patel:
> 
> Hello Everyone,
> 
> We are running asterisk 1.2.x version in production environment since last
5 year and we have no issue at all, But now time to upgrade. and i heard about
1.8 which has introduce many features. I am wondering should I use asterisk 1.8
in production ? or should I go with 1.4 or 1.6 stable version?
> 
> I would like if you suggest me which version would be good for production
since asterisk 1.8 still in beta process.
> 
> Thanks,
> S. Patel  
> 
Hello Patel,

it hardly depends on how many users and concurrent calls you have in
your system cause i have recognized 1.2 can handle much more peers than
1.6 or 1.8.

maybe you should try to setup a test server and first try it with your
setup and some load tests if everything is working as you expect.

best regards

stefan

I have used 1.4 & 1.6. I am testing 1.8 for production and it is looking 
very good. I am making some changes to accommodate some minor dialplan 
changes from 1.6. Our 1.4 is very solid 1.6 has some issues with DTMF 
issues when used with Sonus on the back end. 1.8 is looking very good and 
we hope to go production before the end of the year. 

If you have to change righ now are you using custom dialplan code? If you 
are I would roll the dice and go for 1.8 this will give you the longest 
life span. If not there is no real big hit for stepping from 1.4 to 1.8. 
The other issue is if you want really detailed logging for call records the 
CEL method in 1.8 is the way to go. You will need to be able to boil the 
data down but it is there. I have seen a few kinks in the current version 
but it looks like they will be worked out with some incremental updates.

Our hope is to be fully 1.8 on all of our backbone production units by the 
end of Jan 2011 with our first unit by December 2010.
I would shy away of 1.6.x based on our experience. Our 1.6.x boxes will 
move before our 1.4.x boxes.

Thanks
Bryant

----------------------------------------
 From: "Tilghman Lesher" <tlesher at digium.com>
Sent: Wednesday, November 03, 2010 11:26 AM
To: "Asterisk Users Mailing List - Non-Commercial Discussion" 
<asterisk-users at lists.digium.com>
Subject: Re: [asterisk-users] Migration from 1.2 to 1.8 in production

On Wednesday 03 November 2010 09:32:10 Danny Nicholas
wrote:
> satish patel wrote:
> > We are running asterisk 1.2.x version in production environment since
> > last 5 year and we have no issue at all, But now time to upgrade. and 
i
> > heard about 1.8 which has introduce many features. I am wondering
> > should I use asterisk 1.8 in production ? or should I go with 1.4 or
> > 1.6 stable version?
> > 
> > I would like if you suggest me which version would be good for
> > production since asterisk 1.8 still in beta process.
> 
> 1.8 will introduce many features and is the "supported standard",
which
> will be important to you since you are on a "5 year upgrade"
plan. It
> also has more "opportunities" than the 1.4 version since it is
under
> active development and 1.4 is in a "patch only" state. 
This is not the case. Both 1.8 and 1.4 are in the same state right now.
The only difference in support level is that 1.4's EOL is much sooner than
the EOL for 1.8. 1.6.2 will EOL at approximately the same time as 1.4.
See https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions for the
most up-to-date schedule.
> If immediate
> stability is your goal, you may want to stick with 1.4. If I were
> going to bite the bullet on 1.6, I'd jump straight to 1.8 since there
> is no "end-of-life" advantage.
-- 
Tilghman Lesher
Digium, Inc. | Senior Software Developer
twitter: Corydon76 | IRC: Corydon76-dig (Freenode)
Check us out at: www.digium.com & www.asterisk.org

-- 
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users


-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20101103/89da8536/attachment.htm

If 1.2 is working fine without any problem then why do you need to upgrade
to any newer version? I would suggest don't do it. If you really want to do
it just for the sake of doing it, upgrade to 1.4 only, which is the most
stable and well tested version of asterisk. Upgrading always causes hickups
in the new system, and effects quality of service to the customers. As they
say, if its not broken, don't fix it.

Zeeshan A Zakaria

--
www.ilovetovoip.com
www.pbxforall.com

On 2010-11-03 11:30 AM, "Tilghman Lesher" <tlesher at
digium.com> wrote:

On Wednesday 03 November 2010 09:32:10 Danny Nicholas wrote:
> satish patel wrote:
> > We are running asterisk 1.2.x version in production environment since
> > ...
> 1.8 will introduce many features and is the "supported standard",
which
> will be important to you...
This is not the case.  Both 1.8 and 1.4 are in the same state right now.
The only difference in support level is that 1.4's EOL is much sooner than
the EOL for 1.8.  1.6.2 will EOL at approximately the same time as 1.4.
See https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions for the
most up-to-date schedule.

> If immediate
> stability is your goal, you may want to stick with 1.4. If I were
> going to bite...
--
Tilghman Lesher
Digium, Inc. | Senior Software Developer
twitter: Corydon76 | IRC: Corydon76-dig (Freenode)
Check us out at: www.digium.com & www.asterisk.org


-- 
_____________________________________________________________________
-- Bandwidth and Colocati...
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20101103/9e5127d2/attachment.htm

El 03/11/10 10:44, Bryant Zimmerman escribi?:
> I have used 1.4 & 1.6. I am testing 1.8 for production and it is 
> looking very good. I am making some changes to accommodate some minor 
> dialplan changes from 1.6. Our 1.4 is very solid 1.6 has some issues 
> with DTMF issues when used with Sonus on the back end. 1.8 is looking 
> very good and we hope to go production before the end of the year.
>
> If you have to change righ now are you using custom dialplan code? If 
> you are I would roll the dice and go for 1.8 this will give you the 
> longest life span. If not there is no real big hit for stepping from 
> 1.4 to 1.8. The other issue is if you want really detailed logging for 
> call records the CEL method in 1.8 is the way to go. You will need to 
> be able to boil the data down but it is there. I have seen a few kinks 
> in the current version but it looks like they will be worked out with 
> some incremental updates.
>
> Our hope is to be fully 1.8 on all of our backbone production units by 
> the end of Jan 2011 with our first unit by December 2010.
> I would shy away of 1.6.x based on our experience. Our 1.6.x boxes 
> will move before our 1.4.x boxes.
>
>
> Thanks
> Bryant
Hi Bryant,

Thanks for sharing your experience, it encourages us to try and test 1.8 
throughly before we upgrade our 1.4 boxes, jumping the 1.6 step in the 
upgrade path. We are also concerned about the short support time that is 
left for 1.4 and 1.6, so 1.8 would be the best in support terms. This 
goes in concordance for what I think the asterisk team wants, that is, 
to focus on only one well supported version instead of having to support 
several parallel branches which mean more work and "cross-fixing" 
between them.

Cheers,

-- 
Ing. Miguel Molina
Grupo de Tecnolog?a
Millenium Phone Center

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20101103/834f1350/attachment.htm

Hello!

http://linuxinnovations.com lists the evolution of the various
commands, applications, and other essential parts of Asterisk from
version 1.4 until 1.8, so you may find it a good resource for helping
you make a decision.

--Elliot