When a Signal Messenger group member initiates a call, a temporary call session is created that triggers ringing notifications for all group members.
The expected behavior is that the call session should terminate automatically when the last participant leaves the call. However, it appears that the session is not properly cleaned up, which prevents subsequent calls from correctly triggering ringing notifications for all members.
This issue has been observed in both Signal Mobile and Signal Desktop, which suggests the problem likely originates from the backend call session lifecycle management rather than the individual client implementations.
Steps to Reproduce
Create or open a Signal group with multiple members.
Member A initiates a group call.
All members receive ringing notifications and can join the call.
All participants leave the call until the last participant disconnects.
Later, another member (B) initiates a new group call.
Actual Behavior
The new call does not trigger ringing notifications for all group members as expected.
The system behaves as if the previous call session is still active.
Expected Behavior
When the last participant leaves, the call session should be fully terminated.
A new call initiation should create a fresh session.
All group members should receive ringing notifications again.
Environment
Observed on:
Signal Mobile applications
Signal Desktop application
Because the issue occurs across multiple client platforms, it likely originates from shared call session management logic.
Suspected Component
The issue may originate from the Signal Calling Service, specifically in the call session lifecycle cleanup after the last participant disconnects.
Repository:
https://github.com/signalapp/Signal-Calling-Service
Additional Notes
The system appears to retain the previous call session state even after all participants have left. Ensuring proper cleanup of the session after the final disconnect should allow new calls to trigger ringing correctly for all group members.
When a Signal Messenger group member initiates a call, a temporary call session is created that triggers ringing notifications for all group members.
The expected behavior is that the call session should terminate automatically when the last participant leaves the call. However, it appears that the session is not properly cleaned up, which prevents subsequent calls from correctly triggering ringing notifications for all members.
This issue has been observed in both Signal Mobile and Signal Desktop, which suggests the problem likely originates from the backend call session lifecycle management rather than the individual client implementations.
Steps to Reproduce
Create or open a Signal group with multiple members.
Member A initiates a group call.
All members receive ringing notifications and can join the call.
All participants leave the call until the last participant disconnects.
Later, another member (B) initiates a new group call.
Actual Behavior
The new call does not trigger ringing notifications for all group members as expected.
The system behaves as if the previous call session is still active.
Expected Behavior
When the last participant leaves, the call session should be fully terminated.
A new call initiation should create a fresh session.
All group members should receive ringing notifications again.
Environment
Observed on:
Signal Mobile applications
Signal Desktop application
Because the issue occurs across multiple client platforms, it likely originates from shared call session management logic.
Suspected Component
The issue may originate from the Signal Calling Service, specifically in the call session lifecycle cleanup after the last participant disconnects.
Repository:
https://github.com/signalapp/Signal-Calling-Service
Additional Notes
The system appears to retain the previous call session state even after all participants have left. Ensuring proper cleanup of the session after the final disconnect should allow new calls to trigger ringing correctly for all group members.