Peter wrote: > After talking the Arjun and Paul here is a summary of the key points > - both sipXconfig and sipXivr can update (in the > abstract/logical sense), > the Active Greeting property (on a user basis) > - currently sipXivr (physically) does this by updating the > local copy of > mailboxprefs.xml > - sipXivr does this by updating the value in the postgres > database but it currently > does not regenerate the mailboxprefs.xml file.
I confirmed with Peter, he did indeed mean: "- *** sipXconfig *** does this by updating the value in the postgres database but it currently does not regenerate the mailboxprefs.xml file." > So to me the conclusion is, > > - sipXconfig owns the data: it updates the postgres > database and re-generates the mailboxprefs.xml file > for the user in question. > - sipXivr reads its local copy of the file and so if the > WAN if down, things still work > - when the user changes the setting via the TUI (sipXivr) > it should invoke a sipXconfig REST API > (it already invokes a sipXconfig REST API when it wants > to change the PIN and when CallPilot > wants to change the attendant URI) > > Hopefully agreement? If so I would change sipXivr to adhere > to the above and remove the REST APIs that Woof added. +1 -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/
