g>Disabled</string></valu >>>e>\n\n..." >>> >>>Any ideas on where to look to get to the bottom of this problem? >>> >> Did config set the version number for that component? Config is >> responsible for calling the XML/RPC SetConfigVersion for the >component >> in question before it can be successfully started. > > >Where does to do the check (i.e. in which file is the >information stored?). Perhaps there is something in the tar >file missing. > The actual component has a version in its process xml file (under /usr/share/sipxecs/process.d). SipXconfig, I believe, gets a version number from its properties file (sipxconfig.properties) and should call the XML/RPC SetConfigVersion using its version number for each of the services it will ask to start. Supervisor will then check the version that was set against what was found in the process xml file. If they don't match, you don't get started.
Raymond _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
