[cisco-voip] Upgrade CUCM&UCCX(7.0) to ver 9.0

[Ryan LaFountain (rlafount)]

Whoops. I meant Repository item filename, not the content of the actual file :) Sorry for the confusion.

There are two defects that are related:

CSCub69129 resolved the issue of special characters that were not allowed in filenames in the underlying Windows OS but still appeared in the filename of the repository item. This includes < ,> , * , | , ? , :. The biggest use case we found from this is uploading a reactive debug file in the form "MIVR:[scriptname].aef". This is fixed in in the 8.5(1)SU4 and 9.0(2) PUT tools in that the backup actually fails until you correct this.

CSCuh09450 is for other, what we consider, 'special characters' (tested so far with the Spanish alphabet), but others would consider normal characters.

The way I recreated this was to create a script on UCCX 5.0(2)SR2 with a ñ (http://en.wikipedia.org/wiki/%C3%91) in the filename. This gets imported into the UCCX DB on the 5.0(2) server as ñ. The PUT backup goes fine then fails the Phase I import process on the Linux version. My UCCX 5.0(2)SR2 was localized to Portuguese at the time. I haven't tested with the extra special characters you've described, but we do some client-side form validation and I would have to check if those are included but haven't tested as there isn't a strong use case for having them in filenames anyway, but there is for localized characters.

I will be validating this bug myself by uploading repository items with localized filenames to all languages we support and trying the backup/import process.

Let me know if this clears things up.

Thank you,

Ryan LaFountain
Unified Contact Center
Cisco Services
Direct: +1 919 392 9898
Email: rlafount at cisco.com
Hours: M – F 9:00am – 5:00pm

From: Anthony Holloway <avholloway+cisco-voip at gmail.com<mailto:avholloway+cisco-voip at gmail.com>>
Date: Friday, May 24, 2013 3:47 PM
To: Ryan LaFountain <rlafount at cisco.com<mailto:rlafount at cisco.com>>
Cc: Angel Castaneda <hello at angelcastaneda.com<mailto:hello at angelcastaneda.com>>, "cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>" <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Subject: Re: [cisco-voip] Upgrade CUCM&UCCX(7.0) to ver 9.0

Ryan,

What exactly is meant by: special characters?

In most cases characters such as: ? ! @ & |, are all special characters and I just don't see how you WOULDN'T have these characters in your scripts.

Or are they referring to "extra special characters" such as: ¶ð¿Σڱ☺♂


On Fri, May 24, 2013 at 2:00 PM, Ryan LaFountain (rlafount) <rlafount at cisco.com<mailto:rlafount at cisco.com>> wrote:
Hi,

This is a bug I recently filed regarding special characters in Repository items. If you have special characters in Scripts, Prompts, Documents, Grammars, the PUT backup will succeed but the PUT restore on 9.x, 8.x will fail during Phase I (configuration import).

It is currently unresolved, but we're working on a solution and hopefully it will be included in 9.0(2)SU1.

HTH.

Thank you,

Ryan LaFountain
Unified Contact Center
Cisco Services
Direct: +1 919 392 9898<tel:%2B1%20919%20392%209898>
Email: rlafount at cisco.com<mailto:rlafount at cisco.com>
Hours: M – F 9:00am – 5:00pm

From: Angel Castaneda <hello at angelcastaneda.com<mailto:hello at angelcastaneda.com>>
Date: Friday, May 24, 2013 2:44 PM
To: Ryan LaFountain <rlafount at cisco.com<mailto:rlafount at cisco.com>>
Cc: Ed Leatherman <ealeatherman at gmail.com<mailto:ealeatherman at gmail.com>>, khaled Saholy <khaled_saholy at hotmail.com<mailto:khaled_saholy at hotmail.com>>, "cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>" <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>

Subject: Re: [cisco-voip] Upgrade CUCM&UCCX(7.0) to ver 9.0

Hello Ryan,

Regarding point #2 - I'm curious what CSCuh09450 is about, but it's currently under review. Does that only affect the Windows to Linux upgrade, or will it affect any other day-to-day operations?

Thank you,

Angel Castaneda
Telephone Whisperer


On Fri, May 24, 2013 at 7:14 AM, Ryan LaFountain (rlafount) <rlafount at cisco.com<mailto:rlafount at cisco.com>> wrote:
Hi Khaled,

All great comments so far (thanks Ed and Joel). I think you've covered most of it already, but I'll add a few pointers:

  1.  You must move UCCX to 7.0(2)ES3 before migration to UCCX 9.
  2.  I'm not sure if you've settled on a 9.x version yet, but I would highly recommend 9.0(2)SU1 (standard disclaimers apply). 9.0(2) is out but SU1 is scheduled to come out next month. We've made/will be making some important fixes in SU1 that WILL impact the Windows to Linux upgrade process. Reference CSCue38031, CSCue59553 and especially CSCuh09450.
  3.  CAD/CSD/CDA clients will automatically upgrade from 7.0(2)ES3 to 9.0(2), but Historical Reporting Client and any Editor clients will not. You will have to uninstall, re-download and reinstall.
  4.  All configuration and historical data will be migrated by the PUT tool.
  5.  As Ed said, take a test PUT backup on the 7.x system to make sure it works. Then, take another right before migrating. Any changes or historical records written after the PUT backup won't be carried over to the 9.x. system. You can even import the PUT backup on a server with a different hostname/IP as the 7.x box. So, you could take the PUT backup on 7.x and just shut that server(s) down for a fallback plan and install 9.x on new servers (or VM) and run the import if you have the spare hardware/resources.
  6.  Upgrade CUCM first. During the PUT restore on 9.x, the CUCM 7.x was integrated with must be up and available and it must contain all of the configuration UCCX is expecting but it must be on a version compatible with UCCX 9.x.

We'll be significantly revamping the upgrade documentation in the coming weeks, so stay on the lookout for improved docs. If I think of anything else, I'll be sure to follow with another email.

Hope this helps. Good luck!

Thank you,

Ryan LaFountain
Unified Contact Center
Cisco Services
Direct: +1 919 392 9898<tel:%2B1%20919%20392%209898>
Email: rlafount at cisco.com<mailto:rlafount at cisco.com>
Hours: M – F 9:00am – 5:00pm

From: Ed Leatherman <ealeatherman at gmail.com<mailto:ealeatherman at gmail.com>>
Date: Friday, May 24, 2013 7:57 AM
To: khaled Saholy <khaled_saholy at hotmail.com<mailto:khaled_saholy at hotmail.com>>
Cc: "cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>" <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Subject: Re: [cisco-voip] Upgrade CUCM&UCCX(7.0) to ver 9.0

I can't comment on version 9 of anything yet, but the UCCX upgrade from 7 to 8.5 (which was also an OS change) went surprisingly smooth. We run an HA pair of servers and that is usually where we run into issues but this time it went great.
Couple things:
- As you see there is a PUT tool to export your configuration from 7.
- May want to run through the PUT tool on a test system (or on the system you will upgrade during a maintenance window) just to see what its doing and make sure it is going to complete. You need a SFTP server available during the export and then during your migration to move the file around.
- Some of the TCP and UDP port numbers have changed from 7 to 8.5+ for CAD, CSD, HRC clients. If the customer has any firewalls in between UCCX and their agents, you will likely need to make modifications there for things to work.

My upgrade from CUCM 7.1 to 8.6 took a looong time as it had the red hat upgrade in there too, which will also be the case for 7.1 to 9 I figure. It took me something like 5-6 hours with 6 nodes and about 7600 endpoints. I would suggest clearing out the CAR and CDR's on the cluster and research any other ways to help it go faster. YMMV.

Good luck




On Fri, May 24, 2013 at 7:11 AM, khaled Saholy <khaled_saholy at hotmail.com<mailto:khaled_saholy at hotmail.com>> wrote:

Hi Friends,

I need your advice.

I have a project with a customer which we about to upgrade the contact center express ver 7.0 to ver 9.0 and also upgrade Call Manager ver 7.1 to 9.

I'm familiar with the upgrade process of call Manager from CM ver 6.1 BE to CM 8.6 Regular as I have implemented this work myself.

I've migrated the users , phones , export and import of config from old CM to the new CM with some manipulation here and there.

But I'm asking specifically about upgrade CM to ver 9,What is your experience of this upgrade , have anyone tried migration or upgrade , which one do you advise?

And more importantly the upgrade of UCCX, I have good experience with UCCX ver 7 but haven't tried yet working with UCCX ver 9.

What kind of configurations , data that can be upgradeable? Applications, scripts, prompts, reports...?

I started reading the Cisco documentation about the UCCX upgrade , and using PUT tools ...etc but I need your opinions and experiences, please.

Thanks in advance for your help.

Regards.

khaled Al-Saholy

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip




--
Ed Leatherman

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip



_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20130524/2e7416f2/attachment.html>