Raymond Dans wrote: > Damian wrote: > >> To: [email protected] >> Subject: Re: [sipX-dev] 3rd party services >> >> Raymond Dans wrote: >>> >> [...] >> >>> In my particular case, I need the 3rd party service to come up >>> automatically on the master system. It probably wouldn't be >>> acceptable to the Administrator to have to go into the Services and >>> manually add it in order to get his sytem running properly. >>> >> That's easily done by adding the service to one of the >> auto-enabled bundles. Depending on the type of the service >> 'managementBundle' or 'primarySipRouterBundle' might be a good choice. >> D. >> > > Yes I did already have the service in the "managementBundle" but it > still wouldn't start. I noticed though that the Config Version wasn't > set for my service and that could explain why its not started. > In examining "SipxServiceManagerImpl.java", I can see why it isn't > called. Looks like setting of the Config Version is only called for > services in the Database of which mine is not. Is this intentional or a > problem? >
It's a problem: it needs to be changed. We should call it only after we generate config for a service. And of course we should call it for every service with the descriptor not for every service in the DB. Kevin - should we reopen an old JIRA issues or create a new one for that. D. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
