> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Lawrence, Scott (BL60:9D30) > Sent: Tuesday, September 23, 2008 11:45 PM > To: sipx-dev > Subject: [sipX-dev] Alarm server url host part > > > In the template for the domain-config file: > sipXconfig/neoconf/etc/commserver/domain-config.vm > > SIP_DOMAIN_NAME : ${domain.Name} > SIP_REALM : ${realm} > SHARED_SECRET : ${domain.SharedSecret} > DEFAULT_LANGUAGE : $language > ALARM_SERVER_URL : https://${domain.Name}:8092 > > ...if I read this correctly, the URL for the alarm server > will use the SIP domain name as the host portion. This will > be correct only when the SIP domain name is also the host > name of the master server - or am I missing something? >
The Alarm Server runs on each box in a cluster, not just on the master. It is true that it won't work if the domain is not the host name of the server in question. In neoconf/etc/sipxconfig.properties.in it is set to https://${MY_FULL_HOSTNAME}:8092. Is there a way of using the full hostname in domain-config.vm? I confess that I do not understand how these templates are created and what the relation is between domain-config.vm and sipxconfig.properties.in. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
