Damian wrote: ... > > There is one alternative to the above, and we should be using it a > > little more than we are - if the configuration item is relevant to > > anything (or many things) in the domain, then that item > should go in > > the domain-config, and your service should expect to find > it there. > > The domain-config is replicated to all systems in the cluster. > > > > > > Sure. But please remember that changing domain-config > requires that all the services on all servers in the cluster > are restarted. > Use domain-config for truly common items that do not change often.
Some questions on domain-config... 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... 2. Could we add a HOSTNAME setting? Basically 'hostname -f' on the server. 3. Why both SIP_DOMAIN_NAME and SIP_REALM? (In the velocity template these are ${domain.name} and ${domain.sipRealm}.) Along these lines, my new feature be writing a file into %{phonedir}/profile/tftproot on occasion. Should it be doing this with replication? Or will I just introduce the restriction that this service must run on the master server? Thanks. -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/
