On Fri, 2010-01-29 at 14:54 -0500, Fowler, Peter AVAYA (CAR:9D10) wrote: > > - 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 _______________________________________________ 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/
