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.<div>
<br><div><br><br><div class="gmail_quote">On Thu, May 10, 2012 at 2:59 PM, Wes Sisk <span dir="ltr"><<a href="mailto:wsisk@cisco.com" target="_blank">wsisk@cisco.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word"><div>I believe Erick got his question answered.</div><div><br></div><div>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 </div>
<div>ucss-support[at]<a href="http://external.cisco.com" target="_blank">external.cisco.com</a>.</div><div><a href="http://www.cisco.com/en/US/solutions/collateral/ns340/ns394/ns165/ns737/net_presentation0900aecd8063dc83.pdf" target="_blank">http://www.cisco.com/en/US/solutions/collateral/ns340/ns394/ns165/ns737/net_presentation0900aecd8063dc83.pdf</a><br>
<div><br></div><div>It appears some folks may be contacting tac[at]<a href="http://cisco.com" target="_blank">cisco.com</a> or cs-support[at]<a href="http://cisco.com" target="_blank">cisco.com</a> 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.</div>
<div><br></div><div>Regards,</div><div>Wes</div><div><div class="h5"><div><br><div><div>On May 10, 2012, at 11:51 AM, Erick Wellnitz wrote:</div><br><div>Absolutely perfect. </div>
<div> </div>
<div>Now to wait for the UCSS team...at least I'll be able to get started on everything else.</div>
<div> </div>
<div>Thanks for all the help. <br><br></div>
<div class="gmail_quote">On Thu, May 10, 2012 at 10:36 AM, Ted Nugent <span dir="ltr"><<a href="mailto:tednugent73@gmail.com" target="_blank">tednugent73@gmail.com</a>></span> wrote:<br>
<blockquote style="BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px 0.8ex;PADDING-LEFT:1ex" class="gmail_quote">
<div>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.</div>
<div>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.</div>
<div><br></div>
<div>I would assume the same for CER however I have not had the joy of working with licensing recently on that product.</div>
<div><br></div>
<div>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.</div>
<div>HTH Ted</div>
<div><br></div><br><br>
<div class="gmail_quote">On Thu, May 10, 2012 at 10:27 AM, Erick Wellnitz <span dir="ltr"><<a href="mailto:ewellnitzvoip@gmail.com" target="_blank">ewellnitzvoip@gmail.com</a>></span> wrote:<br>
<blockquote style="BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px 0.8ex;PADDING-LEFT:1ex" class="gmail_quote">
<div>I really apologize for all the upgrade/CUWL/PUT questions but it's a minefield if you haven't done it in years.</div>
<div> </div>
<div>Waiting to hear back on my UCSS for UCCX but menawhile I'm trying to plan out the rest of my PUT order.</div>
<div> </div>
<div>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.</div>
<div> </div>
<div>CER 2.0 to 8.6 - Same question. I know I can't upgrade directly but I'm doing a clean install as well.</div>
<div> </div>
<div>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? </div>
<div> </div>
<div> </div>
<div> </div>
<div> </div><br>_______________________________________________<br>cisco-voip mailing list<br><a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br></blockquote></div><br></blockquote></div><br>
_______________________________________________<br>cisco-voip mailing list<br><a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
</div><br></div></div></div></div></div></blockquote></div><br></div></div>