asterCC, asterisk callcenter and billing solution

In asterCRM, first eventsdaemon will connect to AMI(asterisk management interface) and store all events to database, then each call center agent need to read all asterisk events from database and analyze in php code, so it’s reduplicated and inefficient, especially it could become more and more serious when agent increased.

When using asterCC, the astercc daemon will get events from AMI and do analyze, then put only call events to database (ex. in the table named “curcdr”, include source/destination callerid, channel, starttime, answeredtime, duration …), agents only need to read from the database and get data it need, it is apparent that using astercc in asterCRM could get a much better efficiency.

In addition to efficiency, using asterCC provides asterCRM more useful features:

1. astercc could catch CDRs, and your recording files could get matched to the CDR
2. astercc could catch call status and put the result to predictive dialer resulet table, then no need modify your dialplan (you have to do so in the old asterCRM), you can get the call result and easy to recycle the no answered numbers

You can set the option “eventtype” in astercrm.conf.php to set if it use astercc
when it’s eventtype = event, it uses the tradition way, so make sure eventdaemon.pl is running
when it’s eventtype = curcdr, it uses astercc, make sure astercc is running

According above stated, the conclusion is

More about asterCC, please go visit asterCC site