somewhat related to: http://track.sipfoundry.org/browse/XCF-2842
After I commit it sipXconfig will stop automatically configuring the IP address
of the primary server as a domain alias (really bad thing to do in HA
installation).
There were some problems with generating registrar-config recently, but the
current implementation in sipXconfig will insert the following as
SIP_REGISTRAR_DOMAIN_ALIASES value:
- the list of domain aliases configured by user
- IP address of the server on which registrar is running (different for each
server in the cluster)
- fully qualified hostname of the server on which registrar is running (again:
different for each server)
So if I have 2 servers:
- a.example.com 10.1.1.1
- b.example.com 10.1.1.2
And I configured 'alias1.example.com' as my domain alias I would end up with:
a.example.com:
SIP_REGISTRAR_DOMAIN_ALIASES : alias1.example.com a.example.com 10.1.1.1
b.example.com:
SIP_REGISTRAR_DOMAIN_ALIASES : alias1.example.com b.example.com 10.1.1.2
Kevin tells me that IP address is probably not needed there. But it looks like
it was inherited from the way registrar-config.in was set up (back in the days
we still used it). And I quickly searched the lists and I did not find any
authoritative recommendation.
Does anyone else have an informed opinion?
D.
PS.
[EMAIL PROTECTED] sipXregistry]$ git grep SIP_REGISTRAR_DOMAIN_ALIASES
etc/registrar-config.in:SIP_REGISTRAR_DOMAIN_ALIASES : ${MY_FULL_HOSTNAME}
${MY_IP_ADDR}
src/SipRegistrar.cpp: mConfigDb->get("SIP_REGISTRAR_DOMAIN_ALIASES",
domainAliases);
src/SipRegistrarServer.cpp: pOsConfigDb->get("SIP_REGISTRAR_DOMAIN_ALIASES",
hostAliases);
src/SipRegistrarServer.cpp: OsSysLog::add(FAC_SIP, PRI_INFO,
"SIP_REGISTRAR_DOMAIN_ALIASES : %s",
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
