[asterisk-users] Fwd: Re: Asterisk CLI unresponsive

[Matthew Jordan]

----- Original Message -----
> From: "Jonas Kellens" <jonas.kellens at telenet.be>
> To: isrlgb at gmail.com, "Asterisk Users Mailing List - Non-Commercial Discussion" <asterisk-users at lists.digium.com>
> Sent: Monday, February 6, 2012 8:15:50 AM
> Subject: Re: [asterisk-users] Fwd: Re: Asterisk CLI unresponsive
> 
> On 02/06/2012 12:25 PM, isrlgb at gmail.com wrote:
> > Your running into a bug and the only way to solve it is to report
> > it and debug it and hope for a fix
> > There is no way someone can help without it being debugged and
> > knowing what's causing it to lockup
> >
> > The only key to unlcock it when it gets locked is by restarting
> > asterisk
> 
> I am now using 1.6.2.22. Would I then be better upgrading to 1.8 ?
> Does
> 1.8 has fewer bugs ?!

Whether or not 1.8 has fewer bugs is a question without a definite answer.
While you can easily do a search in JIRA to find the bugs currently opened
against a release, that does not mean that a version of software works better
or worse in your particular deployment.  If 1.8 had a bug in a module that
you do not use, that is obviously of little impact versus a bug in a module
that you do use.  Feel free to look at the open issues against 1.8 to determine
if there are any open issues that would prevent you from upgrading.

Beyond what is currently reported in the public issue tracker, determining
the set of bugs (for some definition of "bug") in any piece of software is
impossible.

What you should be taking into account is that your version of software is
unsupported.  If you report your issue in JIRA, you will be asked to reproduce
it in 1.8.  If you decide not to, the issue will be closed.  If someone would
like to look at the backtrace they can, but it would have to be a choice
made by some member of the Asterisk community.  If they diagnose it and can
provide a patch that's great - but the 1.6.2.x line will not be officially
patched.  You will have to patch the software yourself, and maintain your
patched version of Asterisk.

I will say that we have fixed a lot of locking issues in Asterisk in 1.8
and later branches, and continue to fix them as they arise.

> 
> Kind regards,
> Jonas.
> 

Matthew Jordan
Digium, Inc. | Software Developer
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at: http://digium.com & http://asterisk.org