What about something like using Exchange Unified Messaging, and the clustering you can do with that for voicemail? It's not open source, but if you were a heavily Microsoft shop already, it might be something that was withing reach.
Call control could stay with Sipx, and the voicemail records could still point to Exchange. Just a thought. Kurt Siegfried On Mon, Jul 19, 2010 at 3:21 PM, m...@grounded.net <m...@grounded.net> wrote: > There's only one way to find out what might work, I'm going to build a couple > of systems and see what I can come up with. > Sometimes, solutions are found by not over complicating the thinking first, > trying it, then working through the problems. > > What would happen if you had two sipx systems, sharing all of the sipx files, > but only one running sipx, the other with it's sipx services off. > One could monitor for a trigger, and when that came in, would fire up sipx > services, using the same files that the previous system was using. > > Worth a shot and I can always stand to learn anyhow. > > _______________________________________________ > sipx-users mailing list sipx-users@list.sipfoundry.org > 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/ > _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org 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/
