3300 7.0.21.4 upgrade problems

[MitelInMyBlood]

In recent days we've put 7.0.21.4 on so far a total of 3 machines, all with resulting issues post-upgrade.

Tonight upgrading a site from 7.0.9.5 to 7.0.21.4 we discovered afterwards that several CLOS options had changed. Notably Multiline set Music went back to "NO" and the biggie, Public Network Access Via DPNSS went to "NO" - That one will bite you.

These anomalies have not occurred in every CLOS across the board, but rather at random. I don't know what else in CLOS has cratered, waiting now on the results of a file compare with the prior database. (Data Restore log file was clean)

On another site last week, 1st 7.0.21.4 we did, the voice mail pager alert or outcall to cell phone would not work unless we set the VM CLOS to have an account code length that matched the digit length of the extension, i.e., 4 in this case. Apparently PS knows about this one.

 

[MitelInMyBlood]

After further review it appears that most, but strangely not all of my Classes of Svc have gone back to factory default settings. DBMS check shows no errors.

 

[bearvalley]

This is very worrying!

 

[TheMitelGuy]

What happens when you restore your database? Are you still in good standing?

 

[MitelInMyBlood]

We're OK

Found the problem this evening. After reviewing the log files from the upgrade (everyone keeps these, right?) I discovered that the data restore kicked out several of my Class Of Service forms for "invalid data".

The plot thickens. The upgrade was done on a separate 3300 (not the one where the data save was from) and the problem was the MiTAI/TAPI option was not selected in the License/Options form of the transient spare 3300, so every class of svc which had the HCI/Tapi options selected failed to restore and thus went back to defaults. Yup, got in a hurry and got caught. >>sheepish grin<<

Moral of this story, no matter how many of these you do, none of them are ever alike. Just when you think you finally have it mastered, the machine will outsmart you and prove you dead wrong every time.

 

[TheMitelGuy]

The Moral of my story; "It's Mitel, it has to work!"

Watch that one bit me in the a%%

 

[andy4uk]

I have upgraded a few system to 7.0.21.4, no problems with the class of service.

However i have dicovered that there's a bug, which is on the 5207 handsets - the bug being with the call history button, when you have a missed call, the button will light up but when you select the button it has no number there, if you press the * key the ext will still call the number.

So somewhere the number must be held, just doesn't show in the screen of the phone?

 

[MitelInMyBlood]

Lots of fun being out here on the bleeding edge, huh?

 

[dnsincomminc]

Anyone running 7.0.21.4!!!! You need to install the 7.0.21.5 patch immediately. I recently upgraded our office switch to 7.0.21.4 and was having a problem with the 5430 sets. I contacted Tech Support and they said there is an issue in the .4 version that will cause all backups and subsequent restores to fail. The patch can be downloaded from Mitel Online and is pretty easy to install. A reboot will be required but a backup before hand will not.

Dan Schollian

http://www.incomminc.com

 

[TheMitelGuy]

I put .21.4 and then .21.5 on the ICP last night and running fine.

 

[dnsincomminc]

I haven’t had any issues with the .5 version either, but I know a lot of people are upgrading to the .4 and not installing the patch because they don’t know about it. You would think that Mitel would send out a notification to all dealers. I found out by contacting TSN. Just glad nothing got corrupted.

Dan Schollian

http://www.incomminc.com

 

[MitelInMyBlood]

This 'bleeding edge' stuff is getting a little old. An upgrade patch means another outage. Another outage means going back to management again to get dispensation to do it again, all of which is starting to become high profile with unwanted attention to what is starting to be perceived as an unstable product. We've already gone to management twice in the last 30 days to put on two different loads of code

Is Mitel starting to conduct their CI trials in the retail channel? I don't remember volunteering.

Slow down guys... Just because Cisco releases 'patch of the week' doesn't mean it's a good idea. Lets spend a little more time getting it right and a little less effort racing new features out the door, lest we alienate the customer.