[cisco-voip] Unity Connection upgrade

[Bill Talley]

No.  They only had around 150 old message total but none went to undeliverable.  I'll go back in and check the log file to see what may have happened.  It may have been due to some error on my part.

I was able to pull messages out of the migration export folder and deliver them to the client on a cd.  They're clearly defined as to who they're addressed to so client was able to redistribute them.  Granted, most system will probably have a higher volume of messages than that so it may not be as simple as providing a cd.



From: Ed Leatherman
Sent: Fri 7/25/2008 8:59 AM
To: Bill Talley
Cc: cisco voip
Subject: Re: [cisco-voip] Unity Connection upgrade


Thanks for pointing out the subscriber templates, I would have missed that.

Time to spin up a UC 1.2 in the lab and test out the message import.. That doesn't give me a warm and fuzzy feeling that people have had trouble importing voice messages. Did it end up sending them to the Undeliverable messages account?


On Fri, Jul 25, 2008 at 9:54 AM, Bill Talley <billt at aos5.com> wrote:

I know you're asking about gotchas, but I threw in an extra comment or two as well.

Evidently OpenSSH is the only TAC supported SSH server for the migration.  I've heard of issues when using other ssh servers.

I don't recall if this was clear in the training video from ciscounitytools.com (I think it was), but if you have multiple subscriber templates, make sure you create them on the new server prior to importing subscribers, otherwise you'll have to bulk edit the subscribers afterwards.  You'll also have to import users assigned to each template separately, so you'll have to take the source csv file from the migration tool and parse out users associated with each template into a separate, identical file and run the import for each template group individually.

I installed Unity Connection 1.2(1) in vmware and restored the original server from the last backup and referenced it for recreating the call handlers, etc. and for recovering any greetings or messages I missed.

I imported old messages, but none of them were delivered to the end users, so make sure you test that.  I haven't spent a lot of time investigating the reason though.

HTH.



From: Ed Leatherman
Sent: Fri 7/25/2008 8:27 AM
To: cisco voip
Subject: [cisco-voip] Unity Connection upgrade


Planning to upgrade Unity Connection at a regional campus from 1.2 to 2.x next month, curious if anyone has run into any gotchas with it. The documentation on doing a migration seemed to be kind of "lite" out on cisco.com.

As part of the upgrade I also need to upgrade CM from 4.1.3 to 4.2. Unfortunately I don't have the time to plan a full blown migration to version 6, it will have to wait till next summer. I'd just wait and do it all at once next summer, but they are going to need more mailbox licenses at some point this year and UC 1.x is EoS already.

I'm aware that I can migrate user accounts and messages but not any call handlers, distro lists, etc. and found the migration tool out on CiscoUnityTools.com. What a pain :) My hardware appears to be supported for this upgrade (7835H-H1 server).

Thanks!
-- 
Ed Leatherman
Senior Voice Engineer
West Virginia University
Telecommunications and Network Operations

CONFIDENTIALITY NOTICE: This electronic mail transmission (including any accompanying attachments) is intended solely for its authorized recipient(s), and may contain confidential and/or legally privileged information. If you are not an intended recipient, or responsible for delivering some or all of this transmission to an intended recipient, be aware that any review, copying, printing, distribution, use or disclosure of the contents of this message is strictly prohibited. If you have received this electronic mail message in error, please delete it from your system without copying it, and contact sender immediately by Reply e-mail, or by calling 913-307-2300, so that our address records can be corrected.

Although this e-mail and any attachments are believed to be free of any virus or other defect that might negatively affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by the sender for any loss or damage arising in any way in the event that such a virus or defect exists.




-- 
Ed Leatherman
Senior Voice Engineer
West Virginia University
Telecommunications and Network Operations



CONFIDENTIALITY NOTICE: This electronic mail transmission (including any accompanying attachments) is intended solely for its authorized recipient(s), and may contain confidential and/or legally privileged information. If you are not an intended recipient, or responsible for delivering some or all of this transmission to an intended recipient, be aware that any review, copying, printing, distribution, use or disclosure of the contents of this message is strictly prohibited. If you have received this electronic mail message in error, please delete it from your system without copying it, and contact sender immediately by Reply e-mail, or by calling 913-307-2300, so that our address records can be corrected.

Although this e-mail and any attachments are believed to be free of any virus or other defect that might negatively affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by the sender for any loss or damage arising in any way in the event that such a virus or defect exists.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20080725/b79d9a0c/attachment.html>