Multi-server setup with servers at different locations?

[bryan.kewl]

GoAutoDial 2.1CE
VICIDIAL VERSION: 2.4-325c
BUILD: 110430-1924

Right now we have only 1 server serving all 3 components (db, web and asterisk). Now I am planning to bring in couple of more servers and make a cluster, but want to have these new server at multiple different geographical locations.

We also want to use a central server for database to provide db-services to all the asterisk boxes at different locations.

Do you think this solution will work without any hiccups?

Another issue is that the server we want to use for db is already running, and we can't install asterisk/vicidial on this server. So is it possible that I install vicidial/goautodial on one server and thn export the database and import it on the db-server? We can grant all the privileges and setup the firewall etc to allow asterisk boxes to communicate with db, do we need anything else to make it work?

Are there any other required demons or cron scripts or other processes for the database server, or a bare server with mysql is enough?

PS: I have also read the "Vicidial Multi-Server Manual by Poundteam v1 1.pdf". Though I initially wanted to move the web and db server but after reading the guide its says that for the web we do require a complete vicibox installation. Also on page 10 its mentioned that "A server that is being used only for MySQL does not need to have Vicidial installed on it. Any Standard MySQL server will suffice. ... For your first cluster, it is simplest, however, to use a Standard Vicibox server for this one as well." So what are the other key components we need on the db server. Also if there is a way to move the web-server to a different server without installing vicidial on the target server, I am really interested in the approach and also willing to help/assist if someone is planning to test it.

[williamconley]

these new server at multiple different geographical locations

NO

other key components we need on the db server

NONE, but the my.cnf files and some other possible settings may need to be changed. If you use Kumba's Vicibox Redux 3.1.10 ... all that is "handled".

[bryan.kewl]

Thanks William, so your suggestions is to have all the vicidial boxes on same location. If possible, can you tell me what major problems will occur when the cluster is spread on different locations. The main reason I want to have the server on different locations is to have atleast 1 server close to its users and/or carrier. For example if I put all the servers in a US datacenter and have users from Asia, while carrier are from EU, US and Asia depending on the destination, so to place a call to EU, the call will travel from Asia to US thn US to EU-carrier and thn to the final destination. This long route can create voice issues and I want to avoid such situations.

I don't want these geo-spread servers to load balance but just provide a better route and a centralized user control point.

So is it possible to have the database server at another location, or it also need to be in the same location aswell?

[williamconley]

the database server has massive traffic. all processes WAIT for the response. you will gain faster voice throughput ... but vicidial will then have to wait for those database responses. when you add users, you will find that the "wait time" for a single slow packet will cause crashes on all the satellite servers.

i'd be very interested to see how well it worked and how many users you got onto the system before "death" (2? 5? 10?) but so far noone has ever given any data.

The database server is the Heart of the system. All processes depend on it, and any time-sensitive processes will fail if the database server does not respond instantly. To get it to work, you would likely need a network connection that was so good that it would ... easily transmit the SOUND without problems as well.

Of course the administration web page is not time-sensitive. But the trunk server and agent phone server and agent web server all have intensive operations that will likely crack under stress if MySQL is not local. (usually these functions are in the same box, but not necesssarily in a cluster.) And your purpose would be to get the the trunk server and agent phone server to a remote location (agent web and admin web and database "remote"). Interesting.

Sounds like a good experiment, though. Try it! I'd love to hear the results.

Of course, we have Fiber in our colo, so international is only an issue if there is a problem at THAT end of the circuit. (which does happen).