[asterisk-ha-clustering] The results of your email commands

Thu Jan 17 08:23:21 CST 2008

Hello
    My scenario is like this:
    AudioCodes GW
    Two * production machines
    Extensions Ranges split between both * production systems.
    Mysql 4.1
    Asterisk BE 1.2
    SER 0.9
    Sync and transaction scripts to maintain data inetgrity.
    clients can register to either server.  SER is used for routing. If a client cannot get to it's primary server, it is then re-routed to the second server.
    This scenario has been up and running for over 1 year now with no issues.

    ---------------------------------------
    From: asterisk-ha-clustering-bounces at lists.digium.com [mailto:asterisk-ha-clustering-bounces at lists.digium.com] On Behalf Of Ricardo Carvalho
    Sent: Thursday, January 17, 2008 6:02 AM
    To: Asterisk High Availability and Clustering List - Non-CommercialDiscussion
    Subject: Re: [asterisk-ha-clustering] Load sharing between two asteriskservers
    My scenario is like this:
    * one production machine
    * one hot standby machine
    * MySQL Replication between both servers in Master/Master configuration for CDR and Realtime SIP
    * VRRP (running by the keepalived daemon) to share the same IP address which is set in SRV records of the DNS of the domain served by the Asterisk. Since asterisk daemon of both machines binds that virtual IP address, when the hot standby machine assumes production, by that time keepalived daemon starts asterisk automatically in that machine. 

- Ignored:

    * Since clients registration information isn't shared between servers because it is kept in AstDB and not in the MySQL (which is replicated between those two machines), I made one script that reboots all phones (about 300) that my site have so that they re-register when they go up. But this is a bad solution, the best thing would be to share registration information between both servers. Which one would be the best for me? What would you recommend? I was planning to use DRDB to replicate AstDB registration information but since I read in this thread it is only unidirectional, it already seams not to be so good idea... can and should DUNDI be used in my scenario? 

    Regards,
    Ricardo Carvalho.

          ____________________________________________________________________________________
    Looking for last minute shopping deals?  
    Find them fast with Yahoo! Search.   http://tools.search.yahoo.com/newsearch/category.php?category=shopping

- Done.

-----Inline Message Follows-----

My scenario is like this:

AudioCodes GW
Two * production machines
Extensions Ranges split between both * production systems.
Mysql 4.1
Asterisk BE 1.2
SER 0.9
Sync and transaction scripts to maintain data inetgrity.

clients can register to either server.  SER is used for routing. If a client cannot get to it's primary server, it is then re-routed to the second server.
This scenario has been up and running for over 1 year now with no issues.

---------------------------------------
From: asterisk-ha-clustering-bounces at lists.digium.com [mailto:asterisk-ha-clustering-bounces at lists.digium.com] On Behalf Of Ricardo Carvalho
Sent: Thursday, January 17, 2008 6:02 AM
To: Asterisk High Availability and Clustering List - Non-CommercialDiscussion
Subject: Re: [asterisk-ha-clustering] Load sharing between two asteriskservers

My scenario is like this:

* one production machine
* one hot standby machine
* MySQL Replication between both servers in Master/Master configuration for CDR and Realtime SIP
* VRRP (running by the keepalived daemon) to share the same IP address which is set in SRV records of the DNS of the domain served by the Asterisk. Since asterisk daemon of both machines binds that virtual IP address, when the hot standby machine assumes production, by that time keepalived daemon starts asterisk automatically in that machine. 

* Since clients registration information isn't shared between servers because it is kept in AstDB and not in the MySQL (which is replicated between those two machines), I made one script that reboots all phones (about 300) that my site have so that they re-register when they go up. But this is a bad solution, the best thing would be to share registration information between both servers. Which one would be the best for me? What would you recommend? I was planning to use DRDB to replicate AstDB registration information but since I read in this thread it is only unidirectional, it already seams not to be so good idea... can and should DUNDI be used in my scenario? 

Regards,
Ricardo Carvalho.

Looking for last minute shopping deals? Find them fast with Yahoo! Search.
My scenario is like this:

AudioCodes GW
Two * production machines
Extensions Ranges split between both * production systems.
Mysql 4.1
Asterisk BE 1.2
SER 0.9
Sync and transaction scripts to maintain data inetgrity.

clients can register to either server.  SER is used for routing. If a client cannot get to it's primary server, it is then re-routed to the second server.
This scenario has been up and running for over 1 year now with no issues.

---------------------------------------
From: asterisk-ha-clustering-bounces at lists.digium.com [mailto:asterisk-ha-clustering-bounces at lists.digium.com] On Behalf Of Ricardo Carvalho
Sent: Thursday, January 17, 2008 6:02 AM
To: Asterisk High Availability and Clustering List - Non-CommercialDiscussion
Subject: Re: [asterisk-ha-clustering] Load sharing between two asteriskservers

My scenario is like this:

* one production machine
* one hot standby machine
* MySQL Replication between both servers in Master/Master configuration for CDR and Realtime SIP
* VRRP (running by the keepalived daemon) to share the same IP address which is set in SRV records of the DNS of the domain served by the Asterisk. Since asterisk daemon of both machines binds that virtual IP address, when the hot standby machine assumes production, by that time keepalived daemon starts asterisk automatically in that machine. 

* Since clients registration information isn't shared between servers because it is kept in AstDB and not in the MySQL (which is replicated between those two machines), I made one script that reboots all phones (about 300) that my site have so that they re-register when they go up. But this is a bad solution, the best thing would be to share registration information between both servers. Which one would be the best for me? What would you recommend? I was planning to use DRDB to replicate AstDB registration information but since I read in this thread it is only unidirectional, it already seams not to be so good idea... can and should DUNDI be used in my scenario? 

Regards,
Ricardo Carvalho.

Looking for last minute shopping deals? Find them fast with Yahoo! Search.

      ____________________________________________________________________________________
Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-ha-clustering/attachments/20080117/27259a21/attachment.htm 