vicidial答疑

一,vicidial 为什么不使用Asterisk的Queue功能?

We didn't use Asterisk Queues
when we started the project because we needed easy manager barge-in along with 3rd and 4th party calling and DTMF macros,
all of which cannot be done in Asterisk Queues.
Also, meetme allows recording an agent across calls,
which could not be done in Queues at the time(not sure if it's possible now either)

Using Queues would require a lot of code changes to vicidial.
 The entire system is build around a database queue of calls and sending calls to an extension(which is the meetme room of the agent).
 If you wanted to use Queues you would need to somehow integrate the Asterisk Queues and Agents with the VICIDIAL auto_calls and live_agents tables which would not be an easy task.
 
二,vicidial为什么不能使用MySQL clustering.

Vicidial requires the MyISAM data engine type, which is not compatible with MySQL clustering, which is based upon INNOdb.

Vicidial is a real-time application that requires query queueing, something that is not enabled in InnoDB by default, and if you do enable it there can be serious performance issues at high load when compared to using MyISAM.

We have had success with vicidial clusters up to 500 seats using a well tuned MySQL master/slave combination and the right hardware, we haven't had the opportunity to test any larger installations than that.

If you could describe in more detail the operations, distribution, call handling method, call volume and other specifications we should be able to offer you some suggestions.

三,vicidial为什么不能使用戴尔PERC卡

a hardware caching RAID controller(we ONLY recommend LSI Logic MegaRAID)

The Dell Perc cards all have issues under high load in our experience, they are not designed for SMP Linux heavy RAID IO like the LIS MegaRAID caching RAID controllers are.