<div dir="ltr">Was the 8.x cluster mixed-mode? If so, you just need to get the USB tokens they used. Outside of that, not much you can do without manually deleting ITLs. Any automation program is going to require a valid user with CTI control of the phone.<div><br></div><div>Technically some of the phone models have a way to delete the ITL/CTL via SSH but that would requires setting up an SSH user/enabling SSH on the previous cluster.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Mar 2, 2015 at 9:48 AM, Ryan Huff <span dir="ltr"><<a href="mailto:ryanhuff@outlook.com" target="_blank">ryanhuff@outlook.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div dir="ltr">About 1K of 79xx phones on a ccm 8.X going to ccm 10.5. So CTL/ITL is an issue. There are lots of ways to solve this with access to the previous phone system, I know.<br><br>The catch for me is, I DO NOT have access to the previous phone system or the previous phone certificates (would be so much easier if I did, I know).<br><br>Anyone have any dark magic I can script though the SSH / Web Server client on the phone that doesn't require me to bind to a valid ccm user from the previous system or in any other way, reference the previous system?<br><br>Any other ideas?<br><br>Thanks,<br><br>Ryan<br> </div></div>
<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></blockquote></div><br></div>