[asterisk-bugs] [Asterisk 0016960]: Read factory 0xb6d0acb8 was pretty quick last time, waiting for them
Asterisk Bug Tracker
noreply at bugs.digium.com
Fri Mar 12 13:55:10 CST 2010
The following issue requires your FEEDBACK.
======================================================================
https://issues.asterisk.org/view.php?id=16960
======================================================================
Reported By: pruonckk
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 16960
Category: Core/General
Reproducibility: always
Severity: minor
Priority: normal
Status: feedback
Asterisk Version: Older 1.4 - please test a newer version
JIRA: SWP-1021
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2010-03-04 08:26 CST
Last Modified: 2010-03-12 13:55 CST
======================================================================
Summary: Read factory 0xb6d0acb8 was pretty quick last time,
waiting for them
Description:
Some calls are droped and when i set debug mode on asterisk i get a log of
messages
[Mar 4 11:19:05] DEBUG[31638] audiohook.c: Read factory 0xb6d0acb8 was
pretty quick last time, waiting for them.
Im using a asterisk 1.4.28, i cant upgrade my asterisk version to 1.4.29
because i need the openr2 patch (i can try a manualy apply if necessary),
and i cant upgrade to 1.6.2 (i try this) because the context option from
queues.conf dont work on this version.
======================================================================
----------------------------------------------------------------------
(0119315) lmadsen (administrator) - 2010-03-12 13:55
https://issues.asterisk.org/view.php?id=16960#c119315
----------------------------------------------------------------------
As there is nothing we can do with this bug report as it is (since the
suggestion would be to update to a newer 1.4 since 1.4.28 is quite old
now), then our suggestion is to report your issue with 1.6.2 so it can be
resolved, at which point you can then use 1.6.2.
Otherwise, you'll need to somehow move forward in 1.4 to verify if the
issue still exists, or else there won't be much we can do with the issue as
it is.
Issue History
Date Modified Username Field Change
======================================================================
2010-03-12 13:55 lmadsen Note Added: 0119315
2010-03-12 13:55 lmadsen Status acknowledged =>
feedback
======================================================================
More information about the asterisk-bugs
mailing list