We are told that to avoid buggy, PRI related problems (and possibly other issues), we should upgrade the NVRAM to release 2 (because it is inherently defective).
The problem is, so many people have had issues losing all of their programming when performing NVRAM upgrades. See threads 799-806418 and 799-772357 (among others) for the story. Unfortunately, it looks to be a highly risky procedure. Nortel doesn't seem to be aware of how much pain is caused when people have to scramble for new keycodes and/or spend countless hours reprogramming large systems while spinning damage control with the customer.
Does anybody have a PROVEN procedure to follow when upgrading the NVRAM on a Norstar?? Should we use an upgrade tool for this?
Once the NVRAM upgrade is out of the way, it would seem possible that the software upgrades should then go smoother....
The problem is, so many people have had issues losing all of their programming when performing NVRAM upgrades. See threads 799-806418 and 799-772357 (among others) for the story. Unfortunately, it looks to be a highly risky procedure. Nortel doesn't seem to be aware of how much pain is caused when people have to scramble for new keycodes and/or spend countless hours reprogramming large systems while spinning damage control with the customer.
Does anybody have a PROVEN procedure to follow when upgrading the NVRAM on a Norstar?? Should we use an upgrade tool for this?
Once the NVRAM upgrade is out of the way, it would seem possible that the software upgrades should then go smoother....
