Woof!
On Tue, 28 Oct 2008 13:16:29 -0400, Beeton, Carolyn (CAR:9D60)
<[EMAIL PROTECTED]> wrote:
> Can you check whether your
> domain-config contains SUPERVISOR_PORT and CONFIG_HOST?
Process to get out of chicken/egg mode where sipxconfig cannot write the
config file needed to get sipxsupervisor to accept the config file!
1. Stop system (sudo etc/init.d/sipxpbx stop)
2. Hand edit etc/domain-config. Add:
SUPERVISOR_PORT : 8092
CONFIG_HOSTS : {fully qualified host name of this machine}
3. Tell sipxconfig to regenerate EVERYTHING on the next restart:
bin/sipxconfig.sh --database first-run
3. restart system (sudo etc/init.d/sipxpbx start)
4. Log in as superadmin to sipxconfig WebUI. Navigate to servers:{server
name}:configure
Fill in the IP address (this information was lost in update translation,
and now needs to be added by hand or sipXproxy will not start).
--Woof!
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
