Dale opened an issue yesterday: http://track.sipfoundry.org/browse/XCF-2909
Since sipXecs configuration file management is drastically different in mainline compared to what it was in 3.10 I thought that it's a good opportunity to talk about it once more and see if we have other/better ideas on collecting server data. sipXconfig in mainline generates all configuration files for all the servers and pushes them through XML/RPC interface provided by sipXsupervisor. Some of the configuration files require IP address, and sipXconfig (after recent changes - see http://track.sipfoundry.org/browse/XCF-2617) should fill it in correctly. That change takes sipXecs one more step away from config.defs and configuration preprocessor. Calculating IP address of the server using get_def_addr does not work any more. Instead Edit Server page collects IP address of each server. The drawback is that all IP address changes now require that you change those addresses in sipXconfig UI (which is what Dale points out in XCF-2909). I do not think it's an ideal solution, but it seemed to me that asking admin to enter IP address of the server was the only option. We cannot run DNS query since sipXconfig data is going to be used to generate DNS configuration. All we could do is to add configuration tests that would verify if what we know about DNS names and IP addresses still reflects the reality. How does that sound? Better ideas welcomed... 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
