> Just keeps on going... I don't understand the comment. If others have been asking about this, then it's obviously something which could be very useful. Why not find a way of doing it. It should not be rocket science considering most any professional version of something or other usually offers full redundancy.
Why not find a way to achieve this. Can't be impossible but it's certainly hard for me since I'm not a developer but I do want to use sipx. Mike On Tue, 19 Jan 2010 11:49:37 -0500, Scott Lawrence wrote: > On Tue, 2010-01-19 at 10:39 -0600, [email protected] wrote: > >>> Not necessarily. Just the services that that node is responsible for. >>> Just >>> because sipXconfig is unavailable, it doesn't mean that everything >>> stops, >>> it just means you can't make changes. >>> >> Ah, now this is something I didn't know. I knew that making changes >> stops but it's never been clear if everything just keeps on going. >> So, while working on the primary node to get it back up for example, >> what happens to the rest of the cluster? Does it continue running on >> it's own until primary is back or does it break down after some time? >> _______________________________________________ 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/
