On Thu, 2008-12-18 at 17:16 -0500, Damian Krzeminski wrote: > I was playing with my configuration trying to reproduce various services > problems. I realized that I cannot stop services which are in > "ConfigurationFailed" or "ResourceRequiredState". > > I tried using both sipXconfig and sipxproc and I tried SIPXProxy and > SipxBridge. When I issue "stop" command (as in 'sipxproc --stop SIPXPRoxy') > all I can achieve is the process flipping for a while to 'Failed' state and > then back to its original error state. > > Is this what others see as well? > > I am thinking that admin should be able to stop/disable services that for > some reason are not running correctly.
That seems reasonable. Please file a sipXecs issue with a snapshot from your test if you can. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
