[asterisk-dev] Adding Berkeley DB to Asterisk 1.8 and above

Paul Belanger paul.belanger at polybeacon.com
Tue Jan 28 16:42:31 CST 2014


On Tue, Jan 28, 2014 at 5:01 PM, Tech Support <asterisk at voipbusiness.us> wrote:
> All;
>
>     I'm working on a project (using Asterisk 1.8, but 11 would probably work
> just as well) where so far I've been able to originate over 1,000 concurrent
> outbound faxes. I have no problem with that so far. Where I have the problem
> is that Asterisk is dumping core after the faxes are sent. Now two things
> happen after the faxes are sent. (1) A fax log similar to a CDR is written
> to MySQL for each fax transmitted. Think of it as a fax-centric CDR that
> only contains information related to the fax just sent. (2) The Asterisk CDR
> is written to MySQL. The problem appears to be with the CDR's because if I
> do not record them, things seem to appear to work correctly. I'm going to
> try a remote MySQL server on a second machine and that may or may not work,
> but I don't want to have to come up with the expense of a second server if I
> could avoid it. I tried using Sqlite for the CDR's but the concurrency
> issues were a killer. What I would really like to do is add the Berkeley DB
> to Asterisk. I'm thinking that by using the Berkeley DB, I could most likely
> write the fax logs and CDR's without having the system even breathing heavy.
> The problem is that I have no idea how to add the BDB to Asterisk. Can
> someone point me in the right direction as far as documentation and examples
> go? I would greatly appreciate it and will make it all available publically
> if the implementation turns out well.
>
This post is more suited for -users list.  But, you should be using
res_odbc, vs native database backends.  They're generally more
supported in the community.

-- 
Paul Belanger | PolyBeacon, Inc.
Jabber: paul.belanger at polybeacon.com | IRC: pabelanger (Freenode)
Github: https://github.com/pabelanger | Twitter: https://twitter.com/pabelanger



More information about the asterisk-dev mailing list