similar to: The Asterisk bug tracker :: please think twice before opening a report!

Welcome to a new issue of Asterisk Summer News! The holiday season is coming to an end here in Sweden, people are getting back to work and the kids will start going to school next week. Life is slowly adopting to normal and I have to start dressing more towards a businessman than a beach bum. Guess I have to start going to the gym again as well. Anyway, back to the topic. Asterisk and VoIP.

Okay fellow Asterisk users... Listen up (or perhaps more appropriately, "read down"). The Asterisk community is growing at a remarkable pace. I know there are thousands of you out there -- in fact there are over eight *thousand* subscribers to asterisk-users alone, and almost one *thousand* registered users on the bug tracker. The #asterisk IRC channel is consistently in the top 10

Dear Asterisk community, We are now working hard to complete Asterisk 1.2, testing and finalizing the existing patches and work that is going on in the developer team. Now is too late to file feature requests for 1.2 in the bug tracker. Unless you have a solid, working and tested patch, we will not consider the feature request on behalf of the developer team. A bug marshal will propably close

Welcome to the Asterisk users community! ---------------------------------------- Asterisk is the leading Open Source Telephony platform, with support both for classical telephony and IP telephony. Asterisk.org is a fast moving project. New code is added every day. Our community is also growing fast and we're having a lot of interaction, on the IRC and on the mailing lists. It's great

Today is Swedens national day - since a few years a holiday too. We don't have a tradition on how to celebrate. Sweden has not been to war for a very long time, so there's no real spirit for the country here - it's been aroundfor such a long time, so what? :-) Guess we have to learn from abroad, to get a celebration feeling like July 4th in the US or May 17th in Norway (from

Friends, For a long time, we needed a platform for managing feature requests - things that the community or developers would like to see in Asterisk. In the bug tracker we used to have a "feature request" category, but there was no good way to handle them in the bug tracker and they where in the way for the work done by developers in the tracker. The new site is basically a blog

During the last week, we have had several support issues being reported as bugs on the bug tracker. Since we are going into a final development stage on version 1.1dev (CVS HEAD) in order to complete the 1.2 release we are under pressure to fix bugs and handle a lot of reports in a short time frame. Neither the bug tracker or the asterisk-dev mailing list is second-line support, they're

Friends, To update you on recent changes in svn trunk, I can inform you that we now have ever smarter ways to handle media streams in Asterisk than we do in 1.2 for the IAX2 and SIP protocols. * IAX2: Splitting signalling and media apart Starting with the IAX2 protocol, we now have the ability to transfer media streams to go directly between IAX2 servers and keep the signalling path.

Friends in the Asterisk.org community, There is a lot of cool stuff going on in Asterisk development, things that will change Asterisk and make it work better in your organisation, make it easier to sell in your area or give you more consulting oppurtunities - in short, functionality that will make a lot of sense for you users. However, developers can't really get anywhere without a

We're getting closer and closer to a 1.0 release of Asterisk. In order to get there, the development is now 110% focused on solving major, critical and crash bugs. (And yes, if you follow the CVS updates, you'll see the impossible extra 10% :-) * YOU'RE NOT FORGOTTEN, BUT ON HOLD (WITHOUT ON-HOLD-MUSIC) * If you're reporting other bugs, please don't be disappointed or require

Rather hasty I think. I think whatever version 1.2.X winds up on should be the most stable release of Asterisk, period. Thanks, Steve Totaro http://www.asteriskhelpdesk.com KB3OPB > -----Original Message----- > From: asterisk-users-bounces@lists.digium.com [mailto:asterisk-users- > bounces@lists.digium.com] On Behalf Of Olle E Johansson > Sent: Tuesday, May 29, 2007 5:19 AM >

Asterisk buddies! If you have open issues in the bug tracker, please help us with providing fast responses. All developers are working real hard to close bugs pending the new release, so we kindly ask you for fast responses on our questions in the bug tracker. The quicker the better and we'll get 1.2 out of the door sooner. If you have new ideas, feature requests, thoughts - please keep the

Prompted by the recent discussion on the mailing list regarding the Asterisk development and release process (or lack thereof), John Todd, Thorsten Lockert, Brian K. West, and myself have put together a plan to address the most significant two legitimate concerns that have been expressed regarding these processes. Specifically: Concern #1: Asterisk release schedules and path to 1.0.0 Asterisk

Sunday news is today published on a monday. Yesterday was fourth of july, and I used that as an excuse for being off line yesterday. (Sweden's national day is June 6th - and it's not yet a public holiday, btw). Most of my Asterisk time lately have been used for producing the registration site for Astricon and tracking down speakers that haven't sent in their material for the conference

---------------------------------------------------------------------- Message: 1 Date: Tue, 6 Mar 2007 20:02:07 +0100 From: Olle E Johansson <oej@edvina.net> Subject: [asterisk-users] Building a new voicemail system... Testers needed! To: Asterisk Non-Commercial Discussion Users Mailing List - <asterisk-users@lists.digium.com> Message-ID:

This week starts with the exciting news: We're getting close to Asterisk 1.0 again. After the failed attempt earlier this year, we've been able to remove a lot of the MAJOR/CRASH bugs from the bug tracker and Mark feel's it's time to target 1.0 again. At this point, the community needs to work as a community, spending extra time on finding bugs, solving issues, improving

My continued thanks go out to you guys and the rest of the Asterisk community. Asterisk HAS grown quite a bit since I first used it over a year ago, and ALL the credit goes to the community. I look forward to the new tree and will continue to CVS off of the current branch so that I can stay on the cutting edge. Once again thanks for all your time and efforts in making this a great, powerful

*lol* I think he was referring to a ASTERISK reboot, not a phone reboot. > -----Original Message----- > From: Olle E Johansson [mailto:oej@edvina.net] > Sent: Thursday, March 23, 2006 1:15 PM > To: Asterisk Users Mailing List - Non-Commercial Discussion > Subject: Re: [Asterisk-Users] Re: Subscription state after reload (New > subject) > > > > 23 mar 2006 kl.

How can a reload clear registrations? If I 'reload' without using realtime, I keep my sip peers (as well as astdb). I can still contact other phones... registration info is still there. If I `reload` with realtime, I lose my sip peers (but astdb remains). I can _STILL_ contact other phones.... registration info is still there and Asterisk must be referring to astdb to find the IP

Time to reboot and re-start Asterisk, well, hrrm, monthly, news. It's been a hectic fall with a lot to do, both before and after Astricon. At this time, we're preparing for two Astricon shows in 2005. And no, we haven't made a decision on where to run the European Astricon, not yet. I am preparing to travel to the USA again this coming week. Today, I'm spending my time finding