[sipX-dev] XPB-892: the initial start / default configuraiton problem
On Wed, 2007-04-04 at 16:23 -0400, Douglas Hubler wrote:
> Paul Mossman wrote:
> > Speaking of the larger sequencing problem, I plan to consider it
> > outside the scope of this feature. I think it is covered under
> > http://track.sipfoundry.org/browse/XPB-892 ?
> yes. this is an independent issue. in fact some percentage of restoring
> configs is meaningless because sipXconfig (driven by the database) will
> regenerate them, but there are files outside it's control and therefore
> it doesn't matter.
>
> P.S. If anyone wants to talk about XPB-892, I'd be happy to discuss
> this, interesting topics include:
> Should servers have a default configuration file?
> Should sipXconfig replace them on startup each time or maybe once ever?
I think that following the initial install, the only processes started
should be the process manager / watchdog (that is, once we've rewritten
them to be the same thing), and sipXconfig. The sipXconfig should be
able to detect that it is being started in a 'fresh install' situation,
and should lead the user through some initial setup and familiarization
steps. Then it should generate the initial configurations and start the
correct set of other processes.
--
Scott Lawrence tel:+1-781-938-5306;ext=162 or sip:slawrence@xxxxxxxxxxx
sipXpbx project coordinator - SIPfoundry http://www.sipfoundry.org/sipX
Chief Technology Officer - Pingtel Corp. http://www.pingtel.com/
