On Tue, 2008-09-23 at 12:49 +0000, Scott Lawrence wrote: > On Tue, 2008-09-23 at 07:43 -0400, Joseph Attardi wrote: > > Ananda Teertha wrote: > > > According to XCF-2441 <http://track.sipfoundry.org/browse/XCF-2441> and > > > XCF-2682 <http://track.sipfoundry.org/browse/XCF-2682> this is > > > intentional. > > > > Anand is correct. We are transitioning away from the *-config.in files > > in favor of a more centralized solution. Once the transition is > > finished, sipXconfig will generate all configuration files. > > Probably it would be best for the test infrastructure to transition to > using the sipXconfig SOAP interfaces (which may need to be enhanced) to > do things like change log levels (and add users, and any other > configuration change they want to make). > >
It would be trivial to add media server logging config support to sipXconfig. Everything is already in place, we just need to create a page to show the value. However, for the time being, it is still possible to change the log level and have that change maintained across system restarts. For any service, you can modify the template file that we are using to generate the config. In the case of media server, this file is etc/sipxpbx/sipxvxml/mediaserver-config.vm Please note that any changes made in these .vm files are not preserved across upgrades. This is not a supported means of configuring sipX. Kevin _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
