On Tue, 2010-01-19 at 11:09 -0600, [email protected] wrote:
> >> Might there be some way of having two then, which are kept in sync?
> >> 
> > That would be a wonderfully difficult software engineering problem!
> 
> Why is that? 
> What about using a shared mapped storage for both sipx instances so
> that each can find vm's. Then, a way of syncing up vm notices on the
> two sipx instances so that if a user logs into either, they can get at
> their vm.

And a system of locks so that if one caller is leaving a VM for ext. 123
using system A, and another caller is leaving a VM for ext. 123 using
system B, neither system corrupts the changes to storage that the other
one is making...

The problem is one of a fully distributed and redundant database.

Dale


_______________________________________________
sipx-users mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
sipXecs IP PBX -- http://www.sipfoundry.org/

Reply via email to