NethLink: Mismatch between “Last calls” and NethVoice CTI

[tonyco97]

Summary

The “Last calls” tab in NethLink shows data that is inconsistent with the “Last calls” tab in NethVoice CTI.

Under specific conditions, the same call is duplicated and call status is wrong in NethLink, while CTI reports the correct call states.

This leads to:

• incorrect call history
• wrong call status (answered vs missed)
• confusion for operators

---

Expected behavior

For any given call:

The Last calls list in NethLink
must be identical to
the Last calls list in NethVoice CTI

including:

• number of calls
• call direction
• call status (answered, missed, etc.)

---

Actual behavior

In NethLink:

• Two calls are shown for the same interaction
• Both are marked as answered

In NethVoice CTI:

• Two calls are shown
• One is answered
• One is missed

So NethLink incorrectly marks the missed call as answered.

---

Steps to reproduce

Two users are required:

• User A → caller
• User B → receiver

1. User B opens NethLink
2. User B sets himself to DND on the softphone/app
3. User A calls User B
4. User B answers the call from NethLink
5. User A hangs up
6. User B opens Last calls in both:
   • NethLink
   • NethVoice CTI

---

Result

Application	Calls	Status
NethVoice CTI	2	1 answered, 1 missed
NethLink	2	2 answered (wrong)

NethLink loses the missed call information and marks both as answered.

---

Impact

This breaks:

• call history reliability
• reporting accuracy
• user trust in call logs

For operators this is critical, since missed calls may not be recognized.

---

Notes

The issue seems to happen when:

• NethLink handles the call
• while the same user is in DND on the softphone

This likely causes:

• duplicated call events
• wrong state resolution in the WebSocket / call state sync layer

[tonyco97]

NethLink testing version here: NethServer/nethlink#90 (comment)