On Mon, 2008-08-18 at 11:52 +0800, Jeremy A wrote: > Even if you can get the addresses bound correctly I guess that the > real problem will be how to create the databases and configuration > files per instance. > > However, perhaps that could be sorted by creating different chroot > environments for each instance?
Hmmm, I've never thought of that. But chroot'ing gets around the fact that the various executables have compiled-in file paths. Of course, you have to configure each sipX to use a different set of ports. But I think that all port usages are properly driven by the config files. The difficulty is running sipXconfig, Postgres, and Apache separately for each sipX, since Postgres and Apache use ports as well. They're probably configurable, though. Dale _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
