I'm not aware of the specifics of the doc bug Brian referenced but the original question sounds less like bulk cert import and more like a publisher recovery. Can you provide a bit more details on what you mean by "promote a new publisher to existing phones"?
-Ryan On Nov 3, 2014, at 11:33 AM, Brian Meade <bmead...@vt.edu<mailto:bmead...@vt.edu>> wrote: There shouldn't be a need to restart any subscribers. Should just need to restart TVS on all the nodes at most. On Mon, Nov 3, 2014 at 10:19 AM, Haas, Neal <nh...@co.fresno.ca.us<mailto:nh...@co.fresno.ca.us>> wrote: All subs will need to be rebooted, hence the re-registration of all phones. Neal Haas From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net<mailto:cisco-voip-boun...@puck.nether.net>] On Behalf Of TG Sent: Saturday, November 01, 2014 7:23 PM To: cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net> Subject: [cisco-voip] CUCM 8.6 promotion of new pub Hi all, In order to promote a new publisher to existing phones, cert consolidation is required on existing cluster to authenticate the new publisher and be able to register successfully. Since this consolidation step (even without resetting the service) generates a reset on all phones of existing cluster, is there a way to control this behavior in order to prohibit 20 or 30,000 phones from resetting all at the same time? _______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net> https://puck.nether.net/mailman/listinfo/cisco-voip _______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net> https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
