Top posting on purpose:
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.
- If sipXivr is the "owner" of the data and it does nothing more than
update the xml file
then a backup will not capture the change.
- as Scott mentioned, we don't necessary need to fold these sort of
values into validusers.xml
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.
Peter
> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]] On Behalf Of
> Mossman, Paul AVAYA (CAR:9D30)
> Sent: Friday, January 29, 2010 1:16 PM
> To: Lawrence, Scott AVAYA (BL60:9D30)
> Cc: [email protected]
> Subject: Re: [sipX-dev] Regarding Mailbox preferences -
> active greeting insipXconfig / sipXIvr (XX-6702)
>
> Scott wrote:
> ...
> > > > I would prefer if sipXconfig provided the REST service
> > and sipXivr
> > > > be its consumer. SipXconfig can then write this setting
> out to a
> > > > config file (e.g. validusers.xml), from where sipXivr
> can pick it
> > > > up. The main advantage of this is, it would allow users to make
> > > > configuration changes when sipXivr is not running. And, the
> > > > disadvantage being, no configuration changes are possible when
> > > > sipXconfig is not running - but I think that is an acceptable
> > > > shortcoming.
> > >
> > > +1
> > >
> > > Configuration data should be mastered in sipXconfig.
> >
> > Manage it in sipXconfig if you want to, but that does not
> imply that
> > it should be a part of validusers.xml - that thing is
> turning into a
> > grab bag.
>
> Why not put it in validusers.xml? That seems like the
> logical place for it.
>
>
> -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/
>
_______________________________________________
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/
