[cisco-voip] IPCC Express upgrades 4.x to 5.x 6.x or 7.x

[Scott Voll]

used the PUT to get the media and then contact Licensing at cisco dot com to
get licensing changed.  but  needed the PAK from the PUT / Media to get
Licensing to do anything.

Scott

On Thu, Oct 23, 2008 at 10:24 AM, Aman Chugh <aman.chugh at gmail.com> wrote:

> Just curious , how do you generate licenses for UCCX , when you do a major
> upgrade like 4.x to 5.x which involves an OS re image , do you re use the
> 4.x license or put in a request for the new license.
>
> Aman
>
>   On Thu, Oct 23, 2008 at 10:45 PM, Scott Voll <svoll.voip at gmail.com>wrote:
>
>> how old is your current MCS servers?  might be able to just run it as a
>> refresh of hardware.  Or run it as a part of a Disaster recovery / business
>> continunity plan.
>>
>> I just upgraded from CM 4.1 to 6.1 and UCCx 4.0 to 5.0. but it WAS on new
>> hardware as part of a Disaster recovery plan.
>>
>> Worked pretty good, but I'm glad it wasn't a 4 hour maintenace window.
>>
>> Scott
>>
>>   On Wed, Oct 22, 2008 at 12:38 PM, Micah Bennett <mbennett at als-xtn.com>wrote:
>>
>>>  Thanks Adam.  That is great great news…….What a huge P I T A!!!!!!!!
>>>
>>>
>>>
>>> We have 120 agents, 60+ CSQs, 60+ Skills, 90+ application triggers.  No
>>> plans for a rebuild (upgrade) any time soon, but at least I know what to
>>> plan for.
>>>
>>>
>>>
>>> I know one thing I can plan on when the time comes is for my executives
>>> to be yelling and wondering why they didn't get avaya.
>>>
>>>
>>>
>>> Micah
>>>
>>>
>>>
>>>
>>>
>>> *From:* adam.blomfield at gmail.com [mailto:adam.blomfield at gmail.com] *On
>>> Behalf Of *Adam
>>> *Sent:* Wednesday, October 22, 2008 2:32 PM
>>> *To:* Micah Bennett
>>> *Cc:* cisco-voip at puck.nether.net
>>> *Subject:* Re: [cisco-voip] IPCC Express upgrades 4.x to 5.x 6.x or 7.x
>>>
>>>
>>>
>>> There is no upgrade path for UCCX. The only things you can migrate are
>>> your scripts (if they convert correctly) and your prompts. The "upgrade"
>>> process is a complete system rebuild. The OS changes from 2000 to 2003, so
>>> you have to format the box and start over or, as you suggested, use new
>>> hardware. Once that is done you have to reconfigure agents "IPCC Extension"
>>> (formerly known as ICD extension). You also have to reconfigure all agents,
>>> skills, skill assignments, resource groups and CSQs in UCCX, along with your
>>> port groups, triggers and applications. As you can see screenshots are going
>>> to be your best friend. This is hardly a process that can be called an
>>> "upgrade".
>>>
>>> -Adam
>>>
>>> On Wed, Oct 22, 2008 at 2:07 PM, Micah Bennett <mbennett at als-xtn.com>
>>> wrote:
>>>
>>> Hello all
>>>
>>> Just doing a little research on the upgrade options for our system.
>>>
>>> I have the compatibility matrix for both call manager and ipcc express.
>>>
>>> The call manager matrix shows the support to and from upgrade paths using
>>> the DMA tool or direct upgrade.
>>>
>>> I know that it is mostly a new install because of moving form windows/sql
>>> to linux/Informix.  The DMA tool just helps bring over your data so its not
>>> a 100% scratch rebuild.
>>>
>>> What about the IPCC versions.  The matrix does not seem to show the same
>>> to and from data.
>>>
>>> It looks like the IPCC express systems continue to use Windows for their
>>> OS.  Is this correct?
>>>
>>> Does anyone have a link to any document that shows the supported and
>>> tested upgrades from one IPCX version to another?
>>>
>>> For the group members that have done a full system upgrade, did you
>>> upgrade a live system or purchase new hardware to put the upgrade on.  I
>>> would assume that using new hardware is the best way to have the least
>>> impact on a working system.  I imagine that a full upgrade of all systems is
>>> going to take a few days, and not a few hours in the maintenance window.
>>> We have to be especially careful because we are a 24x7x365 call center.
>>>
>>> Thanks
>>>
>>> *Micah Bennett*
>>>
>>> Telecommunications Admin
>>>
>>> *Automated License Systems*
>>>
>>>
>>> _______________________________________________
>>> cisco-voip mailing list
>>> cisco-voip at puck.nether.net
>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>
>>>
>>>
>>> _______________________________________________
>>> cisco-voip mailing list
>>> cisco-voip at puck.nether.net
>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>
>>>
>>
>> _______________________________________________
>> cisco-voip mailing list
>> 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/20081023/dfb1e039/attachment-0001.html>