I committed some changes (thanks Mircea) to the service restart mechanism. sipXconfig will stop restarting services automatically (that is unless you actually click on a restart button somewhere). Instead, if configuration change requires service restart sipXconfig will change the service status. You can easily identify the services that require restart: they have a different status icon and "Restart Needed" text displayed next to their status text.
In addition, there is a reminder displayed on all pages, It won't go away until admin restarts all affected services. As a reminder: this is the result of the compromise between "let's just do everything automatically" and "let administrator decide when" factions. Let's see how this works. I am pretty sure we could use UI that would list all services that require restart in one place and let admin to schedule restart for them (something similar to the way phone restarts are handled). But before I open any new issues - give it a try and send comments. 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
