As to the original question, I have heard good things about 8.5. I am a recent 8.0 upgrade myself (from the abandoned no man's land of 4.1), and haven't run into any bugs yet that are showstoppers. (one bug through RTMT keeps telling me that a cisco service tried to write to a file and was denied. In trolling the bug toolkit, it seems that the service DOES write to the file just fine, but for some reason, the error is raised). <br>
<br><div class="gmail_quote">On Wed, Feb 9, 2011 at 1:41 PM, Bill Riley <span dir="ltr"><<a href="mailto:bill@hitechconnection.net">bill@hitechconnection.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
All gateways are H.323 or SIP except for a few VG224's. Yes I am going to<br>
setup a Intercluster Trunk.<br>
<br>
Yes on the IOS question. I only need transcoding at the site that has UCCX.<br>
<div class="im"><br>
-----Original Message-----<br>
From: Jason Aarons (US) [mailto:<a href="mailto:jason.aarons@us.didata.com">jason.aarons@us.didata.com</a>]<br>
Sent: Wednesday, February 09, 2011 1:32 PM<br>
To: Bill Riley; 'Ed Leatherman'<br>
Cc: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
</div><div><div></div><div class="h5">Subject: RE: [cisco-voip] 8.0 or 8.5<br>
<br>
I hope you have H323/SIP dial peers and not MGCP, or are you setting up a<br>
Intercluster Trunk, etc?<br>
<br>
Is your IOS high enough to have the SCCP 8.0+ keyword for sccp resoucrce<br>
registration (mtp, cfb, transcoding) ?<br>
<br>
I've done what your doing before, it has it's own set of headaches. I once<br>
had two clustesr, one got upgraded and everybody got moved, other got<br>
upgraded, everybody moved, never really stopped as back in the 4x days we<br>
had so many bugs you didn't want to just upgrade production..<br>
<br>
-----Original Message-----<br>
From: <a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a><br>
[mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>] On Behalf Of Bill Riley<br>
Sent: Wednesday, February 09, 2011 8:54 AM<br>
To: 'Ed Leatherman'<br>
Cc: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
Subject: Re: [cisco-voip] 8.0 or 8.5<br>
<br>
I am at CUCM 6.1 and UCCX 5.0. So in order to go to 8.5 I have to go<br>
<br>
UCCX 7.02 ->CUCM7.1 -> UCCX 8.0 -> CUCM 8.0 -> UCCX 8.5 -> CUCM 8.5<br>
<br>
Also the end users are not allowed to have local admin rights so the CAD<br>
will not auto upgrade. Plus we are 24x7 and have thousands of calls an hour.<br>
<br>
<br>
I am thinking about building a new cluster offline of CUCM 8.5 and UCCX 8.5<br>
and then swinging the sites over one by one.<br>
<br>
-----Original Message-----<br>
From: Ed Leatherman [mailto:<a href="mailto:ealeatherman@gmail.com">ealeatherman@gmail.com</a>]<br>
Sent: Tuesday, February 08, 2011 3:09 PM<br>
To: Bill Riley<br>
Cc: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
Subject: Re: [cisco-voip] 8.0 or 8.5<br>
<br>
I have heard through the grapevine that there are a number of defects on CCX<br>
8.0 that are not resolved until 8.5. I've been meaning to spelunk the bug<br>
toolkit to try and identify them for my own planning.<br>
Supposedly the bugs are HA related.<br>
<br>
What is a pain though is you'll need to upgrade UCCX to 8.0, then upgrade<br>
CUCM to 8.0, THEN upgrade UCCX to 8.5 (assuming you are on some version less<br>
than 8 for both apps).<br>
<br>
On Tue, Feb 8, 2011 at 1:01 PM, Bill Riley <<a href="mailto:bill@hitechconnection.net">bill@hitechconnection.net</a>><br>
wrote:<br>
> Has anyone deployed 8.5 yet? I am getting ready to upgrade and<br>
> question if I should go directly to CUCM 8.5 and UCCX 8.5 or stay with<br>
> 8.0 that has been out for a while.<br>
><br>
> _______________________________________________<br>
> cisco-voip mailing list<br>
> <a href="mailto:cisco-voip@puck.nether.net">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>
><br>
<br>
<br>
<br>
--<br>
Ed Leatherman<br>
<br>
<br>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net">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>
Disclaimer:<br>
<br>
This e-mail communication and any attachments may contain confidential and<br>
privileged information and is for use by the designated addressee(s) named<br>
above only. If you are not the intended addressee, you are hereby notified<br>
that you have received this communication in error and that any use or<br>
reproduction of this email or its contents is strictly prohibited and may be<br>
unlawful. If you have received this communication in error, please notify<br>
us immediately by replying to this message and deleting it from your<br>
computer. Thank you.<br>
<br>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net">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></div></blockquote></div><br>