CTI Login Failure After NethVoice Module Move

[Amygos]

The CTI application, part of the NethVoice module, fails to allow user login
after the module has been successfully moved to a new node. The issue arises
despite the phones registering correctly after reset and provisioning. During
the move, the hostname assigned to the CTI was also changed to match the
client's domain.

Steps to reproduce

• Move the NethVoice module to a new node without modifying any parameters.
• After the move, update the hostname assigned to the CTI to match the
  client's domain.
• Attempt to log in to the CTI application.

Expected behavior
The CTI application should allow successful login after the module move and
hostname update.

Actual behavior
The CTI application fails to allow login, entering an infinite loop and not
completing the login process.

Components

• ns8-nethvoice

Workaround
The issue was resolved by restarting the nethcti-server and nethcti-ui
services, which triggered the correct regeneration of the
/app/public/config/config.production.js file. Specifically, the steps taken
were:

• Restart the services using the command: systemctl --user restart nethcti-server nethcti-ui
• After the restart, the /app/public/config/config.production.js file was
  correctly regenerated with the intended API_ENDPOINT value, resolving the
  login issue.

See also

• Links to discussions on private mattermost:
  https://mattermost.nethesis.it/nethesis/pl/7or68upggfn47nj11w1s3sj7kc

Acknowledgements Thanks to especially @charliewhiting and @tonyco97 , for
their assistance in diagnosing and resolving the issue related to the CTI
login failure after the NethVoice module move.

[Amygos]

Testing release nethesis/ns8-nethvoice 1.3.3-testing.1