[asterisk-dev] The New CDR system

critch critch at basesys.com
Sat Mar 31 06:52:00 MST 2007

On Sat, 2007-03-31 at 13:26 +0200, Andreas Sikkema wrote:
> On Friday 30 March 2007 23:06:46 Steven Critchfield wrote:
> > Security. Funneling CDRs over IAX to a asterisk instance that had no
> > outside connectivity that was billable would only expose yourself to
> > maybe someone hacking their way into leaving bogus CDR records.
> If your network design is so poor that your db server is connected to the 
> internet you deserve all the trouble you're going to get.
> > I don't know if I would want a mysql or other internet enabled DB to be
> > publicly facing. I could let a asterisk instance capture the CDR events
> > and drop them to whatever backend is necessary without exposing the
> > backend.
> >
> > Management, bringing the CDRs back to a single asterisk box would let
> > you manage them all from a single point. Next step would be to provide a
> > way for failover and/or queueing of these events on the off chance the
> > other side is down.
> In  what way is Asterisk so different that it needs to reinvent the wheel in 
> this area? Database servers have been the backend for webservers for at least 
> a decade now (and before that for other services) and the DB server creators 
> might just have solved most of the issues here. This whole idea smells of the 
> NIH syndrome.

You are assuming a single geographic location if you think all of your
install base would be connected to the same private DB. I know of
installs that are not in the same location. So automatic consolidation
of information would be nice.

Also it sounds like this is going to happen because of other features.
Specifically other asterisk related information being pushed from
instance to instance for other purposes. This is one of those ways that
Digium is helping build asterisk into a system that can scale well past
the single location or small install that it easily handles now. 
critch <critch at basesys.com>

More information about the asterisk-dev mailing list