Description
A new migration procedure has been tested to avoid manually resetting each phone when migrating from NethVoice 14 and the migration involves a FQDN change from the old NethVoice to the new one.
The goal is to allow the migration to be managed entirely from the old and new NethVoice interfaces, without requiring direct access to every physical phone.
Proposed migration flow
-
Start the migration procedure.
-
Change the FQDN of the NethVoice 14 instance provisioning service.
- At the moment, this can only be done from the underlying system
- To do that from NethVoice interface you must created the DNS record of NethVoice FQDN on NethServer 7.
- This DNS record must be removed before finalizing the migration.
-
Reboot all phones from the NethVoice 14 interface.
-
The phones register on the new NethVoice instance with a partial configuration.
- For example, some parameters such as the proxy may still be missing.
-
Finalize the migration.
-
Reconfigure all phones from the NethVoice interface so that they receive the complete configuration.
Expected behavior
The migration procedure should support this workflow officially, allowing phones to move to the new NethVoice instance without requiring a manual reset on each device.
After the migration is finalized and phones are reconfigured from the interface, all devices should receive the complete provisioning configuration and register correctly.
Actual behavior
The procedure is currently possible only with manual steps and workarounds:
- The NethVoice 14 FQDN must be changed manually.
- A temporary DNS record must be created on NethServer 7.
- The temporary DNS record must be removed before finalizing the migration.
- Phones initially register with only a partial configuration.
- A second provisioning step is required after finalization.
Benefit
This approach would significantly simplify migrations where many physical phones are involved.
Instead of accessing each phone individually to perform a factory reset, the administrator can complete the migration by working only from the old and new NethVoice systems.
Description
A new migration procedure has been tested to avoid manually resetting each phone when migrating from NethVoice 14 and the migration involves a FQDN change from the old NethVoice to the new one.
The goal is to allow the migration to be managed entirely from the old and new NethVoice interfaces, without requiring direct access to every physical phone.
Proposed migration flow
Start the migration procedure.
Change the FQDN of the NethVoice 14 instance provisioning service.
Reboot all phones from the NethVoice 14 interface.
The phones register on the new NethVoice instance with a partial configuration.
Finalize the migration.
Reconfigure all phones from the NethVoice interface so that they receive the complete configuration.
Expected behavior
The migration procedure should support this workflow officially, allowing phones to move to the new NethVoice instance without requiring a manual reset on each device.
After the migration is finalized and phones are reconfigured from the interface, all devices should receive the complete provisioning configuration and register correctly.
Actual behavior
The procedure is currently possible only with manual steps and workarounds:
Benefit
This approach would significantly simplify migrations where many physical phones are involved.
Instead of accessing each phone individually to perform a factory reset, the administrator can complete the migration by working only from the old and new NethVoice systems.