Looks like there were some changes that went into 1.8 that were supposed to
fix the problem, and the issue was closed because the version the reporter
was on hit EOL. If you think this is a bug within Asterisk, please file an
issue with the appropriate information so we can triage it!
As a side note, make sure you are on version 13 or 15. Any other version
will be autoclosed since bug fixes are not done due to EOL.
Hope this helps!
On Wed, Mar 7, 2018 at 7:29 AM, D'Arcy Cain <da...@vybenetworks.com> wrote:
> I had a problem inserting CDR records into my PostgreSQL database.
> According to the log it failed to open the database at startup. I
> searched and found the following report.
> However, it looks like it was closed after 14 months and nothing was
> done about the problem. Is there any point to opening another report?
> How do we make sure that the issue doesn't get forgotten?
> D'Arcy J.M. Cain
> Vybe Networks Inc.
> IM:da...@vex.net VoIP: sip:da...@vybenetworks.com
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> Check out the new Asterisk community forum at: https://community.asterisk.
> New to Asterisk? Start here:
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
Check out the new Asterisk community forum at: https://community.asterisk.org/
New to Asterisk? Start here:
asterisk-users mailing list
To UNSUBSCRIBE or update options visit: