Unity Connection Upgrade Version Switch - Grab a Coffee

Thought I would post some reassurance for anyone upgrading Unity Connection to 8.5. I can't remember other Unity Connection upgrades taking so long on the version switch (utils system switch-version). In my case I was upgrading a Unity Connection cluster from 7.1(3b) to 8.5(1)SU1. The software installation to the inactive partition took approximately two hours (per server), which is what the documentation describes you should expect during a business hours upgrade. What the documentation didn't say was that during the version switch you could expect ~45 minutes of no network response from the server. Anyway, hopefully someone will read this, grab a coffee, and wait (instead of sending out rollback notifications - - as I did!).
HTH
Dom

Just wanted to make sure you had seen this
If you are upgrading during nonbusiness hours: On the publisher server, run the CLI command utils iothrottle disable to speed up the upgrade.
In an effort to prevent upgrades from adversely affecting system performance during business hours, the upgrade process is throttled and may take several hours to complete. If you are upgrading during a maintenance window, you can speed up the upgrade by disabling the throttling. This decreases the time required for the upgrade to complete but adversely affects Connection performance.
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/upgrade/guide/8xcucrug009.html#wp1056720
Cheers!
Rob
"Your life is worth much more than gold."
- Bob Marley

Similar Messages

Unity Connection Upgrade from 8.6.2 to 9.1 latest version

Hi,
Am planning to Upgrade my CUC(Unity Connection) from 8.6.2 to 9.1 latest version, having my Call manager in the same version 8.6.2. I will upgrade my Call Manager from 8.6.2 to 9.X later.
Hope i can upgrade my CUC first.
I need some info like,
1) Am not getting the image to download which can upgrade from 8.6.2 to 9.1 latest version directly. Should i have to move to 9.0 first and then to 9.1 ??
2) Is their any pre cautions need to be taken care/ well known issues during the upgrade.
3) Also, hope licensing get migrated automatically (no need to have extra efforts)
4) Advantages of Moving to 9.x wrt to features compared to 8.6.
Pls suggest.
Thanks
Jagadish G

Hi Jagadish,
Just to answer few :
you can downlaod the image from below link under UC Applications amd messaging:
http://software.cisco.com/download/release.html?mdfid=284603371&flowid=45680&softwareid=282074295&release=8.4(1)&relind=AVAILABLE&rellifecycle=&reltype=latest
Supported Version Combinations for Cisco Unity Connection 2.x and Later with Cisco Unified Communications Manager
Cisco Unity Connection
Cisco Unified Communications Manager
2.x and Later
9.1(2), 9.1(1), 9.0(1),8.6(2),8.6(1),8.5(1),8.0(x), 7.1(x), 7.0(x), 6.1(x), 6.0(x), 5.1(x), 5.0(x), 4.3(x), 4.2(x), 4.1(3)
No new functionality has been introduced in UCXN 9.1(2)
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/release/notes/912cucrn.html
for licensing on ELM, u need to get in touch with [email protected] take backup of UCXN 8.6 before initiating upgrades.
regds,
aman

Unity Connection upgrade

OK, I went through the upgrade on the inactive partition of both my publisher and subscriber Unity Connection (8.5). Unfortunately, we had some other network issues that caused us to decide to not do the reboot to the updated partitions. Two questions: 1) is there any problem that I didn't complete the upgrade with the reboot? In other words, can I run as long as I like on the old version? 2) When I am able to do the upgrade, do I need to do anything special before I re-run the upgrade on the servers? Like to clear space?
Thanks,
Jill

1. Yes, just be aware you'll lose all changes done between the upgrade and the time you switch versions.
If you want to keep the changes, you'll need to run the upgrade again.
2. No, assuming nothing has changed, if there's any need for it, you'll get the error duing the install.
HTH
java
if this helps, please rate
www.cisco.com/go/pdihelpdesk

Unity Connection upgrade from 7.1.3 to 8.5?

We are considering upgrading our unity connection cluster to version 8.5 from our current version 7.1.3 and we are concerned about a few things.
1. Compatibly between UC 8.5 and CUPS 8.02 and CUPC 8.5
2. How to backup and restore current UC7.15 messages and user's VM name and greetings.
Does anyone here in the support community have experience with this version upgrade? Would we be using cobras to back up and restore the messages? Are there any "gotchas" we need to be aware of here?
Please let me know.
Thank you!
Rgds,
Vicky

Hi Vicky,
No worries my friend
We have not done this upgrade and do not have any current plans to do so. I am
always, always, always slow to move along the upgrade path. This may be a bad thing
but it has saved us some great pain as well over the years. Our current versions are;
CUCM - 7.1(3b)su2
CUC - 7.1(3b)su2
We have found these versions to be very stable. I have spent a fair bit of time looking at people's
migrations to 8.5(x) here @ CSC and have not seen or heard of too many horror stories. This is one bug you'll
want to look out for.
CSCtn61453            Bug Details
Applying 8.5.1 software as patch results in corrupted CUC installation.
Symptom:
After fresh installation of 8.5.1 software, we can notice several problem symptoms.
- Connection services and Connection DB does not start
- System cannot be accessed via web page
- Informix error messages for certain CLI commands
Example :- show cuc cluster status
com.informix.asf.IfxASFException: Attempt to connect to database server (ciscounity) failed.
Command failed
Conditions:
It is observed during fresh installation of Unity Connection product when installation was
started with earlier version of software and 8.5.1 software was applied as a patch during the setup process.
Workaround:
First, perform a fresh installation of earlier version of software using the install media. Then after verifying the installation, proceed with the upgrade to 8.5.1 as a separate process.
Status
Open
Severity
2 - severe
Last Modified
In Last 3 Days
Product
Cisco Unity Connection
Technology
1st Found-In
8.5(1)ES1
Best of luck with your changes.
Cheers!
Rob

Hardware checks performed during an Unity Connection upgrade ?

I have Unity Connection 8.0.3 running on an old HP server. (Identified as a HP 7845H2 2333 during the install)
I tried a clean install of Unity Connection 8.6.1 on an identical server. The install failed with the server hardware failing to be recognised.
This is despite the server hardware meeting the requirements of the Unity Connection hardware compatibility check list.
If I try to upgrade the Unity Connection 8.0.3 system to 8.5, will the install program run a compatibility check before loading / upgrading ?
The last thing I want is to successfully install 8.5 but have the system crash when I try to boot the new version.
Thanks
Andy

Hi Andy -
Your server may have been on the compatible hardware list but could require additional hardware - see these specs -
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/supported_platforms/8xcucspl.html#wp771057
Unity Connection 8.6 requires 6Gig RAM and 4-146 Gig hard drives for the 7845 servers. Yes the install program does a compatibility check - if the install does not see the "correct" configuration, it does not show Unity Connection as one of the applications available for install. I would recommend moving to 8.6 if you can, or if you decide on 8.5, refer to Bug Search (Bug Toolkit) and review the caveats. I recently had to applu ES55 to CUC 8.5 service release 2 to fix ViewMail forwarding voice messages from Outlook. If you are planning to install Cisco UCS or an HP/IBM provided virtualized environment as an option, definitely check out 8.6 - it will save you from having to do a refresh upgrade from 8.5 - 8.6!
Sincerely,
Ginger

Unity Connection Upgrade 8.5(1)SU1 to 8.5(1)SU5

I am upgrading Unity Connection at 2am on a Unity cluster pair. I would like to do as much as possible ahead of time and only do the reboot to the upgrade partition at 2am. If I do the upgrade now without the reboot, will any changes to users made this afternoon be lost when I reboot at 2am?

Yes, all change between now and then will be lost.
Chris

Unity Connection Upgrade Error from 8.6.2.20000-2 to 8.6.2.22900-9

Hello,
After 2 hours my Unity show me this folow error. Anybody see this error?
06_load-database|Depending on the server specifications and on the level of activity on the system, this may take up to an hour.|<LVL::Info>

And that's not an error, if you look closely at the end, it says INFO
HTH
java
if this helps, please rate
www.cisco.com/go/pdihelpdesk

Failure to upgrade Cisco Unity Connection 8.6.2 to 9.1.2

Hi everybody.
Has someone that can help me with follow problem?
I making a Cisco Unity Connection upgrade from version: 8.6.2.20000-76 to 9.1.2.10000-28. But unfortunately we can't sucessfull to make this process.
On the finish of this process, I can see this outup error:
11/23/2013 12:28:55 upgrade_manager.sh|Cleanup exiting - Cached Data: [Vendor= VMware, Inc.
HWModel=VMware
CPUCount=2
CPUType= Intel(R) Xeon(R) CPU E5-2643 0 @ 3.30GHz
CPUSpeed=3300
MEMSize=6144
BIOSVer=PhoenixTechnologiesLTD 6.00 06/22/2012
ObjectId=1.3.6.1.4.1.9.1.1348
OSVersion=UCOS 5.0.0.0-2
SerialNumber= VMware-56 4d e0 4f 4d 85 87 7b-eb 22 0e 52 a7 73 1a 22
VendorOID=1.3.6.1.4.1.674]|<LVL::Info>
11/23/2013 12:28:55 upgrade_install.sh|Cleaning up download...|<LVL::Info>
11/23/2013 12:28:55 upgrade_install.sh|Cleanup upgrade source area.|<LVL::Info>
11/23/2013 12:28:55 upgrade_install.sh|Ejecting DVD (/dev/sda1)|<LVL::Debug>
11/23/2013 12:28:55 upgrade_install.sh|Removing /common/download/9.1.2.10000-28|<LVL::Info>
11/23/2013 12:28:55 upgrade_install.sh|Started auditd...|<LVL::Info>
11/23/2013 12:28:56 upgrade_install.sh|Started setroubleshoot...|<LVL::Info>
11/23/2013 12:28:56 upgrade_install.sh|Changed selinux mode to enforcing|<LVL::Info>
11/23/2013 12:28:56 upgrade_install.sh|Cleaning up rpm_archive...|<LVL::Info>
11/23/2013 12:28:56 upgrade_install.sh|Removing /common/rpm-archive/9.1.2.10000-28|<LVL::Info>
11/23/2013 12:29:00 upgrade_install.sh|IOWAIT monitor stopped|<LVL::Info>
11/23/2013 12:29:00 upgrade_install.sh|File:/usr/local/bin/base_scripts/upgrade_install.sh:599, Function: main(), Upgrade Failed -- (1)|<LVL::Error>
11/23/2013 12:29:00 upgrade_install.sh|set_upgrade_result: set to 1|<LVL::Debug>
11/23/2013 12:29:00 upgrade_install.sh|is_upgrade_lock_available: Upgrade lock is not available.|<LVL::Debug>
11/23/2013 12:29:00 upgrade_install.sh|is_upgrade_in_progress: Already locked by this process (pid: 14477).|<LVL::Debug>
11/23/2013 12:29:00 upgrade_install.sh|release_upgrade_lock: Releasing lock (pid: 14477)|<LVL::Debug>
Best Regards,
Claudio Costa
A mensagem foi editada por: Claudio Costa

Tks Manish, I just perform a restart on the both nodes on my CUC cluster and after that I did can install this upgrade patch.
Also is very important install the upgrade patch on all servers of the cluster before perform a switch-version on the publisher and then on the others nodes.
Best Regards,
Claudio Costa

Upgrade Unity Connection Failing

I am upgrading a Unity Connection from
Version '7.1.5.33900-10 Unrestricted' to '8.5.1.13900-5 Unrestricted'
It fails with hardware validation (error below)
My hardware is a VM on a C210M2
Memory: 6144
CPU: 2
HD1: 146gb
HD2: 146gb
Do I need a special version of CUC for VM?
Any Help appreciated.
James
10/18/2011 14:13:48 upgrade_manager.sh|Check if the upgrade is allowed|<LVL::Info>
10/18/2011 14:13:48 upgrade_manager.sh|Validate hardware for the upgrade|<LVL::Info>
10/18/2011 14:13:48 upgrade_manager.sh|Hardware is supported for the upgrade|<LVL::Info>
10/18/2011 14:13:48 upgrade_manager.sh|Validate hardware for "connection" deployment|<LVL::Info>
10/18/2011 14:13:48 upgrade_manager.sh|File:/common/download/8.5.1.13900-5/Cisco/base_scripts/upgrade_manager.sh:892, Function: validate_upgrade_allowed(), This server is not supported for use with the version of "connection" that you are trying to install. For information on supported servers, see the applicable version of the "connection" Supported Platforms List at http://www.cisco.com/en/US/products/ps6509/products_data_sheets_list.html|<LVL::Error>
10/18/2011 14:13:48 upgrade_manager.sh|Cleanup RAM disk|<LVL::Info>

Right - after much testing - found out the solution to this problem.
The Cisco OVA Templates dont work for CUC for certain install disks (well for at least 7 that I tried !)
Tested Disks (with VSXI version 4.1)
CUCM 8.5 - 80-9842-02
CUCM 8.5 - 80-9927-02
CUCM 8.5 - 80-9929-01
CUCM 8.5 - 80-9842-02
CUCM 8.6.1a - 80-9986-02
CUCM 8.6.1a - 80-9988-02
CUCM 8.6.1a - 80-9989-02
You need to load the OVA template and make the following changes -
Memory     :     6gb (can be set to 8gb if required)
CPU          :     2 (can be set to 3 if required)
Video          :     16mb (hard set)
VMCI          :     Unrestricted (enable checked)
SCSI          :     LSI Logic Parallel
HD          :     200gb - independent persistent
Network      :     needs to be 'connect at power on'
FD              :     Client Device 'Connected' but I dont think this setting matters.
Now Cisco Unity Connection appears at as part of the installable product suite.
I think the OVA templates are extremely poor - clearly untested.
eg - its names your VM - ALIGNED_500User-UnityConnection1CPU160GB.ova etc
Anyway - hope this information help other people from wasting a lot of time.

Unity Connection 8.6.2 report error and issues

Hello,
I found some other hits on this error and tried the workarounds (restarting tomcat, and report data harvester) but am still getting "Unable to find any report data based on parameter(s)" for a certain timeframe on multiple reports when I know activity occurred in that timeframe.
User Phone login report, Outcall Billing Detail Report, others.
CUC version is 8.6.2.20000-2
Problem is during this timeframe someone dialed into system and changed the transfer extensions to various LD numbers throughout an entire day and the reports aren't showing these outcalls. Call Manager CDR data show the calls being placed from Unity VM ports and the Unity Conversation Manager traces I grabbed for the timeframe show the calls to those numbers to. I'm just trying to match up with a report and figure out if there is some other log or trace file I can look to determine for sure the caller logged in to the voicemail box and changed the transfer extension on it. (guessed the voicemaill password). The failed log in report doesn't even show the failed login attempt in output from traces below. The transfer extension dest addr was different on the transfers on this same mailbox. Have locked down the system since but want to get better grip on this with the reports and traces.
I looked over the CUC 8.6.2 SU1 and SU2 release notes and not seeing any resolved bugs for these matters either.
Here are some samples lines from Conversation Manager traces:
00:32:46.399 HDR|02/04/2013 ,Significant
00:32:46.399 |9744,PhoneSystem-1-001,E68CA6DB3CAE4118BE9F9612BD3540A9,Arbiter,-1,Incoming Call [callerID='' callerName='' calledID='555123' redirectingID='555123' lastRedirectingID='555123' reason=4=FwdNoAnswer lastReason=8=FwdUncond] port=PhoneSystem-1-001 portsInUse=1 ansPortsFree=23 callGuid=E68CA6DB3CAE4118BE9F9612BD3540A9
00:33:55.006 |9744,PhoneSystem-1-001,E68CA6DB3CAE4118BE9F9612BD3540A9,MiuGeneral,25,Enter CAvMiuCall::TransferEx destAddr='715551231234' type=2=Release maxRings=4 mediaSwitch='00a499fa-a193-45b0-a153-564a64019eb8'
00:33:58.955 |9744,PhoneSystem-1-001,E68CA6DB3CAE4118BE9F9612BD3540A9,MiuGeneral,25,Exit CAvMiuCall::TransferEx=0x00000000=S_OK
00:34:37.090 |9832,PhoneSystem-1-001,9DB394E443A3419FA0020BC9D1A92806,Arbiter,-1,Incoming Call [callerID='' callerName='' calledID='555123' redirectingID='555123' lastRedirectingID='555123' reason=4=FwdNoAnswer lastReason=8=FwdUncond] port=PhoneSystem-1-001 portsInUse=1 ansPortsFree=23 callGuid=9DB394E443A3419FA0020BC9D1A92806
00:34:50.403 |9832,PhoneSystem-1-001,9DB394E443A3419FA0020BC9D1A92806,CDL,11,CCsCdlImsAccess::AuthenticateSubscriber: Cannot authenticate user: JOESMITH IMS Result Code: 1 on line 108 of file CdlIms/src/CsCdlImsAccess.cpp: Error: 0x80046505 Description: E_CDL_SP_EXEC_FAILURE
00:34:50.403 |9832,PhoneSystem-1-001,9DB394E443A3419FA0020BC9D1A92806,CDE,3,Authentication Failed for Subscriber 555123 (Src/CsCallSubscriber.cpp 2969)
00:34:50.404 |9832,PhoneSystem-1-001,9DB394E443A3419FA0020BC9D1A92806,-1,-1,An invalid password entered when trying to log into a user mailbox. Details - [].
00:36:29.331 |9832,PhoneSystem-1-001,9DB394E443A3419FA0020BC9D1A92806,MiuGeneral,25,Enter CAvMiuCall::TransferEx destAddr='715551231234' type=2=Release maxRings=4 mediaSwitch='00a499fa-a193-45b0-a153-564a64019eb8'
00:36:33.484 |9832,PhoneSystem-1-001,9DB394E443A3419FA0020BC9D1A92806,MiuGeneral,25,Exit CAvMiuCall::TransferEx=0x00000000=S_OK
00:44:53.444 |9743,PhoneSystem-1-001,FEB6975B82284F37A161CD66ECBA61C6,Arbiter,-1,Incoming Call [callerID='' callerName='' calledID='555123' redirectingID='555123' lastRedirectingID='555123' reason=4=FwdNoAnswer lastReason=8=FwdUncond] port=PhoneSystem-1-001 portsInUse=1 ansPortsFree=23 callGuid=FEB6975B82284F37A161CD66ECBA61C6
00:45:20.019 |9743,PhoneSystem-1-001,FEB6975B82284F37A161CD66ECBA61C6,MiuGeneral,25,Enter CAvMiuCall::TransferEx destAddr='715551231234' type=2=Release maxRings=4 mediaSwitch='00a499fa-a193-45b0-a153-564a64019eb8'
00:45:24.121 |9743,PhoneSystem-1-001,FEB6975B82284F37A161CD66ECBA61C6,MiuGeneral,25,Exit CAvMiuCall::TransferEx=0x00000000=S_OK
Thanks

Hello ebergquist,
As advised we could try to run a report before an upgrade was performed to verify if it will pull the information, which in the event it does we would be matching the bug, therefore access the CUC CLI and type the following command: file get install *
You will be required to have an SFTP available for the file transfer and port 22 open on the sftp client.
Once you receive the files you would need to check system-history.log, below is an example.
=======================================
Product Name -    Cisco Unity Connection
Product Version - 8.5.1.12900-7
Kernel Image -    2.6.9-89.0.20.EL
=======================================
02/24/2013 13:35:02 | root: Boot 8.5.1.12900-7 Start
02/24/2013 16:03:45 | root: Install 8.5.1.12900-7 Success
Once you check the time stamp and date of the upgrade try to gather a report for a time range before the upgrade was performed, even though they might be overwritten, there still could be a possibility that it succeeds.
If this bug is not the issue then you might want to take into consideration:
1. Make sure that the service ReportDB is [STARTED] in the output of the command: utils service list.
2. If you have Digital Networking on your server make sure there is no stalled replication. Go to RTMT (Real Time Monitoring Tool)> Syslogs> Select on the dropdown your server> Doble click on Application logs> CiscoSyslog. You can then do a manual search or sort with the filter option:
Severity: Error
App ID: CuReplicator
Hit apply. Below is an example:
Date: Feb 19 08:01:15
Machine Name: LAB1111
Severity: Error
App ID: CuReplicator
Message: : 1151681: LAB1111.corpnet2.com: Feb 19 2013 08:01:11.662 UTC : UC_UCEVNT-3-EvtReplicatorStalledReceiveReplication %[ClusterID=][NodeID=LAB1111]: Detected stalled replication receiving from location LAB1111. Waiting for missing USN 2222. This situation may indicate network connectivity problems.
3.Make sure that replication is working properly in the cluster. You can check them via the following commands: showcuc cluster status    and   utils dbreplcation runtimestate
For the TransferEx that you state changed to ceros -> TransferEx=0x00000000=S_OK , this is just a hexadecimal value that is returned stating that the transfer that took place during the call was successful, in this case the actual transfer was to the following destination -> TransferEx destAddr='715551231234', and was during a call to ->calledID='555123' , this does not have to do with the actual change of a transfer number performed by a user.
Those traces won't be enough you will have to additionally set: ConvSub, level 3   and CDE, level 16 so that you may see output in the traces as the example posted in the previous thread.
Traces would be the path to follow in order to verify the user that changed the transfer rule, as this is as i understand the goal your pursuing.
However if it is of any help, another way to get on hold of the numbers that were updated on the Transfer Rule is to use the User Data Dump tool, this information reflects changes regardless of whether it was done via TUI (Telephone User Interface) or GUI (Graphic User Interface). For more information on the tool go to:
http://ciscounitytools.com/Applications/CxN/UserDataDump/Help/UserDataDump.htm
Traces are extensive to be reviewed if done manually, however you can do a text search with a tool as Notepad ++ to look for keywords as "NewTransferNumber =" or "CDE,16,Transfer allowed", once you find this you check the call GUIDwhich is the reference number of the call and that exists during the entire length of the call, whether it is while a person is leaving a voicemail or the user is accessing his/her's inbox. This would speed up your search.
So as explained in the first thread you would then do another text search returning all possible matches with that callGUID.
Now if you get to the very beginning of the call you would see something like:
Line 13712: 18:58:05.156 |24720,CCIE-1-001,0C9C97BDF5F444F0B535D231C32DDCB4,Arbiter,-1,Incoming Call [callerID='2199' callerName='' calledID='6789' redirectingID='' lastRedirectingID='' reason=1=DirectlastReason=1024=Unknown] port=CCIE-1-001 portsInUse=1 ansPortsFree=1callGuid=0C9C97BDF5F444F0B535D231C32DDCB4
In this example you see my test user callerID='2199' calling the Pilot number 6789 which is the voicemail button
calledID='6789, and the what type of call is it whether Forward or Direct, when logging to voicemail you are going to see Direct which is going to match the Direct Routing Rules and send the call to the attempt sign in conversation.
The other approach is a rule out method between the Audit traces and the User Data Dump tool.
So let's say you have a baseline document that states all of the Transfer numbers for all users.
If the User Data Dump reflects a different number and the Audit logs do not show any change, starting from the time the baseline was created and the point of time where the number was changed, then you could deduce the change was done via TUI (Telephone User Interface). Unfortunately you wouldn't be able to tell who did the change in this case.
Nevertheless, remember that a user may have for example an Alternate Extension so the change might not necessarily be done from the office phone: "Alternate extensions can make calling Cisco Unity Connection from an alternate device—such as a mobile phone, a home phone, or a phone at another work site—more convenient. When you specify the phone number for an alternative extension, Connection handles all calls from that number in the same way that it handles calls from a primary extension (assuming that ANI or caller ID is passed along to Connection from the phone system). This means that Connection associates the alternate phone number with the user account, and when a call comes from that number, Connection prompts the user to enter a PIN and sign in."
Best regards,
David Rojas
Cisco TAC Support Engineer, Unity
Email: [email protected]
Phone: 1-407- 241-2965 ext 6406
Mon, Wed, and Fri 12:00 pm to 9:00 pm ET, Tue and Thu 8:00 am to 5:00pm ET
Cisco Worldwide Contact link is below for further reference.
http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html

Import Export from CUE to Unity Connection 8+

After looking on CiscoUnityTools.com I see there is one CUE tool for importing Users and recorded name WAVs from CUE into Cxn 8+
Does anyone have a method for moving all the users AND voicemails from CUE systems into Unity Connection, any version?

Hi there,
There are no "free" tools that will migrate greetings and messages
from CUE to Connection.
The one place to look is @ Cisco partner CommonVoices "Now There";
http://www.cisco.com/en/US/prod/collateral/voicesw/ps6789/ps5745/ps6509/solutions_partner_cuc.pdf
They do claim to;
Switch from any traditional
system to Cisco Unity®
Connection
• Greetings, name
announcements, existing
messages, and call trees are
all retained along with
message status
• 10 years of experience
migrating millions of mailboxes
worldwide
http://www.commonvoices.com/products/NowThere.php
What many people do when migrating to a new voicemail system is to leave the
old system accessible for a period of time so that users can access their old
messages. This is what we did when migrating from Octel to Unity Connection
Cheers!
Rob
"What you don't have you don't need it now"
- U2

Unity Connections 8.6.2a Single Inbox Problem

We have a Unity Connections Server version 8.6.2a talking to Exchange 2010 SP1. We have verified Authenications, HTTPS, Certs etc. If we run a test from the Edit Unified Messaging Screen, we get the following:
Severity                               Issue                               Recommendation                               Details
The validation results for unified messaging service Exchange are the following:                                                                                                                                                                                                                                               Service "Exchange": AuthenticationMode=[Basic] [use HTTPS/validate] Server=[server.internaldomain.com] Type=[Exchange 2007/2010] Username=[domain\UnityUser]
The server domain name can be resolved.
Server server.domain.com can be contacted by pinging.
The service port for calendaring is functioning.
The certificate verification results from SSL is X509_V_OK.
This test does not test all aspects of the configuration of the service. To complete testing, add a unified messaging account for a user and test the account using the Test button on the Edit Unified Messaging Account page.
However under the user we get:
The validation results for the user unified messaging service account [email protected] with service Exchange are the following:                                                                                                                                                                                                                                               Service "Exchange": AuthenticationMode=Basic [use HTTPS/validate] Server=[server.internaldomain.com] Type=[Exchange 2007/2010] Username=[domain\UnityUser]
Failed accessing [email protected] on server.internaldomain.com                                    .                                                                                                                                                                                                           Diagnostic=[] Verb=[] url=[] request=[] response=[]
The system failed to perform a typical calendar operation.                                    Refer to other warnings and errors generated by the tool, and check the Tomcat log file for details.                                                                                                                                                                                                           The system failed while trying to make an API call.
I'm completely at a loss.

I get the following when I attempt to run that after install:
C:\Program Files\Cisco\Unified Serviceability\JRtmt>".\jre\bin\java" -Dsun.java2
d.d3d=false -Xbootclasspath/a:.;.\lib\xerces.jar;.\lib\log4j.jar;.\lib\jcchart45
0J.jar;.\lib\collections.jar;.\lib\JbcBeans.jar;.\lib\activation.jar;.\lib\axis.
jar;.\lib\axis-ant.jar;.\lib\commons-discovery.jar;.\lib\commons-io-1.3.2.jar;.\
lib\commons-logging.jar;.\lib\commons-lang-2.1.jar;.\lib\commons-net.jar;.\lib\i
fxjdbc.jar;.\lib\mail.jar;.\lib\maverick-debug-all.jar;.\lib\jaxrpc.jar;.\lib\sa
aj.jar;.\tzupdater.jar;.\lib\jide-common.jar;.\lib\jide-dialogs.jar;.\lib\jide-g
rids.jar;.\lib\wsdl4j.jar;.\lib\javacsv.jar;.\lib\jtds.jar;.\lib\commons-beanuti
ls.jar;.\lib\commons-collections.jar;.\lib\commons-digester.jar;.\lib\commons-el
.jar;.\lib\commons-jexl.jar;.\lib\commons-scxml.jar;.\lib\derby.jar;.\lib\xalan.
jar;.\lib\openssoclientsdk.jar -jar JRtmt.jar
Exception in thread "main" java.lang.NullPointerException
        at com.cisco.ccm.serviceability.rtmt.ui.SystemUtil.getLog4jConf(Unknown
Source)
        at com.cisco.ccm.serviceability.rtmt.ui.JRtmtMain.initTrace(Unknown Sour
ce)
        at com.cisco.ccm.serviceability.rtmt.ui.JRtmtMain.main(Unknown Source)
C:\Program Files\Cisco\Unified Serviceability\JRtmt>

Cisco Unity Connection 8.5.1 SU3 to 8.5.1 SU6 & Upgrade to 9.1.2

Two questions !
Firstly - I am upgrading to the latest patch level as I want to upgrade the systems to 9.1.X
I am installing UCSInstall_UCOS_8.5.1.16900-6.sgn.iso onto the inactive partition on the publisher then onto the inactive partition on the subscriber.
Then I plan to switch versions out of hours.
Question - will messages / data that has happened between the installation on the inactive partition and the switch version be preserved ??
So if I install onto the inactive partition at 1pm, then an important message is left at 2pm and I switch version at 3pm, does the iimportant message exist on the active partition at the end ??
Second question -
I have UCCX-8.5.1 SU4 (HA), CUC 8.5.1 SU6 (HA) and CUCM 8.5.1 SU6 (1 pub, 2 sub) - so 7 VM's in total.
If I want to migrate to -
UCSInstall_UCOS_9.1.2.12900-11.sgn.iso & UCSInstall_UCCX_9_0_2_UCOS_9.0.2.11002-27.sgn.iso
in which order should the installations take place ?? CUCM Publisher last ?? Publisher first ??
Thanks
James

Hi James,
+5 to my friend Aman for his good tips here
Messages are preserved during the "switch-version" so the messages left before the command is run will be preserved as they are stored in a "common" partition;
Switching to the Upgraded Version of Connection 8.x Software
If you chose not to automatically switch to the upgraded partition at the end of the upgrade, do the following procedure when you are ready to switch partitions.
To Switch to the Upgraded Version of Connection 8.x Software
Step 1 If you do not have a recent backup, back up the server by using the Disaster Recovery System. For more information, see the Disaster Recovery System Administration Guide for Cisco Unity Connection Release 8.x athttp://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/drs_administration/guide/8xcucdrsag.html.
Step 2 Sign in to Cisco Unified Operating System Administration.
Step 3 From the Settings menu, select Version.
Step 4 On the Version Settings page, select Switch Versions, and the following occurs:
•Connection services are stopped.
•Data from the partition where the older version is installed is copied to the partition where the newer version is installed. If changes to the database schema require updates to the format of data, that occurs in this step. Note that messages are stored in a common partition, so they are not copied.
•The Connection server restarts and switches to the newer version.
Note You can check the status of the installation of the upgrade software by using the CLI command show cuc version. The upgrade is complete when the inactive partition has the upgraded software and the active partition has the old software.
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/8x/upgrade/guide/8xcucrugx/8xcucrug009.html#wp1056720
The upgrade order is shown here (above link) as well, which is Pub followed by Sub;
Task List for Upgrading Connection 7.x or 8.x Software to the Shipping 8.x Version in a Connection Cluster
Cheers!
Rob

Unity Connection version clarification

Hi,
We installed UC 7.0 last January 2009 and this weekend we updated to the October 2009 release of 7.0.2(a)SU2
Where can I find a doc that describes the version numbering between the OS and the Application? Before the upgrade my Inactive Version was 7.0.1.21020-1 and the active was a flavor of 7.0.2 that was given to us by TAC in Jan. It was a pre-release.
Now my Inactive is still the same but my active is reporting as the October release of 7.0.2.22900-3.
So two questions
1 - How is this possible
2 - What does the ES stand for in the App version when I see it on the App web page (I realize the version of the OS is a different number scheme)
thanks

Josh,
I dont know that there is a document that describes the version numbering...if so, I've never seen one. However, it's always contained in the filename. So, to answer your questions:
1) Your active partition shows the application versioning number of 7.0(2a)SU2 which is seen in the first part of the filename which is UCSInstall_UCOS_7.0.2.22900-3. So when you upgraded, you rebooted the servers and switched partitions to the upgraded version which is why you see that as the Active version. The inactive is the same as it was before the ugprade because the system keeps an Active and an Inactive partition. This allows you to upgrade the inactive partition on the fly but choose not to reboot the server until a later time. Vice versa, it allows you to roll back to a previous version if the ugpraded version is problematic.
2) ES stands for Engineering Special. It indicates a certain patch rev of the application code. For example the latest patch rev for Unity Connection is ES 26 so if you upgrade to 7.1(3b)SU2, the CUC web page will give you a versioning number that reflects the code contains all patches and fixes rolled up to ES26.
Hailey
Please rate helpful posts!

Licensing for Unity Connection after Upgrade from 8.5 to 9.1.2

I upgraded my Unity connection from 8.5.1 to 9.1.2. ( my CUCM is still on 8.5.1) . I have 200 CUWL-STD ( 2200 DLUs), and 50 CUWL-PRO (850 DLUs) . Now I am working with Cisco to get a license file for Unity Connection and apply that to my ELM. I attached my licensing page for when I was in 8.5.1 . Just want to make sure if I will be getting enough license with that license file, or possibly I need to buy more. Someone told me that if I want to have users with mailbox I need to order more licenses since every user take one CUWL license.
Honestly i do not know how CUWL licensing work regardig to Unity or even CUCM.
Thanks,

Hi,
The following link provides details of licenses usage by diff endpoints on version 9.x
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/upgrade/uct/9_1_1/CUCM_BK_U0AE00F5_00_uct-admin-guide/CUCM_BK_U0AE00F5_00_uct-admin-guide_chapter_0100.html
HTH
Manish

Unity Connection Upgrade Version Switch - Grab a Coffee

Similar Messages

Maybe you are looking for