Paul Mossman wrote: > > Damian wrote: >> Paul Mossman wrote: >>> Hi all, >>> >>> I am unable to register any SIP UAs in my main stream development >>> environment (revision 14083.) This seems to be because the >>> Www-Authenticate: header in the 401 Unauthorized responses >> contain the >>> wrong realm. It should be "bcmdesk7199.ca.nortel.com" but I am >>> instead seeing "ca.nortel.com", so the follow-up register with >>> Authorization header of course fails. >>> >>> I initially ran sudo sipx-setup to set-up the SIP Domain, but upon >>> looking into this problem I found that my domain-config contained >>> "SIP_REALM : ca.nortel.com". >>> >>> I have a number of times re-run sudo sipx-setup to change the >>> SIP_REALM to bcmdesk7199.ca.nortel.com. When I start sipX back up >>> again though I find that sometimes the SIP_REALM gets set back to >>> ca.nortel.com? In both cases though the 401 Unauthorized responses >>> continue to have the wrong realm. >>> >>> I've confirmed that the sipXconfig System->Domain->Domain >> Name setting >>> is indeed bcmdesk7199.ca.nortel.com. >>> >>> I've tried running "sipxconfig.sh --database drop create" and/or >>> "sipxconfig.sh --first-run" before starting sipX. But neither of >>> these work, the 401 Unauthorized responses continue to have >> the wrong realm. > >> I strongly suspect that sipXconfig and sipx-setup do not >> agree on initial value for domain name and authorization realm. >> >> sipXconfig is (and always was) reading those values initially >> from config.defs (through the sipxonfig.properties.in). I >> think that sipx-setup asks the user and writes them to >> domain-config. However the initial version of domain-config >> does not last long: it gets overwritten pretty much every >> time you start sipXconfig. >> >> We are slowly but surely dropping all references to >> config.defs but in some cases we get out of sync. >> See: >> http://track.sipfoundry.org/browse/XCF-2809 >> >> I have to admit that the emergence of domain-config >> generating sipx-setup took me by surprise. I am not a big fan >> of a solution in which sipXconfig has to read the same file >> that it needs to generate later, but it's doable. >> >> We can make make sipXconfig to read domain and realm from >> domain-config, save it to DB and generates a new version of it... > > Is there a JIRA for this? >
Yup - the one that I mentioned above. I added a specific comment and reference to this post. > >> The quick workaround is: fix your config.defs. Things should >> calm down. > > I removed my installation directory and re-built from scratch. > > Yes as you suggested the config.defs had a SIPXCHANGE_REALM of `hostname > -d` (ca.nortel.com). I manually changed it to `hostname -f` > (bcmdesk7199.ca.nortel.com) and it works now. > > BTW: I am assuming that sipx-setup is only run once and only on a fresh, unconfigured system - right? Otherwise if people change the realm or domain name sipXconfig is still going to get back to the values kept in the database as soon as it starts. Domain initialization happens only once. D. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
