Scott wrote: > On Mon, 2009-09-21 at 11:20 -0400, Paul Mossman wrote: > > Damian wrote: > > > >> 1. Could we add a CONFIG_URL setting, in the same form as > > > it appears > > > >> in sipxivr.properties? (e.g. > > > configUrl=https://puppy.org:8443) Not > > > >> sure if it would entirely replace CONFIG_HOSTS... > > > > > > I think it's possible? What would that be used for? > > > > Isn't this URL required for a REST call? > > Even if true, I don't think we want to create that > association. If what's needed is a URI for making a REST > call, then that's what we should configure (that is, it > should be more specific).
CONFIG_REST_URI sounds good to me. > How many services need that URI? Do they all use it for the > same thing? IVR at least has it today. Likely there will be more in the future. > > Yes, the running server. You could use this value instead of > > executing `hostname -f`, which I'm told doesn't do what we > expect on > > Suse systems anyway. > > You didn't really answer the question - what needs this, and for what? sipXprovision will write a Polycom 000000000000.cfg file to the FTP root directory. That file will contain the URL to the Jetty servlet that will perform the Polycom auto-provisioning. When URL will be written into the file in the form "http://<FQDN>:<port>/<path>". I'm looking for the best way for sipXprovision to determine the FQDN of the server it runs on. -Paul [email protected] _______________________________________________ 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/
