I wrote: > Woof wrote: > ... > > I'd say that the status of prompts, greetings, etc. should > NOT be in > > the database, as they need the recordings to go with them, and the > > recordings are not in the DB. If you backup the DB (but not the > > mailstore) and a user had set the "use the out-of-office greeting", > > but the user had recorded a custom out-of-office greeting--if you > > restore the DB but not the recording the mailbox is in a > more messed > > up state than not. > > That is a good point. One which only just sunk in for me. > > I don't like the thought of sipXconfig not mastering all the > systems data. But this is a very practical argument against > the direction we were going to take. I'm willing to re-visit > our decision. Arjun? > Peter?
I've slept on it, and I'm leaning back towards our original decision: sipXconfig should master all of the system's Configuration. Woof your use case is valid, but I think the problem is with the Backup/Restore categorization of 'Configuration' vs. 'Voicemail' data. VM, ACD, and MOH prompts/recordings are Configuration. Yes they are audio files played by FreeSWITCH, but that does not make them Voicemail. They are unseparable from the Configuration settings relating to their use, and are themselves Configuration data. Voicemail data is the collection of messages deposited by callers in user mailboxes. (Also other meta-data: heard/unheard, folder, subject.) You should be able to entirely recover a system's Configuration without having to restore a Voicemail archive. Thoughts? -Paul [email protected] _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
