/
Device Migration

Device Migration

Owned by Adam Moss (Deactivated)
Last updated: 2022 Apr 04 by Daniel Burkholder
3 min read

The device migration process is a 2 part process. First, we import metadata
from Broadworks about the device, like which Broadworks Group or Department it belongs in, which user the device belongs to,
what type/brand device it is. The import process of this metadata is the staging process. Once the staging process is completed,
we then import the device by changing the device’s provisioning server URL within DMS and pointing it to us. 

Staging a Device

  • Device metadata is automatically ingested on a periodic basis from Broadworks and stored at the corresponding level of the Hierarchy.

  • Devices added to Broadworks will be created as Phones at the corresponding Tenant if the following conditions are met:

    • The Device has a MAC address.

    • The Device type is a supported Brand. This is inferred from the DeviceType and/or configuration in Broadworks.

  • We will attempt to automatically detect the Model of the Device upon ingest. A Phone will be created regardless of Model detection.

    • We will also attempt to detect the Model of Phone upon the Phone’s first contact.

  • Once a Phone has been imported and appears in your list of Phones you can begin the Device Migration process

Migrating a Device

  • Select one or more Phones you wish to migrate and select “Migrate”

 

Migration Process

Once triggered the migration begins in the background. This may take some time depending on the number of devices to be migrated. This feature may be limited by the permissions of the Broadworks account provided.

  1. Devices will have their configuration templates changed in Broadworks to set the provisioning server address to us.

  2. Devices will be rebooted to provision once more from Broadworks to get the modified configuration.

  3. Once reprovisioned from Broadworks the Device will start contacting us for configuration for future provisioning.

  4. At this point we consider the device as Migrated and once migrated its configuration can be imported.

  5. Once Migrated device data is imported, the device will be rebooted once more.

Polycom Devices

Polycom devices tend to maintain local configuration over provisioned configuration. 

Your Polycom device may ignore changes to the provisioning URL from DMS if you configured your Polycom’s provisioning URL via the device’s web interface. 

If so you will have to migrate the devices manually either via the phone’s interface or using DHCP option 66.

Device Configuration Importing

Once the device has been migrated we will perform a one-time ingest of Device configuration data from Broadworks. Configuration can be re-ingested at a later date triggered by the User.

NOTE: This feature may be limited by the permissions of the Broadworks account provided.

  • The provisioning credentials for each device on DMS will be changed to a one-time use set so that we can download config from Broadworks.

  • We will download and import configuration data from Broadworks into the database for the given Phone.

    • Configuration importing is handled using our existing Configuration Import tool.

  • VoIP Credential data like username and passwords will be retrieved at this time and the corresponding VoIP Credential records made and bound to the Phone.

Handling of Existing Devices

If a Device to be imported already exists it will be migrated to the newly created Tenant created by the Broadworks integration provided that it is owned by your Account.

Related content