I wanted to take a moment to explain the latest config.defs changes (related to sip realm and domain-config) in more detail.
This was the world as it existed before 3.11.11: The config.defs file provides params for SIPXCHANGE_REALM and SIPXCHANGE_DOMAIN_NAME. They are defined as follows: SIPXCHANGE_DOMAIN_NAME=`hostname -f` SIPXCHANGE_REALM=`hostname -d` sipXconfig does not store the realm anywhere. Rather, the realm is injected from the config.defs file every time that sipXconfig runs. If someone modifies the config.defs file to change the realm, sipXconfig will pick up the new realm when it restarts. This causes authentication problems, but is still possible to do. Fast forward to the present. sipx-setup now creates an initial domain-config file with values for both domain name and sip realm. These are by default set to the same value. The default is `hostname -f`, though it can be overridden when sipx-setup is run. Either way, the values for the two params are the same. As of svn r14684, sipXconfig no longer reads the realm or domain from config.defs. This is another step in the process to get rid of config.defs. Instead, sipXconfig reads the domain and realm from the domain-config file. In the case of an upgrade from 3.10, this file was written by sipXconfig. In the case of a fresh install, this was written by sipx-setup. Listed below are the 4 cases I have identified, and how sipXconfig will work (or not work) in each case: 1) 3.10 to 4.0 upgrade: sipXconfig reads the domain-config file and intializes the realm appropriately. It doesn't matter how the realm was defined in config.defs (`hostname -d`, `hostname -f`, "foo", etc), sipXconfig will just take the one that it finds in domain-config. This should work and will not cause any authentication issues. 2) Fresh install of 4.0 sipx-setup generates an initial domain-config file. sipXconfig reads this file and parses the realm. As with case (1), this should work and not cause any issues. 3) 3.11.x to 3.11.y upgrade - domain-config contains correct realm This should be the majority of intra-3.11 upgrades. Woof! ran into this yesterday and all he had to do was force a sipXconfig first-run (sipxconfig.sh --first-run). 4) 3.11.x to 3.11.y upgrade - domain-config and config.defs don't agree This one will cause issues. Specifically, you won't be able to log in as any user to sipXconfig. There is an easy way around this... make domain-config agree with config.defs manually, run sipxconfig.sh --first-run, then start sipXconfig and all should be well. However, this is probably going to cause confusion for people when they can't log in. I am still testing and trying to find other cases, but I think these four are the major ones. Basically things work fine most of the time (and as far as I can tell, all the time in non-developer cases). Hope this helps, Kevin _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
