<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Not having an ITL will prevent https services from working, correct. I'm confident that if you changed your secure service URLs to be http:// instead of https:// EM and other services will still work fine. If you are using your production cluster for staging this may not be ideal. IMO you need a staging server where you can set the parameter and upgrade the phones as needed.<div><br><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div>-Ryan</div></span>
</div>
<br><div><div>On Feb 20, 2012, at 12:08 PM, Jonathan Charles wrote:</div><br class="Apple-interchange-newline">When you change that you get a pretty scary message:<div><br></div><div>Prepare Cluster for Rollback to pre 8.0: Enable this option ONLY if you are preparing to rollback your cluster to a pre 8.0 Cisco Unified Communications Manager release. Phone services (for example, extension mobility) will NOT work when this parameter is set to True, however, users will be able to continue making and receiving basic phone calls. IMPORTANT: You must restart the following services on all nodes, in the order described, immediately after setting this parameter to True: First, restart the Trust Verification Service (TVS) on all nodes; next, restart the TFTP service on all nodes that have TFTP activated; last, return to the Enterprise Parameters Configuration window and click the Reset button to reset all phones. When those three steps are completed and have been performed in the specified order, the cluster will be ready for rollback.</div>
<div><br></div><div>Some of us like Extension Mobility...</div><div><br></div><div><br></div><div>Jonathan<br><br><div class="gmail_quote">On Mon, Feb 20, 2012 at 10:16 AM, Ryan Ratliff <span dir="ltr"><<a href="mailto:rratliff@cisco.com">rratliff@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">You should set the rollback parameter on your staging servers so the phones don't get an ITL to begin with.<div>
<span class="HOEnZb"><font color="#888888"><br><div>
<span style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:auto;font-style:normal;font-weight:normal;line-height:normal;border-collapse:separate;text-transform:none;font-size:medium;white-space:normal;font-family:Helvetica;word-spacing:0px"><div>
-Ryan</div></span>
</div></font></span><div><div class="h5">
<br><div><div>On Feb 19, 2012, at 11:59 AM, Jonathan Charles wrote:</div><br>That was it, I had them erase the ITL and the phone reg'd and picked up the timezone... yay Cisco.<div><br></div><div>So, our plan was to stage phones to our CCM before sending them to remote customer sites so they will have the correct load on them (so they can just plug em in), I will need to change the process to include erasing the ITL.</div>
<div><br></div><div><br></div><div>Jonathan<br><br><div class="gmail_quote">On Sun, Feb 19, 2012 at 9:59 AM, 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">Based on this and your previous post I suspect an ITL issue. Are your phones are downloading signed config files AND trusting them?<div><a href="https://supportforums.cisco.com/docs/DOC-17679" target="_blank">https://supportforums.cisco.com/docs/DOC-17679</a></div>
<div><br></div><div>/wes</div><div><br><div><div><div><div>On Feb 19, 2012, at 12:05 AM, Jonathan Charles wrote:</div><br>Just some more info, a phone runnning 8.3.2 shows the correct timezone; upgraded them to 8.3.3 and it still had the timezone; upgraded to 9.2.1 and it retained it.<div>
<br></div><div>Tried downgrading the other phones, they wouldn't take the firmware (made no effort to download it); also noticed that the other phones are only registered to the Publisher. All phones are in the same device pool.</div>
<div><br></div><div><br></div><div>J<br><div><br><div class="gmail_quote">On Sat, Feb 18, 2012 at 9:57 PM, Jonathan Charles <span dir="ltr"><<a href="mailto:jonvoip@gmail.com" target="_blank">jonvoip@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">CUCM 8.6, phones running 9.2.1; Cisco 7900s are not picking up the timezone from CCM, so they are showing GMT.<div><br>
</div><div>Timezone is configured for EST, but phones are blank (on their web pages) for timezone... </div><span><font color="#888888">
<div><br></div><div><br></div><div>Jonathan</div>
</font></span></blockquote></div><br></div></div></div></div>
_______________________________________________<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></blockquote></div><br></div>
_______________________________________________<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></blockquote></div><br></div>
</div><br></div></body></html>