Device Migration Strategies
Most of our customers are coming in with hundreds of thousands of devices in the field they want to migrate to Phonism. It’s daunting but This document briefly describes common scenarios our customers have brought to us and the strategies used to migrate these devices to Phonism.
Of course, one size does not fit all. If your deployment does not fit any of these scenarios, feel free to reach out to our Support team for help!
Considerations for all Scenarios
Utilizing Manufacturer Redirect Services
Most of our supported manufacturers provide a redirection service. Devices registered with the service are automatically redirected to the provisioning server of your choice when the phone is factory reset
For services we integrate with, Phonism automatically handles registering the devices for redirection once added to Phonism
See our documentation on Zero Touch Provisioning for more information
- Zero Touch Provisioning (ZTP)
DHCP Option 66
If you have support from the on-site network administrator, DHCP Option 66 could be utilized to redirect the phones to Phonism for provisioning
Retaining Existing Configurations
If maintaining existing device configurations is a requirement, you can import existing configurations into Phonism.
Phonism cannot extract configuration out of your devices. You need access to the configuration files.
Scenarios
No Existing Provisioning System
Assumptions:
Your devices were configured manually
You have no remote access to the device
Migration Strategies:
Per-device, modify their configurations in the Phone's Web GUI to redirect them to Phonism for provisioning
This may require cooperation from someone on-site to do this task or provide remote access
Setup DHCP Option 66 on the network so that the phones are told to provision from Phonism
Utilize manufacturer redirect services and our integrations so that phones are automatically directed to Phonism for provisioning after being factory reset
See our documentation on Zero Touch Provisioning for more information
Existing Provisioning System
Assumptions:
You have an existing provisioning system that your devices are periodically accessing for configuration
You have the ability to modify the configuration files in this system
Migration Strategy:
Utilize your existing provisioning system to redirect the devices to our service.
Modify the configurations such that on their next provision, they will be reconfigured to provision from Phonism.
Broadworks DMS using Phonism's Broadworks Integration
Assumptions:
The devices in question are periodically provisioning from DMS
A Broadworks integration is setup in Phonism
Your Broadworks hierarchy and device records have been synced from Broadworks into Phonism
Migration Strategy:
Utilize our automated migration tool. This tool does the following:
Reconfigures your device(s) to provision from Phonism
Tells the phone to reboot and pull this new configuration from DMS (This will be the last contact to DMS)
Once the Phone reprovisions and the system confirms that it is communicating with Phonism, the Phone's existing configuration will be imported from DMS into Phonism
After import, Phonism will serve configuration to the device on it's next provision
Refer to our documentation for more details
Broadworks DMS without using Phonism's Broadworks Integration
Assumptions:
The devices in question are periodically provisioning from DMS
Inside DMS, you can modify the Device Profile Templates of the devices to be migrated
Migration Strategy:
Utilize your existing provisioning system to redirect the devices to our service.
Modify the Device Profile Templates such that on their next provision, they will be reconfigured to provision from Phonism