NethVoice: SIP port migration misses aliases and local-address trunks #8271

Steps to reproduce

1. Configure a NethVoice instance with an additional SIP domain route pointing to its UDP listener.
2. Configure an inbound trunk whose destination uses another address assigned to the node, rather than the node VPN address.
3. Run the update that moves the SIP UDP listener to a new port.

Expected behavior

All matching UDP destinations belonging to the instance follow the new listener, including additional domains and trunks using other assigned local addresses. Unrelated destinations and explicit TCP/TLS routes remain unchanged. Repeating the migration also repairs installations whose port was moved by an earlier update.

Actual behavior

The public update code leaves two cases uncovered:

• 90repoint_sip_proxy invokes configuration code that updates only NETHVOICE_HOST, so additional domain routes are omitted.
• 91repoint_proxy_trunks matches only the node VPN address, so it skips trunks pointing to another address assigned to the same node even when the old instance port matches.

Those destinations retain the old UDP port. Reloading the proxy cannot fix saved destinations that were never rewritten.

Components

NethVoice SIP-port migration in ns8-nethvoice.

See also

• Primary route refresh
• Trunk destination migration

Moved from nethesis/ns8-nethvoice#1090.