Dale Worley wrote: > On Wed, 2008-05-14 at 14:49 -0400, Damian Krzeminski wrote: >> You can modify etc/sipxpbx/sipxproxy/sipXproxy-config.vm >> It should not be harder then modifying the .in file > > I expect it to be significantly harder than modifying the .in file, for > any but the simplest usage. It seems to make no allowances for > differences between hosts, and doesn't seem to allow a clean way to > record a canned configuration. (I'm assuming you are already set to > document this is the Wiki.) > > Dale > >
If changing the .vm files and using backup/restore for "canned" configuration is not sufficient, maybe we should add an option to suppress sipXconfig config file replication. After all services are free to maintain alternative ways of generating their configuration files. I can imagine a set of tools based on configpp or its successor that has all the properties you ask for. As a matter of fact I do not see why you could not continue using configpp and friends for that. The only change that we would all have to agree upon is that config.in to config translation does not happen automatically every time the services start, but is performed by an independent script instead. It's true that there are no provision for arbitrary differences between distributed hosts configuration because arbitrary differences should be treated as errors during normal system usage. All other differences should be resolved automatically by sipXconfig. D. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
