<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Verdana; font-size: 10pt; color: #000000'>I hear ya Jason - I get the same reaction when I mention this list.<br><br>In a world now full of blogs and RSS feeds and forums (and bears, oh my) - the idea of a mailing list seems foreign to some people. It's a powerful tool and the content is top notch as you say.<br><br><br><span><br><span name="x"></span>---<br>Lelio Fulgenzi, B.A.<br>Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>(519) 824-4120 x56354 (519) 767-1060 FAX (ANNU)<br>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>Cooking with unix is easy. You just sed it and forget it. <br> - LFJ (with apologies to Mr. Popeil)<br><span name="x"></span><br></span><br><hr id="zwchr"><b>From: </b>"Jason Gurtz" <jasongurtz@npumail.com><br><b>To: </b>"James Buchanan" <jbuchanan@presidio.com>, "Ryan Ratliff" <rratliff@cisco.com><br><b>Cc: </b>cisco-voip@puck.nether.net<br><b>Sent: </b>Tuesday, July 10, 2012 11:47:54 AM<br><b>Subject: </b>Re: [cisco-voip] CUCM 8.6 licenses disappear on reboot<br><br>Hopefully, resources like this list would be passed on by Cisco (with<br>participation highly encouraged) to the channel at large at your special<br>meetings and events.<br><br>Most times, people I talk to are like, "mailing list, huh?" It is easy to<br>see the participants in this list are the cream of the crop in cisco-voip<br>land. The people we work with are technically OK, but seem unplugged.<br>Meanwhile I come from the networking and server infrastructure side with<br>little voip experience (just trying to catch up. :)<br><br>I hear ya WRT major version releases and being careful. Unfortunately, our<br>reseller regards even the smallest point release as a major upgrade. :( My<br>expectation is something like quarterly or semi-annual upgrades to latest<br>point release or SU; is that a reasonable expectation?<br><br>Cheers,<br><br>~JasonG<br><br>> -----Original Message-----<br>> From: Buchanan, James [mailto:jbuchanan@presidio.com]<br>> Sent: Tuesday, July 10, 2012 11:34<br>> To: Jason Gurtz; Ryan Ratliff<br>> Cc: cisco-voip@puck.nether.net<br>> Subject: RE: [cisco-voip] CUCM 8.6 licenses disappear on reboot<br>> <br>> Speaking from the channel side, I certainly don't take that position.<br>> That said, when a new major release comes out (like 9.0), I exercise<br>> caution and make sure to read the release notes closely as well as the<br>> SRND. With a minor release and a service release, there generally is a<br>> reason for it, such as SU1, so in a situation like this one that's been<br>> described, I would go straight to SU1, still having read the release<br>> notes. A lot of this comes back to experience, and lists like this help<br>> all of us share our experiences and go forth better informed.<br>> <br>> James Buchanan| UC Technology Manager | Presidio South |<br>> Presidio Networked Solutions<br>> 12 Cadillac Dr Ste 130 Brentwood, TN 37027 | jbuchanan@presidio.com<br>> D: 615-866-5729 | F:615-866-5781 www.presidio.com<br>> <br>> <br>> -----Original Message-----<br>> From: cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-<br>> bounces@puck.nether.net] On Behalf Of Jason Gurtz<br>> Sent: Tuesday, July 10, 2012 10:26 AM<br>> To: Ryan Ratliff<br>> Cc: cisco-voip@puck.nether.net<br>> Subject: Re: [cisco-voip] CUCM 8.6 licenses disappear on reboot<br>> <br>> > I'm curious why each of you would do an upgrade to 8.6(2) base when<br>> > SU1 is out there on cisco.com? You still have to order the 8.6(2)<br>> > upgrade via PUT to get the license but there's no reason to do the<br>> > 2-step<br>> upgrade<br>> > when SU1 is the desired destination (or should be).<br>> <br>> I can't speak for any others of course but I can say that our reseller<br>is<br>> staunchly against upgrading...period. The only time they will recommend<br>> an upgrade is when we are actively experiencing a known bug and there is<br>> no workaround. This goes for Cisco VOIP as well as more traditional<br>> IOS/ASAOS devices. There seems to be a perception and intense fear of<br>> "spaghetti code" type issues. e.g. fix this; break that, general<br>> likelihood of regressions, etc... With all the bugs and warts<br>experienced<br>> I'm not sure I would say the fear is unfounded! With no Linux CLI access<br>> to actually fix anything, the fear increases.<br>> <br>> Internally, we are not allowed to do anything unless<br>recommended/approved<br>> by our reseller.<br>> <br>> It would be great if Cisco could (broadly) inform the channel<br>> (VARs/Resellers/Etc...) about the benefits of keeping software<br>up-to-date<br>> vs. the "Mainframe Mentality." Also, best practices WRT testing/QA for<br>> bugs before roll-out...<br>> <br>> Again, that's our situation, hoping it's not a widespread one.<br>> <br>> ~JasonG<br>> <br>> _______________________________________________<br>> cisco-voip mailing list<br>> cisco-voip@puck.nether.net<br>> https://puck.nether.net/mailman/listinfo/cisco-voip<br>> This message w/attachments (message) is intended solely for the use of<br>> the intended recipient and may contain information that is privileged,<br>> confidential or proprietary. If you are not an intended recipient,<br>please<br>> notify the sender, and then please delete and destroy all copies and<br>> attachments. Please be advised that any review or dissemination of, or<br>> the taking of any action in reliance on, the information contained in or<br>> attached to this message is prohibited.<br><br><br>_______________________________________________<br>cisco-voip mailing list<br>cisco-voip@puck.nether.net<br>https://puck.nether.net/mailman/listinfo/cisco-voip<br></div></body></html>