This is correct, astdb isn't stored in a database and essentially your scenario with astdb file being shared won't work or will be highly unreliable. I am almost sure there was a patch in circulation, alas I didn't find it in the bug tracker.


On 12/1/05, Bruce Ferrell <[EMAIL PROTECTED]> wrote:
Matt Riddell wrote:
> dashy dude wrote:
>
>>Dear All
>>I am trying to build a high availability cluster of
>>asterisk.
>>I am using RedHat cluster management suit on
>>Enterprise edition AS3
>>
>>Origianally, astdb was located on native hard disk of
>>each server.
>>All my end points are configured for Reinvite=Yes
>>
>>Everrything was working fine and if active server is
>>rebooted, the standby would take over and the ongoing
>>calls will continue without any problem.
>>
>>But this had a problem that the astdb file is not
>>updated with latest end-point information and phones
>>dont get a call untill they re register.
>>
>>To avoid this, I moved the astdb file on the shared
>>storage and created sym links from individual servers.
>>Now, when the active server is rebooted, all the
>>active calls are dropped.
>>
>>Please help me in resolving this.
>
>
> Why don't you use Asterisk RealTime?
>
correct if I'm wrong (frequently) but the call state isn't stored in the
realtime db is it?

linux-ha uses a form of shared disk called DRBD that might solve this if
you forced the astdb onto that.  Only one node of the cluster is
currently allowed to write to astdb on that though.

Just a thought
_______________________________________________
--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