On Thu, 2011-02-24 at 23:24 -0300, Andrew Latham wrote:
On Tue, Feb 22, 2011 at 12:16 PM, Ishfaq Malik i...@pack-net.co.uk wrote:
Has this issue been fixed in this release of 1.8 (or even in the
previous 1.8.2.3)?
https://issues.asterisk.org/bug_view_advanced_page.php?bug_id=18403
On Tue, Feb 22, 2011 at 12:16 PM, Ishfaq Malik i...@pack-net.co.uk wrote:
Has this issue been fixed in this release of 1.8 (or even in the
previous 1.8.2.3)?
https://issues.asterisk.org/bug_view_advanced_page.php?bug_id=18403
Thanks
Ish
Ishfaq, I spoke to soon and was looking at the
The Asterisk Development Team has announced security releases for Asterisk
branches 1.4, 1.6.1, 1.6.2, and 1.8. The available security releases are
released as versions 1.4.39.2, 1.6.1.22, 1.6.2.16.2, and 1.8.2.4.
These releases are available for immediate download at
Has this issue been fixed in this release of 1.8 (or even in the
previous 1.8.2.3)?
https://issues.asterisk.org/bug_view_advanced_page.php?bug_id=18403
Thanks
Ish
On Tue, 2011-02-22 at 08:02 -0500, Asterisk Development Team wrote:
The Asterisk Development Team has announced security releases
On Tue, Feb 22, 2011 at 12:16 PM, Ishfaq Malik i...@pack-net.co.uk wrote:
Has this issue been fixed in this release of 1.8 (or even in the
previous 1.8.2.3)?
https://issues.asterisk.org/bug_view_advanced_page.php?bug_id=18403
Thanks
Ish
snip
--
Ishfaq Malik
Software Developer
On 11-02-22 10:16 AM, Ishfaq Malik wrote:
Has this issue been fixed in this release of 1.8 (or even in the
previous 1.8.2.3)?
https://issues.asterisk.org/bug_view_advanced_page.php?bug_id=18403
No. The ChangeLog would give you the information you're looking for.
