vicidial.org

Hi,

Assuming that the current setup is a multi tenant where web and asterisk are in one box and the db server in a separate box. Is separation of the asterisk server from the web server relevant? Will it have a great impact in the cpu usage?



Regards,
Lui

Hello Lui,
Can you please let is a little bit about you?

-Your vicidial version with build
-Installation method with version

Hi Omarr,

I will revise my question.

I divided vicidial into 3 servers. Then give the functions of each.

1. Web - HTML/Images, PHP Scripts
2. DB - SQL Queries
3. Asterisk - Voice Over IP, Conferences, Channels, Call routing, IVR, Perl Scripts, etc.

Example Scenario:
25 agents
2:1 ratio (2 lines per agent, around 50 calls simultaneous)
outbound only
multi tenant setup (web/asterisk + DB)

Since the database is consuming high load because it's processing queries then it's a good idea to separate it. However, I'm not sure about the WEB. I know that the Asterisk is also consuming high load because of the perl scripts. Do you think that it's a good idea to separate the web from the asterisk? Does the php scripts/html/images in the web server consume high of load? Will it give a give impact on the overall performance if we do it that way?


Thanks,
Lui

best practice is to have a server for each of these roles and when any one of them begins to bog down, clone that server's role to create more capacity. This does not work with the DB server, of course, which is why the DB server is usually the one with the most horsepower.

You can also further divide the roles:

Web = Web for Administration or Web for Agents
Web for administration can be on a Virtual server somewhere. Pulls very little load
So there could actually be Two web roles instead of one.

Dialer = Dialer for Trunks (carriers) or Dialer for Agents (meetme, phones)

And then there are a couple more:
Archive server => This need not actually even have any vicidial code in it. On the other hand, Vicibox 4.0 has the ability to activate FTP and web for this purpose. It should also have Web so the admin links to recordings will still work. This would be the machine with the huge HD to store recordings. RAID1 to allow a dead drive to NOT wipe out all your recordings. And mirrored offsite just to be funny.

Slave MySQL Replication / Report server => This one is tricky, but in an enterprise environment can be quite useful to reduce MySQL load while pulling hefty reports for daily activities. this will also generally hold your individual server backups for that rainy day.