CM 6.0 to 6.1.3 - any known issues

[bigchiefdan]

Its me again. We are going to upgrade to 6.0(1b)tonight, then 6.1(2)& 6.1(3) this weekend in an attempt to resolve all the weired things that keep happening.

For example, ever x number days the codec gets changed in my regions on CM. This messses up the MOH and causes me to just have TOH. I did get the date issue resolved by waiting a few days to change it again.

My question to anyone is do you have any suggestions or comments on what I might be getting into with 6.1(3)?
Cisco is saying this will resolve most of my issues as they cannot find any reason I am having problems.

 

[iptuser]

We too are upgrading from 6.0 but only to 6.1.2.xxx as suggested by our SI. Let me know if you have any issues? thanks

 

[pndscm]

I have several customer running either 6.1.2 and 6.1.3. I have seen no huge problems with either version. I am installing a system next week and it will 6.1.3. Cisco always tells you to upgrade to the latest greatest before they'll dig too deep. Usually they are right. I upgrade first then call them.

 

[iptuser]

I`ve upgraded in our lab on a flat network from 6.0.1 to 6.1.2.xxxx - all ok however if I try to switch back to 6.0.1 , the phones downgrade themselves as the phone load on 6.1.2 load is higher then 6.0.1- this is successful and is completed however the phones are struck in registering - any ideas. I` going to do the upgrade again on another 6.0.1 and try the switch back again

 

[bigchiefdan]

iptuser (TechnicalUser) 5 Feb 09 12:09
We too are upgrading from 6.0 but only to 6.1.2.xxx as suggested by our SI. Let me know if you have any issues? thanks "
The update last night failed about 40 minutes into it. Cisco is trying to figure somthing out. I hope to try again tonight. We have been on 6.0 for a year now and cannot go a week without something acting up.
Will update you then on my experience, however I have a sneaky feeling that for the duration of my ownership of the call manager here - it will be unique.

 

[iptuser]

I just upgraded our lab again from 6.0.1 to 6.12.1132 and agan if I switch back to the older version the handset just show registering even if I stop , restart dbreplication

 

[bigchiefdan]

Good Morning,
After several attempts (failed that is) we tried upgrading directly to 6.1.2. It worked great. Then on up to 6.1.3, again piece of cake.
Minor issue so far is the licensing, I had 30 more units loaded and available prior to the upgrades.

One thing I have noticed:
When a call is coming in to extension 8501, 8502, 8503, or 8504 on the last ring it will appear on the other 3 phones that a transfer is taking place. An example would be 4452 > 8502 being displayed on 8501, 8503, & 8504.

Can somone enlighten me as to what this is? The only commonality I can think of is all these extensions are in the same call pickup group (seldom used).

 

[iptuser]

Glad to hear it however we still have the switch-version error from 6.1.2 to 6.0.1 out with Cisco TAC now

 

[pndscm]

Are they built into a Hunt Group possibly?