On Thu, Oct 11, 2012 at 5:16 AM, George Niculae <[email protected]> wrote: > On Thu, Oct 11, 2012 at 12:05 PM, Douglas Hubler <[email protected]> wrote: >> On Thu, Oct 11, 2012 at 3:58 AM, George Niculae <[email protected]> wrote: >>> please send profiles to server after updating to latest 4.6 RPMs - >>> there was a change in conferences records so they need to be >>> regenerated >> >> George, >> When sipxconfig restarts, it regenerates profiles but does not rebuild >> mongo tables. just checking, is the fix in regenerating mongo tables? > > Nope, that was not included yet. We should add the mechanism to > regenerate mongo tables on sipxconfig restart only when new patch that > needs this.
Ok, so if i understand you correctly : your fix do require regenerating mongo data therefore you ask folks to send server profiles. That's fine, I was just making sure you (and other developers) understood that if any code change only requires that config files are regenerated, then there's nothing you have to do. restarting sipxconfig regenerates all config files. George and for other's sake, we could automate regenerating mongo data through SetupListener interface, but then the code to check if this has been done will live in codebase forever. We'll reserve that sort of option for after 4.6.0 is released. _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
