If you compare Andrei's patch for XCF-1098 with what I ended up committing you notice that I ended up committing much simpler version of this feature.
I removed restart persistence (scheduling restarts surviving sipXconfig restart) and status reporting (new columns for devices table, new error messages). I significantly simplified the UI. The only addition is the date/time field that let's you to specify the restart time when generating the profile. By default it's pre-filled with current date/time. I wanted to commit such simple implementation first. It's hard to get all details right (although Andrei did in most cases) and I would not want this to stand in the way of implementing background profile generation. DeviceStatus is a good concept - but it's probably better if such status is mainained by profile manager and not by Phone/Sbc/Gatewat context. The fact that someone scheduled device restart is an interesting data point, but it should not prevent me from regenerating the profile and restarting device immediately. I was toying with various strategies to implement what should happen if you schedule the restart and then change your mind. After conversation with Kevin I decided that the least surprising thing would be to stick with the last decision of the administrator. That is if you enter restart time as 7:05am and later change it to 6:55am we will attempt restart at 6:55. I think that as it's currently implemented the schedule restart is an incremental improvement over 3.10. If we have some time we can get back to the patch and add more functionality. 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
