-
Notifications
You must be signed in to change notification settings - Fork 17
Description
Automate the update of all registered MAC address records in Redirect and
Provisioning Service (RPS) during a NethVoice module migration, allowing phones
to be migrated to the new instance using a different hostname without manual
record updates.
Purpose and Motivation
Currently, when migrating the NethVoice module, if the new instance uses a
different FQDN (hostname) than the previous one, phones previously provisioned
cannot automatically obtain their updated configuration.
Administrators are required to manually remove and re-add each phone’s
provisioning entry in NethVoice to allow the update of the record in the RPS.
This is a time-consuming and error-prone process that could be streamlined.
Automating this update would considerably simplify the migration process and
reduce both workload and risk of misconfiguration.
Proposed Solution
Implement an automated process that updates the RPS records for all MAC
addresses registered in the migrating instance, setting them to the
provisioning server address of the new NethVoice instance, even if it has a new
hostname. After this update, a simple hardware reset—performed either by the
installer or the phone user—will be sufficient for phones to automatically
retrieve the new configuration from the provisioning server associated with the
new hostname.
Alternative Solutions
- Continue with the current process: manually remove and re-add phones in
NethVoice and RPS, then manually reset the phones. - Require that the new NethVoice instance always uses the same FQDN as the
previous one to avoid changing provisioning server addresses.
Additional Context
Currently, changing the hostname/FQDN during migration creates extra workload
and risk, as all phones must be re-provisioned individually. Automating the
update of RPS records will make the migration process much smoother and more
reliable, especially for larger installations.
Metadata
Metadata
Assignees
Labels
Type
Projects
Status