[cisco-voip] SBD and staging phones

[Ryan Ratliff (rratliff)]

If the staging server is just for upgrading phone firmware then just set the rollback parameter so phones will get an empty ITL.

-Ryan

On Oct 28, 2014, at 1:57 PM, Brian Meade <bmeade90 at vt.edu<mailto:bmeade90 at vt.edu>> wrote:

There is https://supportforums.cisco.com/document/60716/migrating-ip-phones-between-clusters-cucm-8-and-itl-files that describes each method you can use.

Bulk Certificate Export/Consolidate/Import is the preferred method.

Brian

On Tue, Oct 28, 2014 at 1:16 PM, Heim, Dennis <Dennis.Heim at wwt.com<mailto:Dennis.Heim at wwt.com>> wrote:
There is a process to trust the certificates between cluster via the bulk certificate tool/function.

Dennis Heim | Collaboration Solutions Architect
World Wide Technology, Inc. | +1 314-212-1814<tel:%2B1%20314-212-1814>
<image001.png><https://twitter.com/CollabSensei>
<image002.png><image003.png><tel:+13142121814><image004.png>


From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net>] On Behalf Of Erick Wellnitz
Sent: Tuesday, October 28, 2014 12:08 PM
To: cisco-voip
Subject: [cisco-voip] SBD and staging phones

I remember back when I did a v6 to v8.6 migration and SBD would cause some issues going back and forth between the clusters.

Would the same be true taking a phone from one 8.6 cluster and moving it to another 8.6 cluster?

I'm looking at remotely staging and upgrading firmware on 1000 phones to save time placing them and running TAPS.

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip


_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20141028/6237547a/attachment.html>