[Asterisk-Users] Failover question

[Boris Bakchiev]

The registry's are stored in DB.

Just export your database with 'database show'
Schedule it with cron to run every 5 minutes or so.
You can do that with -rx command line switch for asterisk.

Send the file across to other node and pipe it through awk/perl/cut or
whatever you like and import it when you bring the other node up.

You will have to stop and start asterisk I think. 

I think this should work :)



-----Original Message-----
From: asterisk-users-bounces at lists.digium.com
[mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Mohamed A.
Gombolaty
Sent: Thursday, June 30, 2005 10:20 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: [Asterisk-Users] Failover question

Dear All,

I am using Linux-High Availability between two Asterisk servers,
everything is
fine but I do have one problem with this, When a server fails and the
other
assumes the ip address and start asterisk on server 2, the ip phone must
re-register themselves again, otherwise the phones won't ring.

Does anyone have Ideas of how to overcome this.

Thx
MAG

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


This message (and any associated files) is intended only for the use of the individual or entity to which it is addressed and may contain information that is confidential, subject to copyright or constitutes a trade secret. If you are not the intended recipient you are hereby notified that any dissemination, copying or distribution of this message, or files associated with this message, is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and deleting it from your computer. Messages sent to and from us may be monitored... 

Internet communications cannot be guaranteed to be secured or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. Therefore, we do not accept responsibility for any errors or omissions that are present in this message, or any attachment, that have arisen as a result of e-mail transmission. If verification is required, please request a hard-copy version. Any views or opinions presented are solely those of the author and do not necessarily represent those of the company.