I have it in our Lab. It works well. The question is how it works by the Customer:))
ohh..no problems on the upgrade..the only thing is you must upgrade your SQL Server to service pack 3.
I have some problems right to upgrade a CM 3.1.2c to 3.2.1.
After the upgrade we boot the server but the CM remains with ver 3.1.2c, we are working with the TAC to solve this problem.
Did TAC provide you an solution?
I have the same problem, I upgraded a PUB/SUB, but the SUB remains 3.1(2c). If I look on the pub (http://localhost/ccmadmin) and look at the component versions for both callmamangers they appear to be 3.2(1). If I do this on the sub, I see 3.1(2c) ???????
I have not upgraded my 3.1 box with ata's configured but I assume you might have to delete them and readd them. Since in 3.1 they are 7960's and in 3.2 they are ATA 186 devices. If you have a bunch of them you can just let them auto-register. I did this on my 3.2 cluster without any problems. Did you have another specific concern?
I had trouble getting CM to find ATA devices initially. I loaded the latest version of ATA 186 software on the box and this allowed our CM 3.1.x to recognize the boxes. (Version 212ms). Connected to the 6500 box it does DHCP correctly. Needed to go to the DHCP manager to determine the MAC address to then add it as a 7960 phone. We needed to put these off of 3524 switches also. DHCP didn't work on those though. Needed to give static IP's. Still having a problem of the boxes reregistering w/ CM's and that makes them put off a ring each time. Anyone have help with the reregistering problem or having to issue static IPs on the 3524 boxes?
How did you go back to 3.1(2c)? Did you pull a drive before the upgrade and then go back to the pulled drive? Was it the SQL database with devices and route patterns or just the user database under users -> global directory or both?
Upgraded last weekend, reverting back to 3.1.x this weekend. Mostly just real buggy annoyances with our 7960 phones. While on one line, if another call came in on a different line on the same phone, all options (hold, transfer, endcall) disappear and all you can do is answer the incoming call. This really upset some of our small office attendants, and it was quite annoying for me as well. I also noticed that caller ID, while on another line didn't work. And sometimes only 3 digits out of 4 would be displayed when someone called from another 4-digit extension. Not really major problems, but users don't tolerate even minor problems when it comes to phones.
Anybody else run into this (hold, transfer, endcall disappear on second incoming call)? It happens to us on 7940 and 7960 phones, I tried sending a specific phone back to the P00303010102 load and it still looses the soft keys on the second line. I'd sure hate to revert back to 3.12c just for this.
I'm glad to see others with this problem. I'm surprised I havn't seen more people complaining. I tried the other phone load with 3.2, but it still didn't do everything quite right. Calls coming in to the second line would either not show caller-id, or only show 3 out of 4 digits.
If this remains this way, we'll never be able to upgrade to 3.2!
I think the answer might be "as designed". If you take a look at what is happening, you will notice that the soft keys for the first call do not actually go away, what you are seeing are the soft keys for the second line. Before the second call is actually answered, the only key available is "Answer". The trick is to select the line button for the first call, act on it (Hold, xfer, etc.) then go to the second line and act on it.
Cisco told me the same thing. We are not using call waiting, but rather a second line appearance that the call will forward to if the first line is busy. I had to press the first line twice, not once to get back to the right display. Also, it put the first line on hold for just an instant while I hit the button twice. This was just to much of a hassle for my users to deal with. They were happy with the way it was. Imagine an attendant in a small office answering one number that is coming in on four line appearances. All of the button pushing is ridiculous.
I upgraded a PUB/SUB to 3.2.1 but a failover ends in a 'registration rejected'. I also upgraded my Extended services to 2.2(3a), this should work according to the documents, but when I use extension mobility and I fill in the userID an PIN I get a blank screen with 'Please Sign On' on the top.
Did someone else ran in to this?
I got to the very end of the upgrade and it failed to accept the new SA password for SQL (step 10). It appeared to complete the upgrade, but when I tried to bring CM up, the database was completely gone. I had TAC on the line (#C417413) and they thought given the circumstances the best thing to do would be to reinstall 3.1(2c) then restore the previous backup.
They seemed to think that the SA problem was because CM was moved from a workgroup to a domain after my initial installation and that password restrictions in the domain were somehow interfering with the new SA password. When I did the recovery, I left the CM in the Workgroup to avoid this problem the next time I attempt the upgrade.
So now I have my recovered Publisher server in a Workgroup, and my Subscriber in the Domain. How can I successfully move the Subscriber CM from the domain and into the workgroup without restoring? I tried to simply remove it from the domain and place it in the workgroup, but when I do that SQL will not start.
BTW, I did all of the preliminary steps (service packs, patches, and BIOS upgrades) to upgrading except one. I did not do the step of breaking the mirror and setting the hard drive aside as a recovery precaution. After spending a very long night recovering, I can tell you that that step is one that you should follow, I certainly will on my next attempt.
I have upgraded one of our CM's to 3.2 with no problems. There are some things to be aware of when upgrading. You cannot have 3.2 on one server and 3.1 on another, they will not talk to each other. Also, ICD is not supported in 3.2, support will be added back in a future upgrade. Also, there are some issues with Extension Mobility not working on 3.2.
As for 3.2 and ICD, the details are in the Compatibility Matrix in the 3.2(1) release notes. Something to the effect of requiring a patch for DC Directory and JTAPI - which are not available. Yikes!
For those having the soft key issue.. (on a line and call comes in on another line, only answer is presented)
What happens if you press answer? Does it automatically put the current call on hold the way it does for calls on the same line? or does it answer the new call and drop the existing one?
If you cleck answer the call on line 1 is put on hold and the call is answered. This has changed and all of the operators are very annoyed about this. Can we revert possibly to old phone loads?
It does automatically put the other call on hold, but what if you don't want to put them on hold? What if you're an operator in a small department that wants to transfer the first call, or put the first call on hold, or even end the first call? The only way to do that is to hit the first line button twice. The first hit puts the original caller on hold and the second hit brings them back. Then you can select what you want to do with them, while you still haven't answered the second call coming in. This is very annoying and frustrating for our operators.
I was having the same issue at one of my customers. If you turn off call waiting on the lines all of your options remain and you can handle the first call (transfer, park, etc) before dealing with the second. Let me know if this works for you as well.