Clear Asterisk network NAT options on migration

Stell0 commented 2 months ago

During the migration from NethVoice 14 on NethServer 7 to NethVoice on NethServer 8, the existing NAT settings from FreePBX (such as public IP and local networks) are carried over. These settings have caused issues because they do not account for all networks from which Asterisk may be accessed (e.g., VPN network or a new green network if it has changed). This leads to specific cases where Asterisk applies NAT incorrectly, causing malfunctions:

Putting a call on hold from a physical phone generates another INVITE, which Asterisk manages with NAT. This confuses the proxy, causing it to contact Asterisk on the public IP rather than the VPN IP.
The hold issue also causes failures in consultative transfer.

Solution: Clear the NAT settings in Asterisk that are carried over during the migration to match that of a clean installation (which does not include these NAT settings by default).

Stell0 commented 2 months ago

Test case 1 (migration):

on ns7 install nethserver-ns8-migration
change /usr/share/nethesis/nethserver-ns8-migration/apps/nethserver-nethvoice14/bind.env MODULE_IMAGE_URL="ghcr.io/nethesis/nethvoice:286"
migrate
verify networks are empty
make sure audio and calls works in every supported scenario

Test case 2 (fresh install):

install ghcr.io/nethesis/nethvoice:286
make sure audio and calls works in every supported scenario

Amygos commented 2 months ago

Moved to https://github.com/NethServer/dev/issues/7013

nethesis / ns8-nethvoice

Clear Asterisk network NAT options on migration #286