On Sun, 2011-01-23 at 15:42 +0200, George Niculae wrote: > On Sat, Jan 22, 2011 at 6:31 PM, Kris Buytaert <[email protected]> wrote: > > > > I've just uploaded the initial version of my puppet sipx module to > > github https://github.com/KrisBuytaert/puppet-sip > > > > > > Nice work! > > > > > Stuff that's still missing because I didn't figure out how to do them > > from either the cli or the api > > > > - Setting the Initial Password > > - Creating / configuring roles (eg. disable conference server etc) > > - Add a 2nd node to the setup > > - Send profiles > > > > We'll add JIRA issues to track the requests and try to get them solved > in next release. > Got ID's on those so I can keep an eye on them ?
> > - Restarting services when needed > > (actually even getting visibility on them is something I still haven't > > figure out) > Have you tried bin/sipxproc --state? It will return a list with all > the services and current status. For restarting services use I should rescratch a box and take a closerlook at the output of sipxproc and how puppet could react to them. Whilst on the topic .. google learned me about some German student having worked on Nagios modules for sipx... did any of that work got published ? greetings Kris > bin/sipxproc --restart serviceName where serviceName is one of the > names returned by --state call (e.g. /sipxproc --restart > ConfigServer). --stop and --start are also valid choices. > > George > _______________________________________________ > sipx-dev mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev/ _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
