We experienced a strange issue this morning. We updated all SIP extensions in Zero Config after a minor change to the default model template. I don’t believe the nature of the change to be pertinent, but it was to add a couple of pcodes to set up distinctive rings for calls coming in a certain inbound route. None of the templates or policies (model, global, etc.) define a single VMPK (other than extension board ones) and when we updated all extensions en masse, anyone who had locally programmed VMPKs had them overwritten to default settings.
The management team at the company was really upset, understandably, and we can’t explain why it happened or, therefore, prevent it from happening again. We have tested and have been unable to repeat the issue. Not wanting to impact the whole company (50 extensions/handsets) we have been pushing updates to one or two phones and the issue hasn’t occurred again.
Has anyone else run into this? Is there a setting somewhere we can employ to prevent local programming (VMPKs in particular) from being wiped by a model template or global policy? TIA!