[cisco-voip] more upgrade questions

[Ted Nugent]

Not to split hairs Wes but I have contacted the UCSS team over
a dozen times in the past year (directly and via our inside sales) and
never received a response in 24 hours. The best response I ever received
was about 48 hours and the worst was about 8 business days, averaging about
72 hours, they have gotten better as the year has progressed. 4 months was
obviously a joke but when you're waiting to order something for
a angry client that never registered their UCSS, it seems about that long.



On Thu, May 10, 2012 at 2:59 PM, Wes Sisk <wsisk at cisco.com> wrote:

> I believe Erick got his question answered.
>
> As to UCSS response times -  The UCSS team aims for a 24 hour turnaround.
>  The UCSS team strives to meet this guideline for all inquiries to
> ucss-support[at]external.cisco.com.
>
> http://www.cisco.com/en/US/solutions/collateral/ns340/ns394/ns165/ns737/net_presentation0900aecd8063dc83.pdf
>
> It appears some folks may be contacting tac[at]cisco.com or cs-support[at]
> cisco.com for UCSS support. Those teams are unfamiliar with UCSS. In
> those situations it takes some time to understand the issue and get it
> routed properly.
>
> Regards,
> Wes
>
> On May 10, 2012, at 11:51 AM, Erick Wellnitz wrote:
>
> Absolutely perfect.
>
> Now to wait for the UCSS team...at least I'll be able to get started on
> everything else.
>
> Thanks for all the help.
>
> On Thu, May 10, 2012 at 10:36 AM, Ted Nugent <tednugent73 at gmail.com>wrote:
>
>> It typically takes 3 days to 4 months for the UCCS team to respond so i
>> would not hold my breath waiting on them although they always seem to
>> respond eventually.
>> If you are doing a fresh build then you should not need the intermediary
>> licenses, similar as you do with Unity Connection you'll send licensing the
>> old CM license files, new MAC address, upgrade PAK received from PUT and
>> the upgrade SO# and they will cut you new licenses based off the new MAC.
>> The only thing that is obtained from the PUT is the actual application
>> license which basically just enable 8.x. Everything else will come over
>> from your old cluster and you will just bolt on the addon CUWL DLUs to that.
>>
>> I would assume the same for CER however I have not had the joy of working
>> with licensing recently on that product.
>>
>> The CUC HA Ports were require for CUC 7.x however now once you install
>> the HA licensing on the HA node (make sure you use the HA MAC) all the
>> ports magically appear so the HA ports licencing is no longer required.
>> HTH Ted
>>
>>
>>
>> On Thu, May 10, 2012 at 10:27 AM, Erick Wellnitz <ewellnitzvoip at gmail.com
>> > wrote:
>>
>>> I really apologize for all the upgrade/CUWL/PUT questions but it's a
>>> minefield if you haven't done it in years.
>>>
>>> Waiting to hear back on my UCSS for UCCX but menawhile I'm trying to
>>> plan out the rest of my PUT order.
>>>
>>> Going from CUCM 6.1.3 to 8.6 - do I need to order all the intermediary
>>> upgrades as well?  I'm not really 'upgrading' but installing 8.6 fresh.
>>> I'm sure there's a licensing minefield to navigate on this which will
>>> require me to submit a multitude of licensing requests and hope they get
>>> the entire chain right.
>>>
>>> CER 2.0 to 8.6 - Same question.  I know I can't upgrade directly but I'm
>>> doing a clean install as well.
>>>
>>> I have a handle on Unity/Uconn thanks to the group, particularly Ted!
>>> Well, one thing.  What is the difference between HA ports and regular ports
>>> and do I need them for a HA deployment?
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> 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/20120510/40b5512e/attachment.html>