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/
