> -----Original Message----- > From: Lawrence, Scott (BL60:9D30) > Sent: Tuesday, October 28, 2008 3:07 PM > To: Beeton, Carolyn (CAR:9D60) > Cc: Spitzer, Andy (BL60:9D30); [email protected] > Subject: Re: [sipX-dev] SUPERVISOR_HOST not defined in > sipxsupervisor-config > > Carolyn is mostly right - the problem is that the directives > and locations changed and regenerating domain-config will help. > > The controlling directives moved from sipxsupervisor-config to > domain-config: > > SUPERVISOR_PORT (was SIP_WATCHDOG_XMLRPC_PORT) > CONFIG_HOSTS (was SIP_WATCHDOG_XMLRPC_PEERS) > > The SUPERVISOR_HOST directive in sipxsupervisor-config is > read, but is not required. It specifies the host that the > supervisor is running on and that host is always added to the > internal list of valid peers (CONFIG_HOSTS). >
right - I forgot there is an issue open asking for sipxsupervisor-config to be generated. The chicken and egg problem is that it can't be generated if sipxsupervisor refuses the request because it isn't in the list of valid peers. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
