That sounds fine except where registrations are involved although I'd suggest you look into SRV as well as RR for the DNS to more finely balance the load for clients which support it. Doug's mail says it all where registrations are involved - not all state information is stored in the database so you need to ensure that incoming and outgoing traffic for a given user is hitting the asterisk box with which they've registered.

Simon

On 6/17/06, unplug <[EMAIL PROTECTED]> wrote:
Hi,
  I am designing a asterisk load balancing model as follow.  There are
3 asterisks connected to a single DB and a single server storing all
the configuration file and voicemail.  Round Robin DNS will distribute
the request to asterisks.

DNS round robin ---+ asterisk1--------------------------+ DB and file server
                             +---asterisk2-----------------------+
                             +---asterisk3-----------------------+
Does anyone has load balancing experience implemented in asterisk that
can share?  Does my design work?  Does any conflict will happen in my
design?  Any comment?
Thanks!
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --

Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --

Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Reply via email to