NethVoice: Proxy IP not updated after moving instance within the same cluster

[mgarra]

Description

When moving instances within the same cluster, from a leader node to a worker node, using the “Move” function, a proxy IP update issue occurs.

Specifically, for all Extensions:

• associated with physical phones (both provisionable and non-provisionable)
• associated with Mobile Apps

the Advanced settings in FreePBX still contain the previous Proxy IP (the one from the source node).

The same behavior also affects VoIP trunks configured with a Proxy:
after moving the instance, the Proxy IP is not updated and still points to the previous node.

Steps to reproduce

1. Cluster with a leader node and one or more worker nodes
2. An active instance running on the leader node
3. Extensions (physical phones, Mobile Apps) and VoIP trunks configured with a Proxy
4. Move the instance from the leader node to a worker node using the “Move” function
5. Check the Advanced settings of Extensions and trunks in FreePBX

Expected behavior

After moving the instance:

• the Proxy IP should be automatically updated
• Extensions and trunks should point to the Proxy of the new node

Actual behavior

• The Proxy IP remains set to the previous node
• A manual intervention is required to fix the configuration

Impact

• Possible phone registration issues
• Malfunctions on Mobile Apps
• VoIP trunks continuing to use an incorrect Proxy

[margit86]

Additional note

The same issue also occurs during backup restore operations.

When an instance is restored from a backup on a different node, the Proxy IP configured in FreePBX is not updated accordingly. As a result, Extensions (physical phones, Mobile Apps) and VoIP trunks continue to reference the Proxy IP of the original node, requiring manual correction after the restore process.

This makes the problem reproducible not only during instance moves, but also during disaster recovery or migration scenarios involving backups.

[Stell0]

Test cases

Test case 1 - Move instance updates Proxy IP for extensions and PJSIP trunks

• Preconditions

  • NS8 cluster with 1 leader + 1 worker

  • NethVoice instance running on leader

  • At least:

    • 1 extension configured with Proxy (leader Proxy IP A)
    • 1 PJSIP trunk configured with Proxy (leader Proxy IP A)

• Steps

  1. From Cluster UI, Move the NethVoice instance from leader → worker
  2. Open FreePBX on the moved instance
  3. Check the extension Advanced settings (proxy/outbound proxy)
  4. Check the PJSIP trunk proxy/outbound proxy settings
  5. Verify registration and place a test call

• Expected

  • Extension Proxy IP is updated to worker Proxy IP (B)
  • PJSIP trunk Proxy IP is updated to B
  • Extension registers successfully
  • Calls work without manual changes

---

Test case 2 - Restore from backup updates Proxy IP for extensions and PJSIP trunks

• Preconditions

  • NS8 cluster with 1 leader + 1 worker

  • Backup of a NethVoice instance created on leader (Proxy IP A)

  • Backup contains:

    • 1 extension with Proxy
    • 1 PJSIP trunk with Proxy

• Steps

  1. Restore the backup on the worker node
  2. Open FreePBX on the restored instance
  3. Check the extension Advanced proxy/outbound proxy field
  4. Check the PJSIP trunk proxy/outbound proxy field
  5. Verify registration and place a test call

• Expected

  • Extension Proxy IP is automatically updated to worker Proxy IP (B)
  • PJSIP trunk Proxy IP is automatically updated to B
  • Extension registers successfully
  • Calls work without manual intervention