That's some strange behavior since the bulk reset is due to a change in the ITL. Importing CallManager-trust certificates like what happens during a Bulk Certificate Import shouldn't change anything in the ITL.
But it looks like the behavior is documented- https://tools.cisco.com/bugsearch/bug/CSCun32117 I don't know of any workaround to prevent the phones from resetting when the ITL gets updated through the normal processes of adding a node or regenerating a certificate so I'm assuming it should be the same here. Brian On Sat, Nov 1, 2014 at 10:22 PM, TG <techguy...@gmail.com> wrote: > 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 > 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