Hi all, I would like to summarize what we discussed with Kevin and Scott about the configuration stamp for sipx services ( http://track.sipfoundry.org/browse/XCF-2612 ). SipXsupervisor needs the configuration stamp value in order to compare it to the actual service version. If they are both the same, the service can be started. Otherwise the state of the service will be set to "ConfigurationVersionMismatch". SipXconfig should be responsible for sending the configuration stamp value via XML-RPC layer to SipXsupervisor. This should happen whenever the configuration for a specific service changes (and gets replicated) or when a new service is added for a specific host. As far as we now, the configuration of a service can get changed at application's startup or from the System/Server/Services page (as per user action). In conclusion the stamp will be passed to sipXsupervisor in the above use cases.
Is this information correct and complete ? Will this work in a distributed environment ? Please share your opinion on this matter. Thanks, Bogdan _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
