NethVoice: port conflict causes CTI and App access failure on both migrated and fresh installations

[Amygos]

After migrating from NethServer 7 to or freshly installing NethVoice on NethServer 8, users are unable to access the CTI and related applications. The issue is caused by a TCP port conflict between Asterisk and the NethCTI middleware service, resulting in SSL errors and failed service startups.

Steps to reproduce:

1. Perform a fresh installation of NethVoice on NethServer 8, or migrate from NethServer 7 to 8.
2. Attempt to access the CTI or any related application (e.g., mobile App).
3. Observe that login fails and services are inaccessible.
4. Check the Asterisk and system logs for errors related to TCP port binding and SSL.

Expected behavior:
Users should be able to access the CTI and related applications immediately after a fresh installation or migration, with all services starting correctly and without port conflicts.

Actual behavior:

• Access to CTI and App fails for all users.
• The NethCTI middleware service fails to start due to port already being used by Asterisk.
• System logs show repeated attempts to start the middleware, hitting the systemd start limit.
• Asterisk logs display SSL connection errors.

Components:
NethVoice 1.4.5

See also:

• Helpdesk ticket 1
• Helpdesk ticket 2
• Private Mattermost Discussion

[Amygos]

Testing release nethesis/ns8-nethvoice 1.4.6-testing.7