As reported in XECS-2133, we need to ensure that sipXconfig gets enabled, on the master (or on the config server host?), on upgrade from pre-4.0 loads. New loads currently enable sipXconfig as part of the sipx-setup scripts, and force its version to match the software in the sipxpbx init.d script (these commands are qualified by "TEMPORARY" markers).
Questions: - what was expected to replace the TEMPORARY WORKAROUND in sipxpbx? - would it not make sense to do the enabling and version setting in the same place, in the sipxpbx startup script? Then it would be guaranteed to run, upgrade or not - or should the startup script detect the upgrade (by checking config file versions against software version) and do the version setting/enabling only then (I don't think there is any other upgrade to be done at this level: sipXconfig will take care of its databases once it gets started) Carolyn
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
