nethvoice-cti UI service becomes unresponsive

[gsanchietti]

Introduction:
The CTI UI service, based on Next.js, can become unresponsive. Incidents is not detected by monitoring or internal alarms; the service is online but unreachable. Restarting the service with systemctl restart --user nethcti-ui restores the access, but saving or restoring NethVoice settings did not resolve the issue.

Steps to reproduce:

1. Deploy a dedicated NethServer 8 instance for a customer with the nethvoice-cti UI module (Next.js 14.2.x).
2. Operate under normal production usage.
3. Wait for the CTI UI to become unresponsive (no warnings or alerts).
4. Attempt to access the CTI web page (offline/unreachable).
5. Try restoring or saving NethVoice settings (has no effect).
6. Restart the service with systemctl restart --user nethcti-ui (restores functionality).

Expected behavior:
The CTI UI should remain accessible and responsive, or monitoring should promptly alert staff to any service outage.

Actual behavior:

• The CTI UI becomes completely unresponsive and appears offline for several hours, with no alarms raised by monitoring tools.
• Direct access (via browser or curl) fails.
• Saving/restoring NethVoice settings does not resolve the issue.
• Only restarting the service restores normal operation.
• The customer is the only source of feedback about the outage.

Components:

• NethServer 8
• nethvoice 1.3.3

See also:

• Customer support ticket
• Previous reports and discussion
• Ongoing issue tracking/discussion
• Upgrade to Next.js 15.3.x PR

[Amygos]

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

[edospadoni]

Test case:

• check the bug is not reproducible