Re: [asterisk-users] *End Of Life ASTERISK 1.2.X Was: INSTRUCTIONSFOR THE ASTERISK COMMUNITY - PLEASEREAD NOW *
On Wed, 2007-05-30 at 07:50 -0400, Matt wrote: We still run 1.2.6 on some of our production systems because, so far, it has been the only stable release of Asterisk for us. Other versions core dump for no reason and do all kinds of other funky things. On 5/29/07, Jaswinder Singh [EMAIL PROTECTED] wrote: What you say might be true for small business or home pbx systems . But if you have a production server handling sip/iax trunks over internet then you need to upgrade to avoid security related bugs and exploits that are released . Well, once you've developed the perfect asterisk app, I guess you could just stick with it forever and never change anything. Or, you invest some time==money into the process, and keep a separate machine to do testing with, file bugs, and push them thru so someday, you get an even better perfect asterisk app. A once a day crash could never, ever get fixed without users collecting a backtrace, filing a bug, and helping out with testing! If asterisk is really involved in your cash flow, I don't see how you can justify grabbing one version and staying with it forever. Such a business model is doomed to extinction. All apps, for that matter, all living and even artificial things follow a predictable sequence that ends in death. Your perfect server will last maybe 5 or so years max, and then the hardware will fail or obsolesce, and unless you actively participate in keeping the software up to date, you will have an expensive, time-consuming, perhaps fatal ordeal getting your app up and running on newer hardware/software again. A sustaining model has you actively participate in the evolution of the software you find critical. Right? In a closed source model, you'd pay yearly maintenance, and get a voice in the direction the software evolved. In an open-source model, the yearly maintenance cost is your own time in filing bugs, and testing, submitting patches, etc. One way or the other, it costs you something. Or, like dinosaurs, stick with one version and follow that evolutionary branch to its end. murf -- Steve Murphy Software Developer Digium smime.p7s Description: S/MIME cryptographic signature ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] *End Of Life ASTERISK 1.2.X Was: INSTRUCTIONSFOR THE ASTERISK COMMUNITY - PLEASEREAD NOW *
My specific problem is that Asterisk 1.2.17 and 1.2.18 (I've not tried 1.2.16) core dumps at least once per day. 1.2.15 works just fine for me. I don't know if there are open bugs. I've not opened any bugs. Any time I open a bug for a problem I have on a production server, all people want me to do is test patches to see if they fix the issue. They don't seem to understand the term production server. Sorry, but this is my JOB, not my hobby. Perhaps the customers of the developers don't care if the PBX crashes once per day, but my customers do care and I will do whatever is required to make them stop yelling at me. What made them stop yelling at me is moving back to 1.2.15. I guess it's not that they don't care, but that they haven't got the same hardware/software environment as yours. ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [asterisk-users] *End Of Life ASTERISK 1.2.X Was: INSTRUCTIONSFOR THE ASTERISK COMMUNITY - PLEASEREAD NOW *
-Original Message- From: [EMAIL PROTECTED] [mailto:asterisk-users- [EMAIL PROTECTED] On Behalf Of Stephen Bosch Sent: Tuesday, May 29, 2007 10:30 AM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [asterisk-users] *End Of Life ASTERISK 1.2.X Was: INSTRUCTIONSFOR THE ASTERISK COMMUNITY - PLEASEREAD NOW * John covici wrote: I have an install using Rhino cards -- I sure hope they get their act together by then. They have no choice now, do they? Nothing focuses the attention like a deadline. -Stephen- You are lucky to have any support for anything other than Adtran. The very early Asterisk code supported Adtran only. Thanks, Steve Totaro http://www.asteriskhelpdesk.com KB3OPB ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] *End Of Life ASTERISK 1.2.X Was: INSTRUCTIONSFOR THE ASTERISK COMMUNITY - PLEASEREAD NOW *
We still run 1.2.6 on some of our production systems because, so far, it has been the only stable release of Asterisk for us. Other versions core dump for no reason and do all kinds of other funky things. On 5/29/07, Jaswinder Singh [EMAIL PROTECTED] wrote: What you say might be true for small business or home pbx systems . But if you have a production server handling sip/iax trunks over internet then you need to upgrade to avoid security related bugs and exploits that are released . You seem to miss the idea here. You work with a version that supports your feature needs and find the sub-version that provides the most stability for your deployments. Lets face it these boxes should go in and run for weeks, months or even years without much intervention (assuming the mission of the box does not change). I'm running a 1.2.7.something (i think) that has been running almost nonstop since installing. Very reliable and stable for my needs. Compared to a Merlin or Nortel or any other system out that I feel I have a much better product. Could I benefit from a newer sub-version? Maybe. Will I upgrade the box in it current roll? No. Unless the application I use the box for has a major change (or the hardware dies) I'll just let it keep on running as it is. For my future deploys I am working closer with 1.4. The reason is clear. 1.4 is the future of asterisk. When 1.6 or 2.0 comes out I'll investigate into migrating in that direction at that time because that will become the future of asterisk. ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] *End Of Life ASTERISK 1.2.X Was: INSTRUCTIONSFOR THE ASTERISK COMMUNITY - PLEASEREAD NOW *
I'm running a 1.2.7.something (i think) that has been running almost nonstop since installing. Very reliable and stable for my needs. This version has some security issues inside. ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [asterisk-users] *End Of Life ASTERISK 1.2.X Was: INSTRUCTIONSFOR THE ASTERISK COMMUNITY - PLEASEREAD NOW *
I think its a fair decision . 1.2 is very stable and they are not closing it all together , security issues will still be fixed . They need to concentrate more on 1.4 to make it bugfree . Fair indeed. I would guess that a completely stable 1.2 w/ security maintenance is acceptable to the majority of users. Those folks still using 1.0.x certainly aren't clamoring for new features! The great many folks using 1.2 are happy w/ a stable release and don't necessarily need new features. A lot of those folks might consider moving to 1.4 when the stability issues and bugs are worked out. Possibly there are features that they would like to have but they don't want to invest the time and effort into a migration until they are reasonably confident that 1.4 will meet their needs. I think that having the development team be able to focus the majority of their attention on improving 1.4 is better than having them split their time between the old and new releases. I'm feeling like there's more ROI to be had improving 1.4. -MC ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] *End Of Life ASTERISK 1.2.X Was: INSTRUCTIONSFOR THE ASTERISK COMMUNITY - PLEASEREAD NOW *
Michael Collins wrote: I think its a fair decision . 1.2 is very stable and they are not closing it all together , security issues will still be fixed . They need to concentrate more on 1.4 to make it bugfree . Fair indeed. I would guess that a completely stable 1.2 w/ security maintenance is acceptable to the majority of users. Those folks still using 1.0.x certainly aren't clamoring for new features! The great many Except that for some users 1.2.18 is NOT stable. I've had to roll back to 1.2.15 on my production servers in order to prevent core dumps at least once per day. No, I am not willing to turn my production servers into testing servers to solve this. Doing so would make me a former consultant for these customers. ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] *End Of Life ASTERISK 1.2.X Was: INSTRUCTIONSFOR THE ASTERISK COMMUNITY - PLEASEREAD NOW *
Well i guess you just need a good look on logs for why and when you are getting core dumps . We are having few servers running .1.2.18 and it has turned out to be most stable in whole 1.2 branch ( had some issues with 1.2.13 and 14 ) . Except that for some users 1.2.18 is NOT stable. I've had to roll back to 1.2.15 on my production servers in order to prevent core dumps at least once per day. No, I am not willing to turn my production servers into testing servers to solve this. Doing so would make me a former consultant for these customers. ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] *End Of Life ASTERISK 1.2.X Was: INSTRUCTIONSFOR THE ASTERISK COMMUNITY - PLEASEREAD NOW *
Eric ManxPower Wieling wrote: Michael Collins wro Except that for some users 1.2.18 is NOT stable. I've had to roll back to 1.2.15 on my production servers in order to prevent core dumps at least once per day. No, I am not willing to turn my production servers into testing servers to solve this. Doing so would make me a former consultant for these customers. You seem to miss the idea here. You work with a version that supports your feature needs and find the sub-version that provides the most stability for your deployments. Lets face it these boxes should go in and run for weeks, months or even years without much intervention (assuming the mission of the box does not change). I'm running a 1.2.7.something (i think) that has been running almost nonstop since installing. Very reliable and stable for my needs. Compared to a Merlin or Nortel or any other system out that I feel I have a much better product. Could I benefit from a newer sub-version? Maybe. Will I upgrade the box in it current roll? No. Unless the application I use the box for has a major change (or the hardware dies) I'll just let it keep on running as it is. For my future deploys I am working closer with 1.4. The reason is clear. 1.4 is the future of asterisk. When 1.6 or 2.0 comes out I'll investigate into migrating in that direction at that time because that will become the future of asterisk. smime.p7s Description: S/MIME Cryptographic Signature ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] *End Of Life ASTERISK 1.2.X Was: INSTRUCTIONSFOR THE ASTERISK COMMUNITY - PLEASEREAD NOW *
Hi, Except that for some users 1.2.18 is NOT stable. I've had to roll back to 1.2.15 on my production servers in order to prevent core dumps at least once per day. No, I am not willing to turn my production servers into testing servers to solve this. Doing so would make me a former consultant for these customers. I've got some core dump on 1.2.18 and the patch available on ticket 9602 have fix all issues, using 1.2.18 on lots of server without any issues http://bugs.digium.com/view.php?id=9602 -- Joel Vandal ScopServ Inc. ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] *End Of Life ASTERISK 1.2.X Was: INSTRUCTIONSFOR THE ASTERISK COMMUNITY - PLEASEREAD NOW *
What you say might be true for small business or home pbx systems . But if you have a production server handling sip/iax trunks over internet then you need to upgrade to avoid security related bugs and exploits that are released . You seem to miss the idea here. You work with a version that supports your feature needs and find the sub-version that provides the most stability for your deployments. Lets face it these boxes should go in and run for weeks, months or even years without much intervention (assuming the mission of the box does not change). I'm running a 1.2.7.something (i think) that has been running almost nonstop since installing. Very reliable and stable for my needs. Compared to a Merlin or Nortel or any other system out that I feel I have a much better product. Could I benefit from a newer sub-version? Maybe. Will I upgrade the box in it current roll? No. Unless the application I use the box for has a major change (or the hardware dies) I'll just let it keep on running as it is. For my future deploys I am working closer with 1.4. The reason is clear. 1.4 is the future of asterisk. When 1.6 or 2.0 comes out I'll investigate into migrating in that direction at that time because that will become the future of asterisk. ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] *End Of Life ASTERISK 1.2.X Was: INSTRUCTIONSFOR THE ASTERISK COMMUNITY - PLEASEREAD NOW *
Eric ManxPower Wieling escreveu: Michael Collins wrote: Except that for some users 1.2.18 is NOT stable. I've had to roll back to 1.2.15 on my production servers in order to prevent core dumps at least once per day. No, I am not willing to turn my production servers into testing servers to solve this. Doing so would make me a former consultant for these customers. If you use app_macro you probably hit this: http://bugs.digium.com/view.php?id=9602 The fix: http://svn.digium.com/view/asterisk/branches/1.2/apps/app_macro.c?view=diffrev=63477r1=63476r2=63477 I thought there would be a 1.2.19 after that fix but it seems it's not easily triggered (but here I got many segfaults in different servers until the fix). Leonardo ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] *End Of Life ASTERISK 1.2.X Was: INSTRUCTIONSFOR THE ASTERISK COMMUNITY - PLEASEREAD NOW *
On Tue, May 29, 2007 at 01:06:54PM -0500, Eric ManxPower Wieling wrote: Michael Collins wrote: I think its a fair decision . 1.2 is very stable and they are not closing it all together , security issues will still be fixed . They need to concentrate more on 1.4 to make it bugfree . Fair indeed. I would guess that a completely stable 1.2 w/ security maintenance is acceptable to the majority of users. Those folks still using 1.0.x certainly aren't clamoring for new features! The great many Except that for some users 1.2.18 is NOT stable. I've had to roll back to 1.2.15 on my production servers in order to prevent core dumps at least once per day. No, I am not willing to turn my production servers into testing servers to solve this. Doing so would make me a former consultant for these customers. So basically what you're saying is that some efforts should be concentrated on 1.2 as well. So let's start with your specific problems. Are there open bugs for them? -- Tzafrir Cohen icq#16849755jabber:[EMAIL PROTECTED] +972-50-7952406 mailto:[EMAIL PROTECTED] http://www.xorcom.com iax:[EMAIL PROTECTED]/tzafrir ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] *End Of Life ASTERISK 1.2.X Was: INSTRUCTIONSFOR THE ASTERISK COMMUNITY - PLEASEREAD NOW *
Well if you are out of luck with asterisk .. How about its fork callweaver ? I am highly awaiting its stable release to see if it holds upto what its wiki says . On 30/05/07, Tzafrir Cohen [EMAIL PROTECTED] wrote: On Tue, May 29, 2007 at 01:06:54PM -0500, Eric ManxPower Wieling wrote: Michael Collins wrote: I think its a fair decision . 1.2 is very stable and they are not closing it all together , security issues will still be fixed . They need to concentrate more on 1.4 to make it bugfree . Fair indeed. I would guess that a completely stable 1.2 w/ security maintenance is acceptable to the majority of users. Those folks still using 1.0.x certainly aren't clamoring for new features! The great many Except that for some users 1.2.18 is NOT stable. I've had to roll back to 1.2.15 on my production servers in order to prevent core dumps at least once per day. No, I am not willing to turn my production servers into testing servers to solve this. Doing so would make me a former consultant for these customers. So basically what you're saying is that some efforts should be concentrated on 1.2 as well. So let's start with your specific problems. Are there open bugs for them? -- Tzafrir Cohen icq#16849755jabber:[EMAIL PROTECTED] +972-50-7952406 mailto:[EMAIL PROTECTED] http://www.xorcom.com iax:[EMAIL PROTECTED]/tzafrir ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] *End Of Life ASTERISK 1.2.X Was: INSTRUCTIONSFOR THE ASTERISK COMMUNITY - PLEASEREAD NOW *
At 16:17 5/29/2007, Tzafrir Cohen wrote: On Tue, May 29, 2007 at 01:06:54PM -0500, Eric ManxPower Wieling wrote: Michael Collins wrote: I think its a fair decision . 1.2 is very stable and they are not closing it all together , security issues will still be fixed . They need to concentrate more on 1.4 to make it bugfree . Fair indeed. I would guess that a completely stable 1.2 w/ security maintenance is acceptable to the majority of users. Those folks still using 1.0.x certainly aren't clamoring for new features! The great many Except that for some users 1.2.18 is NOT stable. I've had to roll back to 1.2.15 on my production servers in order to prevent core dumps at least once per day. No, I am not willing to turn my production servers into testing servers to solve this. Doing so would make me a former consultant for these customers. So basically what you're saying is that some efforts should be concentrated on 1.2 as well. So let's start with your specific problems. Are there open bugs for them? I don't know if this is an open bug, but I think an updated version with the fix should be in 1.2.19. This bug kills calls after 20 seconds. It took quite a bit of time to get our box to work. http://www.mail-archive.com/asterisk-users@lists.digium.com/msg181107.html -- Tzafrir Cohen icq#16849755jabber:[EMAIL PROTECTED] +972-50-7952406 mailto:[EMAIL PROTECTED] http://www.xorcom.com iax:[EMAIL PROTECTED]/tzafrir ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] *End Of Life ASTERISK 1.2.X Was: INSTRUCTIONSFOR THE ASTERISK COMMUNITY - PLEASEREAD NOW *
On Wed, May 30, 2007 at 03:35:36AM +0530, Jaswinder Singh wrote: Well if you are out of luck with asterisk .. How about its fork callweaver Is it not enough that they have forked Asterisk, you now want to fork from CallWeaver? You're sure after some interesting life ;-) ? I am highly awaiting its stable release to see if it holds upto what its wiki says . The Wiki also says quite a few good things about Asterisk. Some people here don't fully trust that. Please remind me how many public releases have there been of CallWeaver? You can say quite a few things about it and its codebase, but you seem to have picked the wrong argument. CallWeaver has yet to prove itself and earn its reputation. -- Tzafrir Cohen icq#16849755jabber:[EMAIL PROTECTED] +972-50-7952406 mailto:[EMAIL PROTECTED] http://www.xorcom.com iax:[EMAIL PROTECTED]/tzafrir ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] *End Of Life ASTERISK 1.2.X Was: INSTRUCTIONSFOR THE ASTERISK COMMUNITY - PLEASEREAD NOW *
Tzafrir Cohen wrote: On Tue, May 29, 2007 at 01:06:54PM -0500, Eric ManxPower Wieling wrote: Michael Collins wrote: I think its a fair decision . 1.2 is very stable and they are not closing it all together , security issues will still be fixed . They need to concentrate more on 1.4 to make it bugfree . Fair indeed. I would guess that a completely stable 1.2 w/ security maintenance is acceptable to the majority of users. Those folks still using 1.0.x certainly aren't clamoring for new features! The great many Except that for some users 1.2.18 is NOT stable. I've had to roll back to 1.2.15 on my production servers in order to prevent core dumps at least once per day. No, I am not willing to turn my production servers into testing servers to solve this. Doing so would make me a former consultant for these customers. So basically what you're saying is that some efforts should be concentrated on 1.2 as well. So let's start with your specific problems. Are there open bugs for them? My specific problem is that Asterisk 1.2.17 and 1.2.18 (I've not tried 1.2.16) core dumps at least once per day. 1.2.15 works just fine for me. I don't know if there are open bugs. I've not opened any bugs. Any time I open a bug for a problem I have on a production server, all people want me to do is test patches to see if they fix the issue. They don't seem to understand the term production server. Sorry, but this is my JOB, not my hobby. Perhaps the customers of the developers don't care if the PBX crashes once per day, but my customers do care and I will do whatever is required to make them stop yelling at me. What made them stop yelling at me is moving back to 1.2.15. ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] *End Of Life ASTERISK 1.2.X Was: INSTRUCTIONSFOR THE ASTERISK COMMUNITY - PLEASEREAD NOW *
Tzafrir Cohen wrote: On Tue, May 29, 2007 at 01:06:54PM -0500, Eric ManxPower Wieling wrote: Michael Collins wrote: I think its a fair decision . 1.2 is very stable and they are not closing it all together , security issues will still be fixed . They need to concentrate more on 1.4 to make it bugfree . Fair indeed. I would guess that a completely stable 1.2 w/ security maintenance is acceptable to the majority of users. Those folks still using 1.0.x certainly aren't clamoring for new features! The great many Except that for some users 1.2.18 is NOT stable. I've had to roll back to 1.2.15 on my production servers in order to prevent core dumps at least once per day. No, I am not willing to turn my production servers into testing servers to solve this. Doing so would make me a former consultant for these customers. So basically what you're saying is that some efforts should be concentrated on 1.2 as well. So let's start with your specific problems. Are there open bugs for them? My specific problem is that Asterisk 1.2.17 and 1.2.18 (I've not tried 1.2.16) core dumps at least once per day. 1.2.15 works just fine for me. I don't know if there are open bugs. I've not opened any bugs. Any time I open a bug for a problem I have on a production server, all people want me to do is test patches to see if they fix the issue. They don't seem to understand the term production server. Sorry, but this is my JOB, not my hobby. Perhaps the customers of the developers don't care if the PBX crashes once per day, but my customers do care and I will do whatever is required to make them stop yelling at me. What made them stop yelling at me is moving back to 1.2.15. ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
