I imagine it's because the upgrades were written to rewrite config files from its direct descendant, rather than taking into account other versions before them, which may have had their own changes prior. Supporting multiple version upgrades, especially for such a rapidly evolving product, is very difficult to do.
As a matter of couse, I never skip a version during upgrades of any software, just to avoid situations such as yours. The rest of your questions fall in line once the first is answered above. You would realize significant savings in time to just recover your old vm guest, and upgrade it as recommended. The procedure should take less than an hour to bounce up the two two versions. On Tue, Aug 23, 2011 at 2:48 PM, ITNC Support <[email protected]> wrote: > > Content-Type: text/plain; > charset="utf-8" > Content-Transfer-Encoding: 8bit > Organization: SipXecs Forum > X-FUDforum: 08063afcdd00a6e76393c5b9527381e8 <62824> > Message-ID: <[email protected]> > > > > It is our understanding that upgrading sipxecs should be > done in a linear fashion in order to avoid problems with > voicemail and other configurations but can anyone explain > the reasoning behind this. Are changes written to the config > files during the upgrade or is it more related to a change > in file types? If changes are made to the config files > during upgrade are these changes documented somewhere? I am > just trying to get an idea of why the upgrade must be > linear. Thanks in advanced. > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ >
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
