Thank you! That was the tip I needed to untangle this. The issue ended up being that sipxconfig *was* regenerating the files after a --first-run, however 'sipxecs-setup' was groping around in /etc/sysconfig/network-scripts/ifcfg-eth0 (even though eth0 was not up or even present from the kernels point of view) and finding the old IP address then using that to fill in sipxconfig-netif which was then used to fill in all the other templates with the bad IP.
-Eric Varsanyi On Jan 15, 2010, at 7:25 PM, Arjun Nair wrote: > > On the "Servers" page, there is a "Send Profile" button, that will > re-generate and replicate the config files. > > Arjun _______________________________________________ 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/
