<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
The ES patches were always there for 4.x and the periodic SR releases were pretty much ES patches that got some extra testing. With 5.x and later we don't have SRs any longer, and you will see ES patches released to cisco.com after they have been out for 4 weeks (I think) with no major bugs filed against them. ES patches do get tested and the "pre-builds not mainstream, ie test at your own risk" thought is nowhere near applicable. If you are running any appliance based version of CUCM you should get used to the idea of running an ES version because you will have to at some point. <div><br><div> <p style="margin: 0.0px 0.0px 0.0px 0.0px"><font face="Helvetica" size="3" style="font: 12.0px Helvetica">-Ryan</font></p> </div><br><div><div>On Aug 12, 2008, at 1:13 AM, James Buchanan wrote:</div><br class="Apple-interchange-newline"> <div class="Section1"><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"; color:#1F497D">It depends. I have a customer who uses Extension Mobility extensively and it locks everything up (per them). TAC told them to install the ES. While I don’t go out and download the latest ES (or even SR) necessarily, Cisco does support them and release them for a reason. I do not recall seeing ESes hardly at all for 4.x, so I would assume this ES is significant enough to demand a closer look.<o:p></o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"; color:#1F497D"><o:p> </o:p></span></p> <div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in"><p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> cisco-voip-bounces@puck.nether.net [<a href="mailto:cisco-voip-bounces@puck.nether.net">mailto:cisco-voip-bounces@puck.nether.net</a>] <b>On Behalf Of </b>Darren<br> <b>Sent:</b> Monday, August 11, 2008 11:07 PM<br> <b>Cc:</b> Cisco VoIP<br> <b>Subject:</b> Re: [cisco-voip] CM stable @ 6.1.2.1106?<o:p></o:p></span></p> </div><p class="MsoNormal"><o:p> </o:p></p> <div><p class="MsoNormal">So what are everybodies thoughts on running an ES? as 1106-1 is an ES. My thoughts are ES are "pre-builds not mainstream, i.e. test are your own risk". 6.1.2.1000-13 is the main release. I've seen a number of these rolled out (main release 1000-13) and only one has a problem which required a cluster reboot, the issue didn't affect call processing but did affect management (changing settings, etc).<o:p></o:p></p> </div> <div><p class="MsoNormal"> <o:p></o:p></p> </div> <div><p class="MsoNormal">Cheers,<o:p></o:p></p> </div> <div><p class="MsoNormal"> <o:p></o:p></p> </div> <div><p class="MsoNormal">D<o:p></o:p></p> </div> <div><p class="MsoNormal"> <o:p></o:p></p> </div> <div><p class="MsoNormal"> <o:p></o:p></p> </div> <div><p class="MsoNormal"><br> <br> <o:p></o:p></p> </div> <div><p class="MsoNormal"><span class="gmailquote">On 8/12/08, <b>Steve G</b> <<a href="mailto:smgustafson@gmail.com">smgustafson@gmail.com</a>> wrote:</span> <o:p></o:p></p> <div> <div><p class="MsoNormal">My first install with CM6 is on Business Edition running 6.1.1.3000-2. My BAT experience was very painful. I first attempted to insert phones with users with 1 DN and 1 Intercom. It would not let me insert the default activated device on the intercom line. The syntax is SEP<mac address> but it does not recognize the device name as it is not valid. I also could not insert the owner userid of the phone because it to was not valid. I also could not insert the primary user device for mobility. so, inserting phones with users is something that really needs to be tested and fixed in my opinion. I went back to the old way of importing phones/users with just the user ID and the DN. that seemed to work as long as you didn't use any of the new fields. So I wanted to add 1 intercom using the "add intercom" tab in the bat.xls spreadsheet. It was great except it did not have a field for the intercom default activated device, which is mandatory. so once the phones were in I ended up creating a new spreadsheet for just phones, and imported the same fields for my DN and Intercom and this time it all seemed to import, except it deleted the device association of my users. I spent WAY too much time on this ordeal. I was running in circles, so I got to a point where I started updating 100 phones and users by hand. That took me an afternoon to get everything right but I figured I would have been messing with BAT for much longer.<br> <o:p></o:p></p> </div> <div><p class="MsoNormal">Steve<o:p></o:p></p> </div> <div> <div><p class="MsoNormal"> <o:p></o:p></p> </div> <div><p class="MsoNormal"><br> <o:p></o:p></p> </div> <div><p class="MsoNormal">On Mon, Aug 11, 2008 at 3:43 PM, STEVEN CASPER <<a href="mailto:SCASPER@mtb.com" target="_blank">SCASPER@mtb.com</a>> wrote:<o:p></o:p></p><p class="MsoNormal">One was CSCso91969 - Insert of phones,RDP fails to insert CFA<br> parameters. We still have a TAC case open I believe, the work around did<br> not work for us.<br> <br> >>> Rob Gilreath <<a href="mailto:rgilreath@hbs.net" target="_blank">rgilreath@hbs.net</a>> 8/11/2008 5:42 PM >>><o:p></o:p></p> <div> <div><p class="MsoNormal"><br> Can you guys that have seen issues with the BAT give a quick summary?<br> I've not seen any yet myself, but knowing of them ahead of time would<br> be nice…<br> <br> <br> <a href="mailto:From%3Acisco-voip-bounces@puck.nether.net" target="_blank">From:cisco-voip-bounces@puck.nether.net</a><br> [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a>] On Behalf Of STEVEN<br> CASPER<br> Sent: Monday, August 11, 2008 4:39 PM<br> To: Erik Goppel; Jason Aarons (US)<br> Cc: Cisco VoIP<br> Subject: Re: [cisco-voip] CM stable @ 6.1.2.1106?<br> <br> <br> <br> Got to agree with the BAT comment. Due to BAT problems we discovered<br> during testing we had to put the upgrade to 6.1.2 on hold. We are<br> rolling out a 100-200 or so phones a week so the proper operation of BAT<br> is a big deal to us.<br> <br> <br> <br> Steve<br> <br> >>> "Erik Goppel" <<a href="mailto:egoppel@gmail.com" target="_blank">egoppel@gmail.com</a>> 8/11/2008 5:04 PM >>><br> <br> got 2 customers over 8000 phones running stable. one customer running<br> Unity Connection with 6400 VM`s at the same version also stable.<br> <br> BAT is a total different story, i`d suggest testing BAT to see if you<br> can work with it.<br> <br> <br> <br> good luck,<br> <br> <br> <br> Erik Goppel<br> <br> <br> <br> Dimension Data Netherlands<br> <br> <br> <br> <br> <br> On Mon, Aug 11, 2008 at 10:45 PM, Jason Aarons (US)<br> <<a href="mailto:jason.aarons@us.didata.com" target="_blank">jason.aarons@us.didata.com</a>> wrote:<br> <br> I've had no issues with 6.1.2-1000-13 in regards to stability. Most<br> installs have been 100-500 handsets SCCP 7941/7961. Larger 4000-12,000<br> are staying with 4.1.3sr7 (they have a longer lifecycle between upgrades<br> due to UCCE, etc). 6.1.2-1000-13 has some bugs but end users don't<br> notice. I would call it General Deployment release.<br> <br> <a href="mailto:From%3Acisco-voip-bounces@puck.nether.net" target="_blank">From:cisco-voip-bounces@puck.nether.net</a><br> [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a>] On Behalf Of Scott Voll<br> Sent: Monday, August 11, 2008 3:43 PM<br> To: Cisco VoIP<br> Subject: [cisco-voip] CM stable @ 6.1.2.1106?<br> <br> <br> <br> I'm putting a new / upgraded CM 6.1.2 into production this weekend.<br> Should I be running 6.1.2.1000-13 or 1106-1? any issues with either<br> one?<br> <br> <br> <br> Thanks<br> <br> <br> <br> Scott<br> <br> Disclaimer: This e-mail communication and any attachments may contain<br> confidential and privileged information and is for use by the designated<br> addressee(s) named above only. If you are not the intended addressee,<br> you are hereby notified that you have received this communication in<br> error and that any use or reproduction of this email or its contents is<br> strictly prohibited and may be unlawful. If you have received this<br> communication in error, please notify us immediately by replying to this<br> message and deleting it from your computer. Thank you.<br> <br> <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> <br> ************************************This email may contain privileged<br> and/or confidential information that is intended solely for the use of<br> the addressee. If you are not the intended recipient or entity, you are<br> strictly prohibited from disclosing, copying, distributing or using any<br> of the information contained in the transmission. If you received this<br> communication in error, please contact the sender immediately and<br> destroy the material in its entirety, whether electronic or hard copy.<br> This communication may contain nonpublic personal information about<br> consumers subject to the restrictions of the Gramm-Leach-Bliley Act and<br> the Sarbanes-Oxley Act. You may not directly or indirectly reuse or<br> disclose such information for any purpose other than to provide the<br> services for which you are receiving the information.There are risks<br> associated with the use of electronic transmission. The sender of this<br> information does not control the method of transmittal or service<br> providers and assumes no duty or obligation for the security, receipt,<br> or third party interception of this<br> transmission.************************************<br> ************************************<br> This email may contain privileged and/or confidential information that is intended solely for the use of the addressee. If you are not the intended recipient or entity, you are strictly prohibited from disclosing, copying, distributing or using any of the information contained in the transmission. If you received this communication in error, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. This communication may contain nonpublic personal information about consumers subject to the restrictions of the Gramm-Leach-Bliley Act and the Sarbanes-Oxley Act. You may not directly or indirectly reuse or disclose such information for any purpose other than to provide the services for which you are receiving the information.<br> There are risks associated with the use of electronic transmission. The sender of this information does not control the method of transmittal or service providers and assumes no duty or obligation for the security, receipt, or third party interception of this transmission.<br> ************************************<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> <o:p></o:p></p> </div> </div> </div><p class="MsoNormal"><o:p> </o:p></p> </div> </div><p class="MsoNormal" style="margin-bottom:12.0pt"><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><o:p></o:p></p> </div><p class="MsoNormal"><o:p> </o:p></p> </div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">_______________________________________________</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">cisco-voip mailing list</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a></div> </div><br></div></body></html>