Until 3.10 I was not aware of any odd numbers being considered "stable". Maybe on the way to 3.6.8 it become 3.7 (dev) to actually become 3.8 (stable). There might have been a 3.6ISO, then updates to 3.6.. Someone might be able to provide more guidance on this. Who is the desginated sipx historian?
>>> Melcon Moraes <[email protected]> 05/08/09 6:52 AM >>> I thought that 3.6.7 was a stable release, as in major version 3, minor 6 and update 7. From which version on this rule applies? - MM On Fri, May 8, 2009 at 4:12 AM, Tony Graziano <[email protected]>wrote: > I'm not sure I would agree. > > 3.6.7 is an odd release, and probably was never a "stable" release. > 3.6.0 was. And while the ISO isn't on the site, install Centos 4 and > adding the repo and installing 3.6.0 are very attainable now. > > If you "stick" with an unstable version, (typically odd number revisions > are considered unstable), I can see this sort of thing happening. > > I can't answer if there was a 3.6.7 ISO. > > Multi-day effort? I did ours from 3.10.3 to 4.0 in under 2 hours once I > had the ISO burned. Obviously that depends on the number of users/phones > (15). > > >>> "Mel Beckman" <[email protected]> 05/08/09 3:06 AM >>> > Yikes! That would be a multi-day effort. Surely the ISOs are being > archived somewhere, if only for system recovery reasons! This seems a > giant hole in the viability os sipX for business if previous image > versions simply evaporate! > > -mel > > > On 5/7/09 11:57 PM, "Tony Graziano" <[email protected]> > wrote: > > You could always install Centos 4 and install 3.6.0 from RPM, but > don't > know how you would get to 3.6.7, and even if you did, the backup files > are probably not compatible still. Unless there is a way to find the > RPM's for 3.6.7 to upgrade or install. > > At the same time, you could install a stable version (4.0) from ISO, > then do the following (we've done this from 3.10.3 backup which is not > compatible with 4.0 restore). > > 1. Load the new stable version. > 2. Create the users/lines (do not fill in voice mail options, etc.). > 3. Copy the backup to the new system in a separate directory and unzip > it, then copy/paste the voicemail folders over the new one, which > might > pull in the voicemail to email settings, and user recordings. Trying > it > first with a single user would be suggested, since that structure > might > have changed as well. OR > > Create a CSV file with the phones, users, etc., and import the phones > and users at once, then copy the contents of the user voicemail store > one by one from the unzipped backup. > > You will still have to create the dial plan, gateways, etc. by hand. > > Perhaps Scott or someone can determine if the 3.6.7 RPM's live > somewhere > that can be posted? > > >>> "Mel Beckman" <[email protected]> 05/07/09 11:54 PM >>> > > I have a client who’s 3.6.7 sipX box died. I’ve built a new box and > tried restoring to 3.10.2, but the restore fails with “internal > error”, which I suspect means the backup files are not compatible. To > ensure fidelity with the client’s current config I’d ideally want to > install 3.6.7 anyway. But I can’t find an archive of old ISOs. Does > anyone have the Centos-based 3.6.7 ISO? > > -mel > _______________________________________________ > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users > _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
